nerdexam
Google

PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #30

You are migrating an on-premises application to Google Cloud. The application requires a high availability (HA) PostgreSQL database to support business-critical functions. Your company's disaster…

The correct answer is C. Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-. To meet both zonal and regional failure recovery within 30 minutes RTO/RPO, you need two layers of protection. Cloud SQL regional configuration with HA enabled uses synchronous replication to a standby in a different zone, automatically failing over for zonal outages with…

Ensuring Database Reliability, Availability, and Scalability

Question

You are migrating an on-premises application to Google Cloud. The application requires a high availability (HA) PostgreSQL database to support business-critical functions. Your company's disaster recovery strategy requires a recovery time objective (RTO) and recovery point objective (RPO) within 30 minutes of failure. You plan to use a Google Cloud managed service. What should you do to maximize uptime for your application?

Options

  • ADeploy Cloud SQL for PostgreSQL in a regional configuration. Create a read replica in a different
  • BDeploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Take periodic
  • CDeploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-
  • DMigrate the PostgreSQL database to multi-regional Cloud Spanner so that a single region outage

How the community answered

(30 responses)
  • A
    10% (3)
  • B
    7% (2)
  • C
    80% (24)
  • D
    3% (1)

Explanation

To meet both zonal and regional failure recovery within 30 minutes RTO/RPO, you need two layers of protection. Cloud SQL regional configuration with HA enabled uses synchronous replication to a standby in a different zone, automatically failing over for zonal outages with near-zero RPO. Adding a cross-region read replica covers regional disasters - it can be promoted to a primary if the entire region fails, meeting the 30-minute RTO/RPO target. Option A lacks HA (no automatic zonal failover). Option B's periodic snapshots may not meet RPO (data created since the last snapshot is lost). Option D (Cloud Spanner) is not PostgreSQL and is a managed service with no direct PostgreSQL compatibility.

Topics

#Cloud SQL#High Availability#Disaster Recovery#RTO/RPO

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice