Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An enterprise is establishing its Google Cloud resource hierarchy to manage multiple applications across different environments, such as Development, Staging, and Production. The cloud architecture team needs to establish clear administrative boundaries and centrally apply consistent access control policies across collections of projects.
Which level of the Google Cloud resource hierarchy directly serves as a grouping mechanism for projects to apply shared Identity and Access Management (IAM) policies?
Labels are key-value pairs attached directly to individual Google Cloud resources or projects. They are metadata used primarily for cost tracking, filtering, categorization, and inventory reporting across different environments or cost centers.
Labels are not structural nodes within the Google Cloud resource hierarchy and do not provide an administrative boundary for permission inheritance. You cannot attach IAM roles to a label to automatically grant permissions across multiple projects.
environment: production, team: analytics).This option would be correct if the organization needed to filter resources in billing reports or categorize individual virtual machines by department for inventory purposes.
While labels help with granular cost attribution, folders and projects provide the actual structural framework for access management and policy inheritance.
The Organization resource is the root node of the Google Cloud resource hierarchy. It represents the entire company or enterprise and is directly mapped to a Cloud Identity or Google Workspace domain. It provides centralized visibility and global governance across all cloud assets belonging to the enterprise.
While the Organization resource can hold IAM policies, applying access controls directly at the Organization level enforces those policies globally across every folder, project, and resource in the company. The scenario asks for a grouping mechanism to manage subsets of related projects (such as isolating Development from Production). The Organization node is too broad to serve as a selective grouping layer for distinct environments.
This option would be correct if the requirement was to establish the top-level root node for the company, manage central domain ownership, or assign company-wide roles like Organization Administrator.
To use folders, an organization must first have an active Organization resource established as the root parent.
A folder is an intermediate organizing node in the Google Cloud resource hierarchy located directly below an Organization resource and above individual projects or nested subfolders. Folders provide an essential administrative boundary, allowing organizations to structure their cloud footprint by department, environment, or business unit.
Folders are purpose-built to act as a grouping mechanism for projects and child folders. When administrators grant an Identity and Access Management (IAM) role or apply an organization policy at the folder level, that configuration is automatically inherited by all nested folders, projects, and child service resources beneath it. This structure allows the architecture team to enforce consistent permissions across entire environments—such as Development or Production—without having to configure IAM settings on each project individually.
Folder Admin) to department leads without exposing the root Organization node.While the root Organization node applies policies globally and projects isolate individual workloads, folders provide the exact intermediate grouping layer needed to enforce common policies across subsets of projects.
A project is the base-level organizing entity in Google Cloud. It acts as the container where all service-level resources—such as Compute Engine virtual machines, Cloud Storage buckets, and Cloud SQL instances—are created and executed. Projects also serve as the boundary for enabling APIs and establishing billing linkages.
Projects cannot contain other projects, nor can they act as a grouping container for multiple distinct projects. A project is an individual boundary rather than an aggregate grouping mechanism. If administrators configured IAM policies at the project level alone, they would have to repeat the configuration across every individual project, resulting in high administrative overhead.
This option would be correct if the scenario asked where service-level resources like Compute Engine VMs and Cloud Storage buckets are deployed and managed.
Projects inherit IAM permissions from their parent folders and the root Organization, making folders the appropriate layer for grouping multiple projects under common access rules.
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