An enterprise operations team is structuring their Google Cloud resource hierarchy. They created a designated Folder named `Staging-Environment` for testing workloads. You need to allow the software engineering group to create new GCP projects within the `Staging-Environment` Folder only, without giving them project creation permissions across the rest of the Organization. Which administration action follows Google Cloud recommended best practices and the principle of least privilege?
- Grant the Project Creator role (`roles/resourcemanager.projectCreator`) to the software engineering group bound specifically at the `Staging-Environment` Folder level.Cevap
- BGrant the Owner primitive role (`roles/owner`) to the software engineering group at the `Staging-Environment` Folder level.
- CGrant the Project Creator role (`roles/resourcemanager.projectCreator`) at the Organization root level and attach an IAM Deny policy at all other folder levels.
- DGrant the Billing Account User role (`roles/billing.user`) on the parent Billing Account without granting any Resource Manager roles on the folder.
Cevap
Grant the Project Creator role (`roles/resourcemanager.projectCreator`) to the software engineering group bound specifically at the `Staging-Environment` Folder level.
Granting `roles/resourcemanager.projectCreator` at the target Folder level explicitly enables users to provision projects inside that specific container, adhering to the principle of least privilege while utilizing resource hierarchy inheritance appropriately.
Adım Adım Çözüm
Anahtar Kavram
Resource Hierarchy IAM Scoping and Least Privilege Project Provisioning
Tahmini Süre:1m 30s