A cloud administration team needs to ensure that IAM roles within a specific organizational Folder can only be granted to user accounts belonging to their verified corporate Google Workspace domain. They want to prevent project owners within that Folder from adding external Gmail or third-party accounts to IAM policies. Which administrative action correctly enforces this restriction across all current and future projects inside the Folder?
- Apply the Domain Restricted Sharing Organization Policy constraint (constraints/iam.allowedPolicyMemberDomains) on the Folder node and specify the corporate Google Workspace Directory Customer ID.Answer
- BGrant the Organization Policy Admin (roles/orgpolicy.policyAdmin) role on the Folder to all project owners so that their IAM changes are restricted to internal users.
- CAssign the Owner primitive role (roles/owner) at the Folder level to automatically filter external principal email addresses out of child project IAM policies.
- DRevoke IAM policy edit permissions on child projects, relying on inherited IAM policy restrictions from the parent Folder to block external bindings.
Answer
Apply the Domain Restricted Sharing Organization Policy constraint on the target Folder node with the allowed corporate Directory Customer ID.
The correct approach configures the Domain Restricted Sharing Organization Policy constraint (`constraints/iam.allowedPolicyMemberDomains`) at the Folder level. Organization Policies establish constraints on resource configurations and propagate down the Google Cloud resource hierarchy to all child projects.
Step-by-Step Solution
Key Concept
Organization Policies enforce resource hierarchy constraints (such as Domain Restricted Sharing) to restrict allowed configurations independently of IAM permission grants.
Estimated Time:1m 15s