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 organizes its Google Cloud resources using a standard resource hierarchy consisting of an Organization node, departmental Folders, and individual Projects containing workloads.
A cloud administrator grants a developer the Storage Object Admin (roles/storage.objectAdmin) role on the Engineering folder. The Engineering folder contains several child projects, each containing multiple Cloud Storage buckets.
How does this role assignment propagate across the resource hierarchy, and what access will the developer have?
In Google Cloud, Identity and Access Management (IAM) evaluates policies hierarchically down the resource tree. The resource hierarchy forms a parent-child relationship structured from the Organization node, down through Folders, to Projects, and finally to individual Resources (such as Cloud Storage buckets and Compute Engine instances).
Engineering Folder—it is automatically inherited by all descendant resources, including all child Projects and the Cloud Storage buckets residing within them.roles/storage.objectAdmin at the folder level, they have full administrative access over objects in every bucket across all projects residing under that folder without needing redundant role bindings.Granting permissions at the folder level leverages Google Cloud's built-in policy inheritance model. It simplifies governance while guaranteeing that the developer has the required object management privileges across all relevant departmental storage resources.
This option assumes a temporal boundary or state snapshot model where IAM permissions apply only to newly provisioned resources rather than dynamically applying across the entire resource lifecycle.
This option would be correct if Google Cloud used a one-time copy mechanism during resource deployment that copied parent access lists only at initial initialization.
This option describes an isolated resource model or non-inheriting permission system where each tier requires explicit, independent authorization.
This option would be correct only if Google Cloud evaluated IAM policies exclusively within flat, isolated boundaries without resource inheritance or folder structures.
This option describes a destructive overwrite model, where setting an access policy at an upper container replaces or wipes out all fine-grained permissions configured on downstream resources.
roles/storage.objectAdmin to one user at the folder level does not clear out Viewer, Editor, or Custom roles assigned to other users on child projects.This choice would be correct if assigning an IAM policy at a parent node initiated an administrative purge that replaced all descendant IAM policy files with the parent's exact configuration.
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