Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A growing enterprise has a central IT security team that oversees all Google Cloud deployments. The enterprise needs to configure its cloud environment to meet the following requirements:
How should the enterprise structure its Google Cloud resource hierarchy to meet these requirements?
The Organization Administrator role (roles/resourcemanager.organizationAdmin) is the highest-level administrative role within the Google Cloud resource hierarchy. A user assigned this role at the Organization node has complete control over the entire organization, all of its folders and projects, and every Identity and Access Management (IAM) policy within the hierarchy.
Granting the Organization Administrator role would be appropriate if the individuals were members of the central IT security team responsible for defining organization-wide IAM policies, managing global access control, and delegating folder-level responsibilities across the entire company.
To adhere to the principle of least privilege, department heads and team managers should be assigned the Folder Admin role on their specific departmental folder rather than the Organization Administrator role at the root node.
Creating multiple Organization nodes establishes completely separate, independent root hierarchies in Google Cloud. Because the Organization node is the ultimate scope of administrative authority, each Organization operates as a distinct administrative boundary with its own isolated set of resources, Identity and Access Management (IAM) policies, and organization policies.
This approach would be appropriate if the enterprise consisted of autonomously-run subsidiaries or completely independent divisions with no single central IT department overseeing cloud deployments, or if the company needed a dedicated staging organization or experimental sandbox organization to test policy changes without risking production workloads.
A common misconception is that large departments require their own Organization node to achieve administrative autonomy. In practice, Google Cloud best practices recommend using as few organizations as possible to minimize administrative overhead, relying on folders within a single organization to model departments, legal entities, and teams.
In Google Cloud, a project is the base-level organizing entity required to create and use cloud resources. While Google Cloud users are not strictly required to configure an Organization resource to create projects, operating without an Organization node means that projects exist as standalone, ungrouped entities managed independently by the individual user accounts that created them.
Using standalone projects without an Organization resource would only be suitable for a single individual developer experimenting with Google Cloud on a personal account where multi-user collaboration, centralized governance, and enterprise security policies are not needed.
Whenever an enterprise needs to manage more than one user account, configuring an Organization node paired with Cloud Identity or Google Workspace is a foundational best practice for financial governance, security, and access control.
In the Google Cloud resource hierarchy, the Organization node serves as the root node representing an entire company, while folders act as sub-organizations and administrative isolation boundaries underneath the Organization node. Together, they enable a structured hierarchy where Identity and Access Management (IAM) allow policies, deny policies, and organization policies are inherited downward by all child projects and resources.
Folder Admin (roles/resourcemanager.folderAdmin) or Project Creator to specific department heads at their respective folder level, streamlining department-level administration and cost management.Using a single Organization node combined with departmental folders strikes the ideal balance between centralized governance and team autonomy. Unlike using multiple Organization nodes—which fragments visibility and requires duplicating security policies—or granting organization-wide permissions—which violates least privilege—this approach maintains strict global security standards while empowering individual departments.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated