Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A healthcare organization must comply with strict national data residency laws for its cloud workloads. The leadership team has established the following governance requirements:
Which Google Cloud governance mechanism should the organization implement to meet these requirements?
When an administrator configures and enforces the resource locations constraint (constraints/gcp.resourceLocations) in the Organization Policy Service, the policy establishes rules governing future resource provisioning. However, the Organization Policy Service is a preventative governance mechanism, not an automated data migration or infrastructure relocation tool.
The organization already had data stored in unauthorized regions and used a dedicated data movement tool, such as Storage Transfer Service, to actively transfer objects into compliant regional buckets.
A common misconception among cloud beginners is assuming that applying an organization policy retroactively remediates or relocates non-compliant resources. To maintain strict data residency, organizations should apply gcp.resourceLocations constraints before teams begin deploying workloads.
The restrict service usage constraint (constraints/gcp.restrictServiceUsage) is a managed rule within the Organization Policy Service that governs which Google Cloud products and API endpoints can be used within an organization, folder, or project. It operates by restricting runtime access to service resources based on an allowed or denied list of service APIs (such as compute.googleapis.com or storage.googleapis.com).
location property of a resource during provisioning.The organization needed to prevent project teams from enabling or using specific Google Cloud products or APIs that have not been approved by the security or compliance team.
A common misconception is confusing gcp.restrictServiceUsage with gcp.resourceLocations because both constraints are applied together by default in compliance control packages like Assured Workloads. In practice, gcp.restrictServiceUsage restricts which services can be used, whereas gcp.resourceLocations restricts where those services can create resources.
The Organization Policy Service gives administrators centralized, programmatic control over their organization's cloud resources. Within this service, the resource locations constraint (constraints/gcp.resourceLocations) is a governance control designed to limit the physical geographic locations where new Google Cloud resources can be deployed and maintained. For supported data-containing services, restricting the resource location also governs where the underlying data is stored.
gcp.resourceLocations constraint using an allowed values list (allowed_values) containing specific United States regions (such as us-central1 or us-east4) or a curated value group like in:us-locations.
in:us-locations allows organizations to define broad geographic boundaries that automatically include current and future regions within that jurisdiction.Unlike manual audits or reactive cleanup scripts, enforcing the resource locations constraint through the Organization Policy Service provides preventative, automated governance at the platform layer. It directly blocks non-compliant deployments at the time of creation without requiring manual intervention for every project.
In Google Cloud, AI zones are specialized zonal locations (identified by the -ai string in their name, such as us-west4-ai2b) tailored specifically for artificial intelligence and machine learning workloads. Administrators can create a custom organization policy constraint to explicitly allow or deny the creation of virtual machine (VM) instances within these specialized AI zones.
-ai zone naming convention, meaning this custom condition would not properly govern general-purpose United States regions or storage services.in:us-locations).The organization specifically wanted to allow or block developers from provisioning Compute Engine virtual machines inside specialized AI zones (such as us-central1-ai1a) while leaving other resource types unaffected.
When enforcing organization-wide data residency across both compute and storage services, administrators should use the managed resource locations constraint (gcp.resourceLocations) rather than a narrow custom constraint built for specialized AI zones.
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