A security architect is establishing a new Google Cloud resource hierarchy for an enterprise workload. To ensure proper IAM role inheritance and central governance, arrange the initial administrative setup steps in the correct top-down sequence, starting from the highest scope in the resource hierarchy.
- 1Configure central security policies and grant organization-wide governance roles at the Organization node.
- 2Create environment-specific Folders under the Organization and apply folder-level IAM role bindings for business units.
- 3Provision dedicated Google Cloud Projects inside the appropriate environment Folders.
- 4Assign resource-level IAM roles and service account permissions to individual resources within the Projects.
Answer
The correct administrative sequence starts at the Organization node, followed by creating Folders, provisioning Projects within those Folders, and finally granting fine-grained resource-level IAM permissions inside the Projects.
Google Cloud resource hierarchy follows a strict top-down structure: Organization node -> Folders -> Projects -> Resources. IAM permissions granted at parent levels automatically inherit downward to child nodes.
Step-by-Step Solution
Key Concept
Google Cloud Resource Hierarchy and Top-Down IAM Policy Inheritance