Explanation:
To maximize uptime for your application while meeting the RTO and RPO within 30 minutes, the best approach is to deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled and create a cross-region read replica. This setup ensures high availability within the primary region and provides a quick disaster recovery option by promoting the read replica in another region as the primary node in case of a failure. Option A provides high availability but lacks a quick disaster recovery mechanism. Option B relies on backups for disaster recovery, which may not meet the RPO and RTO requirements as effectively as promoting a read replica. Option D suggests migrating to Cloud Spanner, which, while offering high availability and global scalability, requires significant changes to the schema and application, making it less ideal for a straightforward migration aiming to maximize uptime with minimal changes.
Ultimate access to all questions.
No comments yet.
How can you ensure maximum uptime for your business-critical application when migrating it to Google Cloud, using a managed service to deploy a highly available PostgreSQL database that meets a 30-minute RTO and RPO requirement?
A
Deploy Cloud SQL for PostgreSQL in a regional configuration. Create a read replica in a different zone in the same region and a read replica in another region for disaster recovery.
B
Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Take periodic backups, and use this backup to restore to a new Cloud SQL for PostgreSQL instance in another region during a disaster recovery event.
C
Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-region read replica, and promote the read replica as the primary node for disaster recovery.
D
Migrate the PostgreSQL database to multi-regional Cloud Spanner so that a single region outage will not affect your application. Update the schema to support Cloud Spanner data types, and refactor the application.