5 exercises — practice structuring strong English answers to cloud migration architect interview questions: 6Rs decision framework, migration wave planning, TCO analysis, Cloud Adoption Framework, and multi-region trade-offs.
How to structure cloud migration architect interview answers
6Rs questions: frame as a decision framework → give criteria for each R → name the diagnostic assessment process → mention Retire as 10–20% of estate
Wave planning questions: open with risk management framing → Wave 0 foundation → pioneer wave rationale → dependency-ordered main waves → stakeholder communication matrix
TCO questions: name all three cost buckets including transition → call out egress and dual-running → present 3-year and 5-year views
CAF questions: name all six perspectives → characterise it as an assessment tool → note People and Governance as the underestimated gaps
Multi-region questions: establish RPO and RTO first → map requirements to architecture options → name three trade-offs explicitly → raise data sovereignty
0 / 5 completed
1 / 5
The interviewer asks: "Walk me through the 6Rs of cloud migration. How do you decide which R applies to a given application?" Which answer best demonstrates migration vocabulary?
Option B is strongest: it opens by correctly framing the 6Rs as a decision framework (not a checklist), gives a precise definition for each R with specific best-fit criteria that reflect real migration experience, provides the 10–20% Retire estimate that shows portfolio-level thinking, and closes with the structured diagnostic approach that connects to migration wave planning. The 'application owner has left' criterion for Rehost is a practitioner insight that shows genuine field experience. Key vocabulary:Rehost — lift-and-shift with no code changes. Replatform — targeted optimisations without full re-architecture. Refactor/Re-architect — redesign for cloud-native services. Repurchase — move to SaaS. Retire — decommission. Retain — keep on-premises with planned review. Migration wave — a grouped batch of applications migrated together. Options C and D name the criteria but lack the 'what makes each R the right choice' level of detail.
2 / 5
The interviewer asks: "How do you plan and communicate a migration wave sequence?" Which answer best demonstrates migration wave planning vocabulary?
Option B is strongest: it frames wave planning as risk management (not just project sequencing), introduces the underestimated Wave 0 foundation phase, explains the counterintuitive principle of starting with teaching applications rather than important ones (and why), specifies the dependency graph as the ordering principle, and provides a complete stakeholder communication framework with specific timing and content for different audiences. The 'teaching applications reveal gaps' insight is a practitioner-level perspective. Key vocabulary:Migration wave — grouped batch of applications migrated together. Landing zone — pre-configured cloud environment baseline. Dependency graph — map of inter-application dependencies. RACI — Responsible, Accountable, Consulted, Informed stakeholder matrix. Cut-over — the moment traffic switches from source to target environment. Options C and D are accurate but do not explain the reasoning behind Wave 1 pioneer selection.
3 / 5
The interviewer asks: "How do you build a TCO analysis for a cloud migration business case?" Which answer demonstrates the most rigorous approach?
Option B is strongest: it opens by identifying the most common mistake in TCO analysis (ignoring transition costs), provides specific line items within each of three cost buckets with real-world calibration data (30–50% for data centre overhead, 3–6 months dual-running), names egress as the frequently underestimated cost, introduces risk-adjusted value as a fourth dimension, and explains why both 3-year and 5-year views are needed. The data centre overhead percentage and the dual-running period estimate show genuine architecture experience. Key vocabulary:TCO (Total Cost of Ownership) — all costs over a technology's full lifetime. Reserved Instance — commitment-based cloud pricing at 30–72% discount. Egress cost — cloud charges for data transferred out of the cloud region. Dual-running — operating both old and new environments simultaneously during migration. Refactor-track — applications requiring re-architecture for cloud-native deployment. Options C and D are accurate but do not include the risk-adjusted value dimension or explain the year 1 vs. year 2–3 economics pattern.
4 / 5
The interviewer asks: "What is the Cloud Adoption Framework and how do you use it in a migration engagement?" Which answer best demonstrates CAF vocabulary?
Option B is strongest: it correctly frames the CAF as an assessment and gap analysis tool (not a prescriptive checklist), gives accurate descriptions of all six perspectives with their specific focus areas, provides the practitioners' insight that People and Governance are typically the least-prepared dimensions (not Platform and Security as clients assume), specifies a realistic timeline for the readiness workshop (weeks 1–4), and closes with the executive communication value of CAF framing — signalling that migration is organisational transformation. Key vocabulary:Cloud Adoption Framework (CAF) — structured cloud transformation methodology from major cloud providers. Readiness workshop — multi-stakeholder assessment of cloud readiness. Gap analysis — identifying differences between current and target states. Organisational change management — structured approach to managing people-side of transformation. Options C and D are accurate but do not explain why CAF is useful for executive communication or provide the People/Governance insight with its reasoning.
5 / 5
The interviewer asks: "How do you discuss multi-region architecture trade-offs with a client?" Which answer best demonstrates the vocabulary and communication approach?
Option B is strongest: it correctly frames the conversation as starting with business requirements (RPO/RTO), not technology options, provides specific threshold examples that connect requirements to architecture choices (near-zero RPO → active-active; 15-min RPO → active-passive), structures three named trade-offs with specific quantification (active-active doubles cost, warm standby runs at 20–25%), introduces the consistency vs. availability trade-off for concurrent writes — a technically sophisticated constraint most answers omit — and adds data sovereignty as a constraint that can override architecture preferences. Key vocabulary:RPO (Recovery Point Objective) — maximum acceptable data loss measured in time. RTO (Recovery Time Objective) — maximum acceptable service downtime. Active-active — all regions simultaneously serve live traffic. Active-passive — one primary region, one standby. Warm standby — scaled-down standby running continuously. Data sovereignty — legal constraints on data residency and cross-border replication. Options C and D are accurate but do not introduce the consistency constraint for active-active writes.