Cloud infrastructure decisions now represent the single largest technology investment most enterprises make — often 15-25% of total IT budgets. In our experience reviewing 400+ technology cases, cloud strategy questions have tripled in frequency since 2022, appearing across MBB and Big 4 interviews alike. These cases test whether you can think beyond “move to cloud” and reason about architecture tradeoffs, vendor economics, and organizational readiness.
Why Cloud Cases Are Different from General Tech Cases
Cloud infrastructure cases sit at the intersection of technology and operations. Unlike pure digital strategy cases that focus on market positioning, cloud cases demand quantitative rigor around total cost of ownership (TCO), migration risk modeling, and capacity planning. Interviewers expect you to understand that “cloud” is not one decision but a portfolio of architecture choices with compounding implications.
The key differentiator: cloud cases require you to balance short-term migration costs against long-term operational flexibility. Based on our analysis of 150+ cloud-specific cases, candidates who structure around the migration-operations-optimization lifecycle outperform those who treat it as a one-time strategic choice.
Core Case Archetypes
| Archetype | Typical Prompt | Key Framework |
|---|---|---|
| Migration Decision | “Should Client X migrate their on-premise ERP to cloud?” | TCO analysis + risk-adjusted timeline |
| Multi-Cloud Strategy | “Client uses AWS and Azure — should they consolidate?” | Vendor dependency vs. best-of-breed tradeoff |
| Cost Optimization | “Cloud spend grew 40% YoY but revenue grew 12% — diagnose” | Unit economics + resource utilization audit |
| Architecture Modernization | “Client’s monolithic app can’t scale — recommend path forward” | Strangler fig pattern + phased decomposition |
| Edge/Hybrid | “Client needs low-latency processing at 200 retail locations” | Workload placement matrix + connectivity constraints |
The Cloud Migration Decision Framework
When assessing whether and how to migrate, structure your analysis across four dimensions:
flowchart TD
A[Cloud Migration Decision] --> B[Workload Assessment]
A --> C[Economic Analysis]
A --> D[Risk & Compliance]
A --> E[Organizational Readiness]
B --> B1[Application complexity]
B --> B2[Data sensitivity]
B --> B3[Integration dependencies]
C --> C1[Current TCO baseline]
C --> C2[Target state TCO]
C --> C3[Migration investment]
D --> D1[Regulatory requirements]
D --> D2[Data residency]
D --> D3[Downtime tolerance]
E --> E1[Skills gap assessment]
E --> E2[Change management]
E --> E3[Vendor management capacity]
In practice, most consulting cases focus heavily on the economic analysis dimension. A strong answer quantifies the TCO comparison by separating infrastructure costs (compute, storage, networking), operational costs (staffing, licensing, maintenance), and opportunity costs (speed-to-market, scalability ceiling).
Migration Approaches: The 6 Rs
Consulting firms frequently test whether candidates understand migration is not binary. The industry-standard “6 Rs” framework provides a structured vocabulary:
| Strategy | Description | When to Use | Typical Cost |
|---|---|---|---|
| Rehost | Lift-and-shift to cloud VMs | Legacy apps with low complexity | Low upfront |
| Replatform | Minor optimization during migration | Apps needing managed services | Medium |
| Refactor | Re-architect for cloud-native | Core revenue-generating apps | High |
| Repurchase | Replace with SaaS equivalent | Commodity functions (HR, CRM) | Variable |
| Retain | Keep on-premise | Regulated or latency-critical | Minimal |
| Retire | Decommission | Redundant or unused applications | Savings |
Based on our experience coaching candidates, the strongest answers don’t just list these options — they apply them selectively to a client’s application portfolio, creating a phased roadmap that balances quick wins (rehost) with strategic bets (refactor).
Key Metrics Interviewers Expect You to Know
Cloud economics differ fundamentally from on-premise infrastructure. Demonstrate fluency with these metrics:
- TCO per workload: Infrastructure + operations + migration amortization, compared across 3-5 year horizons
- Cloud unit economics: Cost per transaction, cost per user, cost per GB stored — the foundation for diagnosing runaway spend
- Resource utilization rate: On-premise averages 15-25% utilization vs. well-optimized cloud at 60-75%
- Migration velocity: Applications migrated per quarter, adjusted for complexity tier
- Time-to-value: Weeks from migration completion to measurable operational improvement
Common Pitfalls in Cloud Cases
After reviewing hundreds of candidate responses, these are the three most common failure modes:
Treating cloud as purely a cost play: Cloud migration often increases short-term costs by 20-30% before optimization. Candidates who promise immediate savings lose credibility. The real value proposition combines operational agility, scalability, and reduced time-to-market.
Ignoring organizational readiness: In our experience, 60% of failed cloud migrations fail due to people and process issues, not technology. Always address the skills gap, change management, and operating model implications.
Forgetting vendor lock-in economics: Multi-year cloud commitments (reserved instances, enterprise agreements) reduce costs 30-50% but create switching costs. Interviewers expect you to quantify this tradeoff explicitly.
Key Takeaways
- Cloud cases test operational and financial reasoning, not just technology knowledge — always lead with economics
- Structure migration decisions across four dimensions: workload assessment, economic analysis, risk/compliance, and organizational readiness
- Apply the 6 Rs framework selectively to create phased migration roadmaps, not blanket recommendations
- Quantify TCO across 3-5 year horizons, separating infrastructure, operations, and opportunity costs
- Address organizational readiness explicitly — most migration failures are people problems, not technology problems
- Demonstrate awareness of vendor lock-in tradeoffs between cost optimization and strategic flexibility
Ready to practice cloud strategy cases? Explore technology industry cases in our case library, or sharpen your operational thinking with our operations case framework. For real-time feedback on your case delivery, try our AI Mock Interview.