Question

Difficulty: EasyIdentity and Access Management (IAM) Roles and Resource Hierarchy

A cloud administrator is setting up access controls for a departmental team in Google Cloud across multiple projects inside a designated folder. Which TWO access management strategies follow Google Cloud recommended best practices for resource hierarchy and Identity and Access Management (IAM)?

  1. Grant predefined IAM roles at the folder level to allow permissions to automatically inherit down to all child projects within that department.Answer
  2. Assign fine-grained predefined roles matching specific job responsibilities rather than using primitive roles.Answer
  3. C
    Grant the primitive Editor role at the Organization level to ensure team members have uninterrupted access across all infrastructure.
  4. D
    Grant the Service Account Admin role to Compute Engine instances to allow them to execute workloads under identity credentials.

Answer

The correct access management strategies are granting predefined IAM roles at the folder level to leverage resource hierarchy inheritance, and assigning fine-grained predefined roles tailored to specific job responsibilities instead of primitive roles.
In Google Cloud IAM, permissions inherit downward through the resource hierarchy. Applying predefined roles at the folder level simplifies administration while automatically applying permissions to child projects. Furthermore, assigning fine-grained predefined roles guarantees that identities receive only the specific access required for their operational tasks.

Step-by-Step Solution

1
Evaluate the inheritance mechanism of the Google Cloud resource hierarchy.
Permissions applied at parent resource nodes (such as Folders) automatically propagate down to child resources (such as Projects).
Binding roles at the folder level centralizes access management for all projects within that folder.
2
Determine the appropriate IAM role type to satisfy least privilege requirements.
Predefined roles offer fine-grained control for specific workloads, whereas primitive roles grant overly broad permissions.
Using predefined roles minimizes potential security risks by granting only required permissions.

Key Concept

IAM Resource Hierarchy Inheritance and Fine-Grained Predefined Roles
Rate this question