A company is planning to migrate applications to the AWS Cloud. During a system audit, the company finds that its content management system (CMS) application is incompatible with cloud environments. W

Question

Options

• ARetire
• BRehost
• CRepurchase
• DReplatform
• ERefactor

• A
  3% (1)
• B
  71% (22)
• D
  10% (3)
• E
  16% (5)

Explanation

Migration Strategy Explanation

Rehost (B) and Repurchase (C) are correct because they require the least effort when dealing with an incompatible application. Rehost ("lift and shift") moves the application as-is to the cloud with minimal changes, avoiding compatibility issues by simply running it on cloud infrastructure. Repurchase involves replacing the incompatible CMS with a cloud-native SaaS alternative (e.g., moving to a vendor-hosted CMS like HubSpot or WordPress.com), which sidesteps compatibility problems entirely without custom development.

Why the distractors are wrong:

• Retire (A) means decommissioning the application entirely - not a migration strategy
• Replatform (D) requires some optimization and code/configuration changes, meaning more effort than rehosting
• Refactor (E) involves the most effort, requiring significant rearchitecting of the application to be cloud-native

Memory Tip

Think of the "6 R's" ranked by effort: Retire → Rehost → Repurchase (low effort) → Replatform (medium) → Refactor (high). When something is incompatible, you either move it as-is (Rehost) or swap it out entirely (Repurchase) - both avoid touching the problematic code.

No community discussion yet for this question.