You are evaluating Cloud SQL for PostgreSQL as a possible destination for your on-premises PostgreSQL instances. Geography is becoming increasingly relevant to customer privacy worldwide. Your solutio

Question

Options

• AReplicate Cloud SQL databases across different zones.
• BCreate a Cloud SQL for PostgreSQL instance on Google Cloud for the data that does not need to
• CAllow application access to data only if the users are in the same region as the Google Cloud
• DUse features like customer-managed encryption keys (CMEK), VPC Service Controls, and

• A
  13% (5)
• B
  18% (7)
• C
  5% (2)
• D
  65% (26)

Explanation

The question has three distinct requirements that map directly to three Google Cloud capabilities. Customer-Managed Encryption Keys (CMEK) with Cloud KMS controls where encryption keys are stored and who can use them, satisfying the key storage residency requirement. VPC Service Controls creates a security perimeter around Cloud SQL that restricts access based on attributes such as identity, network, and geography, governing who can access the data. Cloud SQL's regional instance configuration combined with Organization Policy constraints (such as constraints/gcp.resourceLocations) controls where data physically resides. Option A (multi-zone replication) only addresses availability, not data residency controls. Option B (separate instances) partially addresses data location but ignores key management and access governance. Option C (region-based access control) addresses only the access dimension and is not a native Cloud SQL feature that covers all three requirements.

No community discussion yet for this question.