Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your company organizes its Google Cloud resources using a multi-layer hierarchy where projects are grouped under department folders within an organization resource. You need to delegate access administration to the team leads of the Engineering department while adhering to the principle of least privilege.
The requirements are:
Engineering folder, with permissions automatically inheriting down to all child folders and projects.What should you do?
The Organization Administrator (roles/resourcemanager.organizationAdmin) role provides comprehensive control over the entire organization's resource hierarchy, organization policies, and IAM allow policies across all departments and projects.
Engineering folder.The engineers were enterprise-wide infrastructure administrators responsible for establishing root-level organization policies and structural hierarchy across the entire enterprise.
Roles should always be granted at the smallest resource scope needed (in this case, the specific folder rather than the organization node).
The Owner (roles/owner) role is a basic role that provides full administrative control over all resources, services, and IAM policies within the assigned scope.
roles/owner on the Engineering folder gives team leads unrestricted read, write, modify, and delete access across all infrastructure, storage objects, and applications in all descendant projects.The organization required the team leads to have universal management authority, including provisioning, altering, and deleting all cloud workloads alongside billing and policy management.
While granting roles to a Google Group is a best practice, pairing it with the roles/owner role introduces massive security exposure and violates compliance guidelines regarding separation of duties.
The Folder IAM Admin (roles/resourcemanager.folderIamAdmin) predefined role provides specific administrative permissions to administer IAM policies on folders without bundling broader data plane or general resource administration privileges.
roles/resourcemanager.folderIamAdmin on the Engineering folder allows leads to modify allow policies across the folder and its descendant resources through hierarchical policy inheritance.Using the predefined Folder IAM Admin role bound to a Google Group at the folder level fulfills the exact functional requirement of delegating IAM policy management while strictly enforcing least privilege and minimizing management overhead.
This approach defines a tailored IAM role with a single permission (resourcemanager.projects.setIamPolicy) and applies it directly to individual user accounts across all separate projects under the department.
Folder IAM Admin role designed specifically for managing policies across folder boundaries.No predefined role existed that matched the required permissions, and granular project-specific isolation without folder inheritance was mandated.
Leveraging folder-level inheritance with predefined roles and Google Groups is the standard architectural pattern for scalable access management in Google Cloud.
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 Validated