What does it mean by a "lift and shift" approach regarding moving applications to the cloud?

Question

Options

• ARetiring the application and replacing it with a different application
• BCode changes and user facing changes
• CNo code changes and no user facing changes
• DCode changes and no user facing changes

• A
  3% (1)
• B
  3% (1)
• C
  94% (29)

Explanation

Lift and shift (also called "rehosting") means taking an application exactly as it is and moving it to the cloud infrastructure - no code modifications, no changes to the user interface or experience (C). The application simply runs on cloud servers instead of on-premises servers, making it the fastest and lowest-risk migration path.

Why the distractors are wrong:

• A describes retire and replace (or rearchitect), a completely different migration strategy where the old app is abandoned.
• B describes a refactor or re-architect approach, where developers modify both the codebase and potentially the UX to take advantage of cloud-native features.
• D is a partial truth that describes a backend refactor - code changes happen, but users don't notice; this is not lift and shift.

Memory tip: Think of physically lifting a server out of your data center and shifting it into a cloud data center - nothing about the software changes, only where it runs.

No community discussion yet for this question.