Migration And Modernization Sequencing — GCP Professional Cloud Architect (PCA)
The Migration Strategy Lives in the Workload Description
The exam encodes the answer in how the workload is described, not in the timeline pressure. 'Legacy binary with undocumented dependencies' signals rehost to Compute Engine. 'Containerised app, no refactoring budget' signals replatform via Migrate for Anthos to GKE. 'Stateless service, team adopting serverless' signals refactor to Cloud Run. Timeline pressure narrows the option set but never overrides workload fit — a tight deadline with a containerised workload still eliminates GCE as the architecturally correct answer.
What This Pattern Tests
Migration questions test sequencing discipline. The exam gives a multi-component system and asks what moves first. Data stores migrate first (everything depends on them), application logic second (depends on data), and presentation last (depends on everything). The answer follows dependency order, not complexity order.
Decision Axis
Dependency graph determines migration order, not migration difficulty.
Associated Traps
More Top Traps on This Exam
Decision Rules
When a workload is already containerized, stateless, and HTTP-only, should the team replatform to GKE via Migrate for Anthos (leveraging Kubernetes-native packaging) or deploy directly to Cloud Run to satisfy both the migration timeline and the no-cluster-management constraint?
Whether to replatform the workload to GKE via Migrate for Anthos, or rehost it to Compute Engine VMs via Migrate to Virtual Machines — determined by reading the workload-state cue (already containerized and Helm-chart-ready) against the operational-overhead reduction constraint, not by the deadline alone.
When a workload is stateless AND the business explicitly mandates eliminating VM operational overhead, lift-and-shift to Compute Engine is architecturally disqualified regardless of migration speed — the correct governing decision is to replatform to Cloud Run, trading a modest containerization effort for permanent elimination of node and OS management.
When the workload is already containerised and Helm-packaged, and the team has GKE operational expertise, select replatforming via Migrate for Anthos to GKE over rehosting to Compute Engine VMs — the containerised state eliminates the primary justification for lift-and-shift, and GKE expertise removes the team-readiness blocker that would otherwise favour rehosting.
Domain Coverage
Difficulty Breakdown