Q: You are tasked with migrating a massive legacy application from on-premises to the cloud. You cannot afford to refactor the code (Cloud Native). Describe the "Lift and Shift" (Rehosting) approach and its major operational downsides.
Lift and Shift (Rehosting) means cloning the physical/virtual machines byte-for-byte directly into identical cloud VMs (like AWS EC2) with zero architectural changes to the application itself.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our engineering organization, DevOps culture meant aligning developer speed with site reliability. The interviewer is testing: Cloud migration patterns, operational trade-offs, technical debt.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Lift and Shift (Rehosting) means cloning the physical/virtual machines byte-for-byte directly into identical cloud VMs (like AWS EC2) with zero architectural changes to the application itself.
- Cost: Legacy apps typically expect vertical scaling (massive servers) running 24/7. You miss out on the cost savings of auto-scaling, pausing idle resources, or using cheap serverless compute.
- Resilience: The app likely expects persistent, permanent local disks and fixed IP addresses, making it fragile if the underlying EC2 instance is randomly terminated by the cloud provider. It physically cannot utilize cloud-native elasticity.
Remediation & Permanent Safeguards
Major Operational Downsides: Because the app is not "Cloud Native", you inherit all on-premise technical debt at cloud prices.
- Cost: Legacy apps typically expect vertical scaling (massive servers) running 24/7. You miss out ...
- Resilience: The app likely expects persistent, permanent local disks and fixed IP addresses, maki...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Engineering bespoke in-house developer tools instead of adopting standardized platform Golden Paths when configuring General tasked migrating Bespoke internal tools create long-term maintenance debt and fragmented workflows, whereas standardized Golden Paths accelerate delivery.
- Overlooking infrastructure cost visibility and FinOps allocation tagging across multi-tenant environments when configuring General tasked migrating Without granular resource tagging, engineering organizations cannot attribute cloud infrastructure costs to specific teams or business units.
- Failing to define explicit Service Level Objectives (SLOs) and Error Budgets to balance feature velocity with reliability when configuring General tasked migrating Without agreed SLOs, engineering and product teams lack an objective data-driven framework to prioritize technical debt over new features.
- Neglecting automated continuous drift detection between declarative configuration and deployed cloud state when configuring General tasked migrating Unmanaged drift accumulates over time, causing future automated deployments to fail or overwrite emergency manual adjustments.