A financial technology enterprise is planning to migrate its core online transaction processing (OLTP) application from an on-premises PostgreSQL database to Google Cloud. The application requires standard relational SQL capabilities, strong ACID compliance, a 99.95% availability SLA within a single GCP region, and sub-10 millisecond write latency. The workload does not require global multi-region distribution or petabyte-scale horizontal scale-out. To minimize operational complexity and unnecessary costs while satisfying all technical requirements, which database resource strategy should you choose?
- Deploy a Cloud SQL for PostgreSQL instance configured with High Availability (regional failover) across two zones in the target region.Answer
- BDeploy a multi-region Cloud Spanner instance configured with multi-region database replication.
- COrder a GCP Transfer Appliance to physically transfer PostgreSQL database backups into BigQuery for operational OLTP processing.
- DDeploy Cloud SQL for PostgreSQL in a single zone and rely solely on IAM object permissions without configuring a standby failover instance or VPC Service Controls.
Answer
Deploy a Cloud SQL for PostgreSQL instance configured with High Availability (regional failover) across two zones in the target region.
The correct option proposes deploying Cloud SQL for PostgreSQL with High Availability configured across two zones. This directly fulfills all technical criteria—native PostgreSQL support, sub-10ms latency, relational ACID compliance, and a 99.95% regional availability SLA—while avoiding the higher cost and complexity of globally distributed databases.
Step-by-Step Solution
Key Concept
Selecting Cloud SQL HA vs. Cloud Spanner for Regional Relational OLTP Workloads
Estimated Time:1m 30s