Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An organization enforces strict data residency requirements by setting the constraints/gcp.resourceLocations constraint at the organization root with allowedValues set to European regions (in:eu-locations). A specialized data science team requires an exception to deploy new resources in us-central1 within their dedicated Google Cloud project, while maintaining European region access and preventing inheritance conflicts.
How should the DevOps engineer configure the organization policy on the target project to grant this exception?
This approach removes the centralized organization-level managed constraint (constraints/gcp.resourceLocations) and attempts to manually enforce regional boundaries on each individual project using custom constraints.
gcp.resourceLocations constraint natively supports hierarchical overrides and value groups, making custom constraints unnecessary for standard regional restrictions.gcp.resourceLocations.The organization required complex conditional logic based on custom resource fields that the standard gcp.resourceLocations constraint does not inspect.
In the Google Cloud Resource Hierarchy, organization policies are inherited down the tree by default from the organization root to folders and projects. When a child node (such as a specific project) requires an exception or modification to an inherited list constraint like constraints/gcp.resourceLocations, administrators can configure the policy on that specific resource node to override its parent by setting inheritFromParent: false (replacing parent rules rather than merging).
in:eu-locations and us-central1 in the project's allowedValues list, the team retains the ability to provision resources in European regions while gaining access to us-central1.allowedValues or deniedValues lists.Replacing inheritance and providing the complete set of permitted values (in:eu-locations and us-central1) ensures deterministic control. If the administrator simply merged values, the parent policy would still restrict creation if restrictive rules conflicted.
This configuration keeps policy inheritance active (merge with parent) and places us-central1 inside the deniedValues list of the project's list policy rules.
us-central1 to deniedValues will strictly block any resource creation in us-central1, achieving the exact opposite of what the data science team needs.allowedValues (in:eu-locations). Because us-central1 is not in the parent's allowed list, merging with the parent would still deny us-central1 even if it were not in deniedValues.deniedValues always takes precedence over allowedValues.The goal was to explicitly forbid us-central1 across a project while inheriting an allowlist that previously contained broad US regions.
This option expands the allowed locations at the organization root to include us-central1 for all folders and projects across the company, while granting the development team administrative permissions over organization policies.
us-central1 to the root organization policy permits all teams across the entire company to create resources in us-central1, violating global data residency governance.roles/orgpolicy.policyAdmin to application developers gives them sweeping privileges to modify, delete, or disable security constraints across the resource hierarchy.The enterprise made a global strategic shift to adopt us-central1 as an approved production region for all business units and teams.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated