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.
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?
Scheduled batch synchronization periodically dumps table snapshots or transaction increments to Cloud Storage (via Dataflow or Avro/CSV export tools) and imports them into a target destination at set intervals.
The workload was an analytical reporting database or data lake where hourly data freshness was acceptable and zero-downtime transactional fallback was not required.
Application dual-writing involves modifying the application service code to synchronously or asynchronously issue write operations to both the legacy source database and the target cloud database simultaneously.
A system required immediate, application-coordinated data mirroring between two identical schemas with distributed transaction coordinator frameworks (like 2PC) already in place.
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.
Bidirectional replication attempts to stream changes in both directions simultaneously across two active database endpoints without intermediate synchronization or cycle detection.
An active-active multi-master replication topology with built-in loop suppression and collision detection was explicitly configured between identical database engines.
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