An enterprise cloud operations team manages a Google Cloud resource hierarchy containing an Organization node, top-level environment Folders, and team-specific sub-folders. A security engineer needs to grant a lead analyst the ability to manage compute resources across all current and future projects located inside the 'Analytics-Dev' sub-folder, while following Google-recommended security practices and avoiding unnecessary operational maintenance. What should the security engineer do?
- Grant the predefined Compute Admin role to the lead analyst at the 'Analytics-Dev' sub-folder level.Cevap
- BGrant the predefined Compute Admin role to the lead analyst individually on each current project inside the 'Analytics-Dev' sub-folder.
- CGrant the primitive Editor role to the lead analyst at the Organization root level.
- DConfigure an Organization Policy at the 'Analytics-Dev' sub-folder level specifying the lead analyst user identity as an allowed admin principal.
Cevap
Grant the predefined Compute Admin role to the lead analyst at the 'Analytics-Dev' sub-folder level.
Granting the predefined Compute Admin role at the folder level leverages Google Cloud's IAM resource hierarchy policy inheritance. Permissions applied at a parent folder automatically flow down to all current and future child projects residing within that folder. Furthermore, using a predefined role ensures compliance with the principle of least privilege compared to broad primitive roles.
Adım Adım Çözüm
Anahtar Kavram
Resource Hierarchy IAM Inheritance & Predefined Roles