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 phased migration of several multi-tier enterprise applications from an on-premises VMware data center to Google Cloud. A comprehensive dependency assessment reveals the following constraints:
How should the cloud architect organize the migration waves and execution strategy to minimize downtime and operational disruption?
Migration wave planning is the systematic grouping and sequencing of workloads during a cloud migration. Rather than moving systems at random or all at once, architects evaluate application dependency mappings, technical constraints, and business operational windows to bundle workloads into logical, risk-managed batches.
This strategy directly follows foundational migration best practices for Google Cloud. It balances technical network dependencies with business constraints and operational efficiency, ensuring minimal business disruption and avoiding redundant power cycles.
Refactoring involves modifying application code and database architectures to leverage cloud-native services (such as Cloud Spanner or Bigtable). This approach redesigns schemas, queries, and connection logic to achieve horizontal scalability.
The project prioritized modernizing legacy relational schemas into globally distributed cloud-native databases, and applications were already architected to tolerate cross-cloud network latency.
Replatforming frontend and application tiers to containers involves extracting application runtimes and packaging them into container images deployed on services like Google Kubernetes Engine (GKE) or Cloud Run, without completely redesigning core application code.
The application had loosely coupled asynchronous components communicating via message queues rather than latency-sensitive synchronous database calls.
Arbitrary sequencing migrates virtual machines based on superficial criteria (such as alphabetical naming conventions or subnet ranges) without analyzing application-level dependencies, business schedules, or technical prerequisites.
All virtual machines in scope were completely independent, standalone hosts with no inter-dependencies, shared services, or change management 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 Validated