CLOUD-DIGITAL-LEADER practice question 20 of 35

An organization wants to migrate a workload to the cloud without changing the application code or architecture Which migration path describes this approach?

Full set: 411 questions
Answer options
A: Replatformed
B: Rehosted Correct answer
C: Reimagined
D: Refactored
Correct Answer:
B. Rehosted
Explanation

Rehosting—often called “lift-and-shift”—moves a workload from on-premises to cloud infrastructure exactly as-is, with no changes to the application’s code, runtime, or overall architecture. Google Cloud’s migration guidance lists rehost as the strategy chosen when the goal is speed and minimal risk, because only the hosting environment changes; binaries, libraries, and configuration remain untouched. Therefore, a migration that keeps the application code and architecture intact is unequivocally a Rehosted approach.

Why Incorrect

A. Replatformed – Requires limited code/config changes to adopt managed services (e.g., move from self-managed MySQL to Cloud SQL); not “no change.”
C. Reimagined – Implies complete redesign to exploit cloud-native capabilities (micro-services, serverless); far beyond lift-and-shift.
D. Refactored – Entails significant code modification to improve scalability or maintainability; contradicts “without changing the application code or architecture.”

References

1. Google Cloud. “Migration to Google Cloud: Choosing your migration path,” Section ‘Rehost (lift and shift)’, para. 1-2. https://cloud.google.com/architecture/strategies-for-migration

2. Google Cloud. “Application migration to Google Cloud,” Table 1: “The 4Rs of migration,” row ‘Rehost’. 2023-09-01 edition.

3. Google Cloud Architecture Framework, Foundation > Migration strategies, bullet ‘Rehost’. (document ID: gcloud-arch-framework-v5, p. 27).

Scroll to Top