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.
An enterprise structures its Google Cloud environment using the Resource Manager hierarchy, which includes an Organization node at the root, department-specific Folders, application Projects, and individual service Resources (such as Compute Engine virtual machines and Cloud Storage buckets). The security team has the following access control requirements for the Engineering department:
How should the security team apply Identity and Access Management (IAM) allow policies within the resource hierarchy to meet these requirements?
The Organization resource is the root node at the apex of the Google Cloud resource hierarchy. It serves as the hierarchical ancestor for all Folders, Projects, and service-level Resources belonging to a company. When an IAM allow policy is applied at the Organization level, the granted roles and permissions cascade downward to every folder, project, and resource across the entire cloud environment.
Organization Administrator or Network Admin) are intended for central IT or security teams who require universal visibility and control across the entire enterprise.This approach would be appropriate if the company needed to grant a central IT or enterprise-wide networking team universal permissions across all departments, folders, and projects in the company.
A common misconception is confusing IAM allow policies with Organization Policy Service constraints. While Organization Policy constraints (which govern what resource configurations are allowed) can be superseded by policies defined at a lower level when configured for exceptions, IAM allow policies (which govern who has access) are always additive as they propagate down the hierarchy.
In the Google Cloud resource hierarchy, resources are organized across four primary levels from top to bottom: the Organization node (the root node representing the company), Folders (optional grouping mechanisms for departments, teams, or environments), Projects (base-level trust boundaries that house enabled services), and Resources (fundamental service components such as Compute Engine virtual machines and Cloud Storage buckets). Identity and Access Management (IAM) allow policies can be attached at any of these levels, and permissions automatically propagate downward through the hierarchy from parent nodes to child nodes.
Applying IAM policies at the Folder level strikes the ideal balance between administrative efficiency and the principle of least privilege. Setting the policy higher (at the Organization level) would grant overly broad access across the entire company, whereas setting the policy lower (at the Project or Resource level) would require repetitive manual configuration across every project.
A Project is the base-level organizing entity in the Google Cloud resource hierarchy and is required to enable APIs, manage billing links, and deploy service-level Resources (such as Compute Engine virtual machines, Pub/Sub topics, and Cloud Storage buckets). In IAM, a Project represents a trust boundary within a company. When an IAM allow policy is granted at the Project level, those permissions are inherited only by the service resources contained within that specific project.
Granting the IAM role at the Project level would be the right choice if the administrators only needed to manage the service resources (such as virtual machines, topics, and storage buckets) belonging to one specific application or workload housed within a single project.
Understanding the directional flow of the resource hierarchy is essential for cloud governance. Because access flows strictly downward, administrators should grant roles at the smallest scope needed that still encompasses all target resources—which, for a multi-project department, is the department's Folder.
Labels in Google Cloud are user-defined key-value pairs (such as my-label:prod or department:engineering) that can be attached to account-level resources like Projects as well as service-level Resources like Compute Engine virtual machines. Their primary purpose is to annotate, categorize, group, and filter resources for inventory organization and granular Cloud Billing cost tracking.
Using Labels would be the right solution if the requirement were to categorize projects and virtual machines for cost tracking, allowing the organization to filter and analyze charges by department in Cloud Billing reports.
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