Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs a mission-critical database workload on a primary Cloud SQL instance located in us-central1. To achieve a low Recovery Time Objective (RTO) and Recovery Point Objective (RPO) in the event of a regional disaster, the team configured a cross-region disaster recovery (DR) replica in us-east1 and connected their applications using a Cloud SQL DNS write endpoint.
A sudden regional outage occurs in us-central1, rendering the primary database instance completely inaccessible.
Which failover procedure should the cloud architect execute to restore write operations in the secondary region with minimal application downtime?
A switchover is a controlled, planned operation used to swap the roles of the primary instance and a read replica, typically for planned maintenance or disaster recovery drills.
The organization were conducting a scheduled disaster recovery drill or migrating workloads between regions during planned maintenance without downtime.
gcloud sql instances promote-replica REPLICA_NAME --failover), allowing the DNS write endpoint to automatically point to the new primary instance.Cloud SQL replica failover is an automated disaster recovery mechanism that promotes an existing cross-region read replica to assume the role of the primary instance immediately during an unexpected outage or disaster.
gcloud sql instances promote-replica REPLICA_NAME --failover immediately promotes the replica to a standalone primary database without waiting for synchronization steps that require an accessible primary instance.
This approach directly satisfies aggressive Recovery Time Objectives (RTO) by minimizing administrative overhead and eliminating manual configuration changes across application fleets.
us-east1 and update the application connection strings to point to the new IP address.Backup restoration involves creating a new Cloud SQL database instance from an automated or on-demand backup stored in Cloud Storage.
There was no pre-existing cross-region read replica, or if the database sustained catastrophic logical corruption across all active replicas.
gcloud sql instances promote-replica REPLICA_NAME) without the failover flag, then delete the failed primary instance.Standard replica promotion decouples a read replica from its primary instance and converts it into a standalone read/write database without enabling disaster recovery failover workflows.
--failover or ENABLE_REPLICA_FAILOVER=true), Cloud SQL treats the action as a permanent detachment rather than a DR event, meaning the DNS write endpoint will not automatically resolve to the promoted instance.You wanted to permanently fork a read replica to create an independent development or analytics database isolated from the production cluster.
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