Your team wants to limit users with administrative privileges at the organization level.
Which two roles should your team restrict? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.AB.
https://cloud.google.com/resource-manager/docs/creating-managing-organizationTo limit users with administrative privileges at the organization level, your team should restrict the roles of Organization Administrator and Super Admin.
A. Organization Administrator - This is the highest level of administrative privilege in Google Cloud, allowing the user to manage all resources and services within the organization, create projects, and grant roles to other users.
B. Super Admin - This role has similar privileges to the Organization Administrator, but also includes access to the Google Workspace Admin console and the ability to manage users, groups, and domains.
C. GKE Cluster Admin - This role is specific to managing Google Kubernetes Engine clusters and does not have the same level of organizational access as the Organization Administrator or Super Admin.
D. Compute Admin - This role is specific to managing compute resources in Google Cloud, such as virtual machines, disks, and networks, and does not have the same level of organizational access as the Organization Administrator or Super Admin.
E. Organization Role Viewer - This role has read-only access to view all roles and permissions within the organization, but does not have any administrative privileges.
Therefore, to limit users with administrative privileges at the organization level, your team should restrict the roles of Organization Administrator and Super Admin. This can be achieved by removing these roles from users who do not require them, or by implementing role-based access control (RBAC) policies to ensure that only authorized users have access to these roles.