Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is deploying new AlloyDB for PostgreSQL clusters and Cloud SQL instances across multiple Google Cloud projects grouped under a standard compliance folder (without Assured Workloads). To satisfy strict European data residency and sovereignty mandates, your architecture must meet the following requirements:
europe-west1 and europe-west4.us-central1 to remain operational while they are audited and migrated.Which approach should you implement at the compliance folder level?
sqladmin.googleapis.com/Instance restricting resource.region to europe-west1 and europe-west4, and apply it to automatically block legacy us-central1 instances from running.Custom organization policies allow administrators to define granular rules using Common Expression Language (CEL) against specific resource fields, such as restricting resource.region on sqladmin.googleapis.com/Instance during CREATE or UPDATE operations.
sqladmin.googleapis.com/Instance applies strictly to Cloud SQL. Newly created AlloyDB clusters would remain unrestricted and could still be provisioned outside Europe.us-central1 instances and will not automatically block or stop them from running.resource.region alone does not require Customer-Managed Encryption Keys (CMEK); a separate rule or constraint for disk encryption would still be required.You only needed granular, Cloud SQL-specific field restrictions (such as enforcing a specific automated backup region or final backup retention period) without affecting AlloyDB or relying on multi-service residency enforcement.
constraints/sql.restrictNoncompliantResourceCreation on the compliance folder, and set constraints/sql.restrictPublicIp to True.The constraints/sql.restrictNoncompliantResourceCreation boolean constraint is an internal compliance guardrail automatically configured during Assured Workloads onboarding to enforce regulatory region and CMEK rules. Meanwhile, constraints/sql.restrictPublicIp is a connection organization policy that prevents Cloud SQL instances from being assigned public IP addresses.
constraints/sql.restrictNoncompliantResourceCreation outside of an Assured Workloads environment causes Cloud SQL instance creation to fail with errors such as Requested region is not compatible with host project.sqladmin.googleapis.com) and do not govern AlloyDB for PostgreSQL clusters or instances.sql.restrictNoncompliantResourceCreation should never be manually enabled or modified on standard projects.sql.restrictPublicIp only regulate network interfaces, not physical data residency.The organization had onboarded the folder into an Assured Workloads European data boundary package (where sql.restrictNoncompliantResourceCreation is managed automatically) and the primary goal was blocking public internet exposure on Cloud SQL.
europe-west1 for the legacy instances.VPC Service Controls create a context-aware security perimeter around Google Cloud services to prevent data exfiltration and restrict API calls—such as blocking unauthorized Cloud SQL imports and exports via Cloud Storage. Cross-region read replicas allow Cloud SQL instances to replicate data to another region for high availability or disaster recovery.
europe-west1 for instances whose primaries remain in us-central1 replicates data across regions rather than providing an inventory for retiring the US-based instances.constraints/gcp.resourceLocations, users with IAM permissions can still create resources in unapproved regions.The primary requirement was to prevent data exfiltration by restricting Cloud SQL Admin API and Cloud Storage API import/export operations to an approved network perimeter, alongside regional disaster recovery.
constraints/gcp.resourceLocations with allowedValues set to europe-west1 and europe-west4, enforce constraints/gcp.restrictNonCmekServices for the database APIs, and use Cloud Asset Inventory to track legacy instances.Google Cloud provides Organization Policy Service constraints that allow administrators to enforce centralized guardrails across folders and projects through policy inheritance. When applied at a compliance folder level, every project inside that folder automatically inherits the restrictions.
constraints/gcp.resourceLocations): Setting allowedValues to europe-west1 and europe-west4 ensures that newly created AlloyDB clusters (along with their instances and backups) and Cloud SQL instances can only be provisioned in those approved European regions.constraints/gcp.restrictNonCmekServices): Requiring Customer-Managed Encryption Keys (CMEK) for database APIs ensures that all new at-rest data is encrypted using keys controlled by your organization rather than Google's default encryption keys.gcp.resourceLocations constraint is not retroactive, existing Cloud SQL instances in us-central1 continue operating without interruption while Cloud Asset Inventory provides visibility into resource locations for auditing and migration.Using standard predefined constraints avoids the compatibility errors associated with Assured Workloads-only policies while delivering broad, multi-service enforcement for both physical location and encryption key sovereignty.
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