A principal security architect is configuring the Google Cloud resource hierarchy for a multi-regional organization. The hierarchy consists of an Organization node, under which sits a top-level folder named 'Production-Workloads' containing two sub-folders: 'App-Services' and 'Data-Analytics'. A DevOps engineer has been assigned the 'Project Creator' role (`roles/resourcemanager.projectCreator`) at the 'Production-Workloads' folder level, and the 'Billing Account User' role (`roles/billing.user`) on the corporate Billing Account. The engineer needs to create a new project named 'analytics-pipeline-prod' under the nested 'Data-Analytics' sub-folder and associate it with the corporate Billing Account. However, an explicit IAM deny policy or missing permission is suspected of blocking the deployment. Based on the Google Cloud resource hierarchy IAM inheritance model and billing requirements, which statement correctly describes the permission behavior for this scenario?
- The project creation will succeed because 'roles/resourcemanager.projectCreator' granted at the parent folder ('Production-Workloads') automatically inherits down to the nested 'Data-Analytics' sub-folder, fulfilling the project creation requirement alongside the Billing Account User role.Cevap
- BThe project creation will fail because IAM policy inheritance is strictly limited to direct parent-child pairs and does not propagate to nested sub-folders unless explicitly re-granted at each sub-folder level.
- CThe project creation will fail because linking a project to a corporate Billing Account requires the primitive 'Owner' role on the target sub-folder rather than predefined IAM roles.
- DThe project creation will fail because the engineer only holds the 'Billing Account User' role on the Billing Account, but requires 'Billing Account Administrator' permissions on the target sub-folder node to establish project billing links.