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 is planning the migration of a mission-critical three-tier enterprise workload from an on-premises data center to Google Cloud. Architectural dependency mapping reveals the following characteristics:
Preliminary testing shows that splitting the application tier in Google Cloud from an on-premises database introduces unacceptable cross-premises network latency.
Which migration sequencing and data synchronization strategy should the cloud architect recommend?
This strategy employs dependency-aware migration wave planning combined with continuous data replication using Change Data Capture (CDC) to migrate tightly coupled tiers without causing cross-premises latency penalties or extended downtime.

Decoupling components that have hard sub-5 ms latency dependencies across a hybrid WAN link inevitably leads to application performance degradation. By keeping dependent tiers within the same migration wave and leveraging continuous CDC data streaming, the architecture minimizes both performance risk and cutover downtime.
This approach sequences downstream analytics pipelines into the initial migration wave and utilizes offline cold backups (full database dumps) to move the primary database during the final transition.
The database were small, non-critical, and had an approved multi-hour maintenance window allowing a complete cold-stop migration.
This strategy migrates the database tier first using periodic scheduled export scripts while leaving the application tier on-premises, routing application queries across public endpoints.
The application tier were completely stateless, already refactored into edge APIs, and read from local caching nodes rather than making synchronous transactional database calls.
This approach splits the migration across two phases by rehosting the application tier in Google Cloud in Wave 1 while maintaining the source database on-premises, attempting to reconcile data state asynchronously via periodic flat file exports.
The workload were an asynchronous batch processing pipeline that processes daily batches with no real-time database query latency constraints.
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