A company's cloud operations team is configuring access control within their Google Cloud resource hierarchy. The hierarchy contains an Organization node with top-level folders for different business units, including a folder named Retail Operations. The team needs to allow a lead developer to create new projects inside the Retail Operations folder only, while preventing them from creating projects in other folders or managing folder policies. Which IAM role configuration meets these requirements while adhering to the principle of least privilege?
- Grant the Project Creator role (roles/resourcemanager.projectCreator) to the lead developer on the Retail Operations folder node.Cevap
- BGrant the Owner role (roles/owner) to the lead developer on the Organization node.
- CGrant the Project Creator role (roles/resourcemanager.projectCreator) to the lead developer on the Organization node.
- DGrant the Folder Admin role (roles/resourcemanager.folderAdmin) to the lead developer on the Retail Operations folder node.
Cevap
Grant the Project Creator role (roles/resourcemanager.projectCreator) to the lead developer on the Retail Operations folder node.
Assigning the Project Creator predefined role (roles/resourcemanager.projectCreator) specifically on the Retail Operations folder node grants the required permission to provision projects under that folder. Because IAM policies inherit downwards in the Google Cloud resource hierarchy, binding the role at the folder level ensures the developer cannot create projects in sibling or parent nodes, adhering strictly to the principle of least privilege.
Adım Adım Çözüm
Anahtar Kavram
Resource Hierarchy IAM Policy Scoping and Inheritance
Tahmini Süre:1m 30s