A company wants to move a large on-premises application to the cloud. How would you decide between moving it as is and re-architecting it?

What the interviewer is looking for

• This question tests cloud architecture & core services. Chooses compute, storage and database services with clear reasons about scale, cost, management effort and trade-offs.
• Strong answers: Assesses business goals, timeline, dependencies, licensing and cost; often moves first then modernises in stages; plans cutover and rollback.
• Likely follow-up: What are the biggest risks in a migration like that?

Another way it may be asked: A business has an old app on its own servers and wants it in the cloud. Do you just copy it over or rebuild it, and how do you decide?

A structure to follow: Frame, structure, analyse, recommend

1. Step 1

   Frame

   Restate the goal and ask what success is and what the constraints are.

2. Step 2

   Structure

   Split the problem into a few separate parts you can check one by one, and say what you will look at first and why.

3. Step 3

   Analyse

   Reason with the information you have, state your assumptions out loud, and say what data would change your mind.

4. Step 4

   Recommend

   Give a clear recommendation, the main risk, and the first step you would take.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Listing ideas without choosing between them.
• Hiding assumptions instead of stating them.
• Finishing without a recommendation.

How to practise it

Answer in four spoken parts, one per step, then check you ended on a recommendation.

Related questions

• If you had to host a simple web app with a database in the cloud, which services would you pick, and why?
• What does least privilege mean in cloud access management, and how would you apply it to a new developer joining the team?
• Explain the difference between a public and a private subnet, and what kinds of resources you would put in each.
• An app server in a private subnet cannot reach an external payment service. How do you troubleshoot that connection?
• How do you structure infrastructure code so several teams and environments can reuse it without stepping on each other?

Browse all questions