Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise runs a mission-critical Cloud SQL for PostgreSQL database deployed across multiple Google Cloud regions:
db-central): Deployed in us-central1 with High Availability (HA) enabled.db-west): Cross-region read replica in us-west1.db-east): Cross-region read replica in us-east1.A catastrophic outage renders the entire us-central1 region unavailable. You need to execute an emergency failover to promote db-west to the new primary while minimizing data loss, redirecting application traffic with minimal downtime, and restoring read and HA topology.
Which operational procedure should you execute?
db-west, promote db-west using replica failover so the DNS write endpoint updates, enable High Availability on the newly promoted primary, and recreate the db-east replica pointing to db-west under a new instance name.In Cloud SQL for PostgreSQL, cross-region replication operates asynchronously. When an unplanned regional disaster incapacitates the primary instance in us-central1, disaster recovery requires manually or programmatically promoting a designated cross-region read replica to assume the read-write primary role.
db-west via a PostgreSQL client to check pg_catalog.pg_last_wal_receive_lsn() and pg_catalog.pg_last_wal_replay_lsn() verifies that the replica has fully applied all write-ahead log (WAL) transactions received from the primary before the outage, preventing stale or partially applied state upon promotion.us-west1 without necessitating application redeployment.db-east replica of the failed primary must be deleted and recreated pointing to the new us-west1 primary using a distinct instance name.This procedure correctly addresses data consistency verification, dynamic application routing via DNS endpoints, and the architectural requirement to rebuild orphaned sibling read replicas from the new primary.
db-central and db-west, preserve the existing db-east read replica connection, and rely on Point-in-Time Recovery (PITR) during the 15-minute promotion window.This option attempts a graceful switchover (role reversal) with the unavailable primary in us-central1, expects db-east to remain attached, and relies on Point-in-Time Recovery (PITR) immediately after failover.
db-east replica will not maintain its replication connection because its upstream master (db-central) is defunct.This were a planned maintenance window with a fully operational primary in us-central1 undergoing controlled database patching.
db-west to enforce RPO=0, retain the instance name of db-east when re-attaching it to db-west, and update local DNS records to point client traffic to db-west.This option claims cross-region replication guarantees zero data loss (RPO=0), attempts to re-attach db-east using its old instance name, and relies on custom local DNS updates.
RPO=0 (zero data loss) if transactions committed to db-central were not replicated before the outage.The cluster used synchronous streaming replication across zones within the same local region and allowed reusing identical instance identifiers.
db-west using gcloud CLI, update client connection strings to the static IP address of db-west, and allow Cloud SQL to automatically switch the replication master of db-east to db-west.This option initiates an unverified promotion of db-west, assumes manual IP reconfiguration for the application tier, and assumes that Google Cloud automatically redirects existing sibling read replicas to replicate from the new primary.
db-east) to a newly promoted cross-region instance. Sibling replicas become orphaned and must be deleted and recreated explicitly from the new primary.db-west introduces avoidable downtime, as the architecture already implements Cloud SQL DNS write endpoints that update dynamically upon replica promotion.pg_last_wal_replay_lsn) risks promoting a replica before all locally received transactions are applied.The application did not utilize DNS write endpoints, and if Cloud SQL supported automatic cascading replica re-pointing across regions without manual recreation.
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 Validated