professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Your team is executing a zero-downtime database migration from an on-premises sharded relational database to Cloud Spanner. The forward migration strategy uses continuous Change Data Capture (CDC) replication to keep Cloud Spanner in sync with the source database.
To ensure business continuity during cutover, you must implement a robust fallback mechanism that allows the application to fail back to the source database with minimal downtime and without data loss if issues occur after cutover.
Which strategy should you implement for the reverse replication and validation framework?
Reverse replication is an essential continuity mechanism in large-scale database migrations that streams changes made in the new target database (such as Cloud Spanner) back to the legacy source system. This enables immediate fallback with minimal downtime if performance degradation or functional defects arise post-cutover.
Cloud Spanner's distributed architecture requires explicit ordering and transformation reversal to write back cleanly to a traditional single-node or sharded relational database. Capturing change streams and temporally ordering events provides a deterministic, zero-data-loss rollback path.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
StudyCerts
StudyCerts