Exam AWS Certified Cloud Practitioner CLF-C02 topic 1 question 481 discussion

It's not (E) Refactor, requiring significant development effort and increased migration timelines. I don't think (A) Retire is an option only because the question states which strategies will help the company migrate the CMS application with the LEAST effort. Choosing to Retire will not help them migrate. This leaves us with Rehost, Repurchase, and Replatform. Based on the following and a process of elimination, my choices would be B and C. B) Rehost - Benefits: Rapid migration, minimal code changes, reduced risk. May not fully leverage cloud-native features, potential for suboptimal cost and performance. C) Repurchase - Benefits: Rapid migration, reduced maintenance burden, potential for cost savings. Limited customization, potential for data migration challenges. D) Replatform - Benefits: Balance of speed and optimization, leverage cloud benefits. Requires careful planning, potential for increased complexity.

B. Rehost (Lift and Shift) Least effort strategy to migrate the app as-is No code changes; just move the app to EC2 or similar compute on AWS Ideal for legacy or cloud-incompatible application D. Replatform Requires some minor adjustments, like changing the operating system or database, but keeps the core architecture unchanged Still considered low effort compared to refactoring or repurchasing A good choice if slight tweaks are needed to make the CMS cloud-compatible A. Retire Removes the app — does not migrate it Not a valid answer since the question is about migration, not decommissioning C. Repurchase Replacing the CMS with a SaaS solution involves medium to high effort due to data migration, integration, and retraining E. Refactor Involves rebuilding or re-architecting the app High effort — not suitable when minimal changes are desired

true for me

content management system (CMS) application is incompatible with cloud environments → (A) Retire → (C) Repurchase Replatform involves some code/config changes

the traditional "lift and shift" (Rehost) or even "lift, tinker, and shift" (Replatform) strategies become difficult or impossible without significant re-engineering. Re-architecting (Refactor) requires the most effort.

The two migration strategies that will help the company migrate the CMS application with the LEAST effort are: B. Rehost D. Replatform Explanation: Rehost (Lift-and-Shift): This strategy involves moving the application to the cloud with minimal or no changes. Replatform (Lift-Tinker-and-Shift): This strategy involves making minor optimizations to the application to make it compatible with the cloud environment. Why not the other options? A. Retire: This means decommissioning the application, which is not applicable here since the company wants to migrate the CMS. C. Repurchase: This involves switching to a different product (e.g., a SaaS CMS). While it may reduce effort in some cases, it is not necessarily the least effort if the company wants to retain its existing CMS. E. Refactor: This involves re-architecting the application to be cloud-native, which requires significant effort and is not the least effort option.

Repurchase “drop and shop” • Moving to a different product while moving to the Cloud • Often you move to a SaaS platform • Expensive in the short term, but quick to deploy • Example: CRM to Salesforce.com, HR to Workday, CMS to Drupal

By a process of elimination... A) is out, because the 2nd paragraph makes it clear the company wants to continue to use a CMS application in a cloud environment, and B) is out, because the audit determined that the existing application is "... incompatible with cloud environments," and E) is out, because it doesn't meet the "LEAST effort" requirement. That leaves (C) and (D).

It all depends on if the CMS is in-house or 3rd party and if they want to keep it in-house or 3rd party. Either way, I believe retiring the CMS is a given. But the other choice, not so much.

It can't be B: the application is INCOMPATIBLE with cloud environments. C and D are the least effort option, in this case.

A. Retire: If the application is outdated or not necessary for future operations, retiring it can be the easiest and most cost-effective strategy. C. Repurchase: This strategy is also known as "drop and shop," where you replace your existing application with a cloud-based solution. It’s often easier than modifying or rehosting an incompatible application.

"Incompatible with cloud environments" means the CMS cannot be migrated to the cloud. Rehost does not work.

probably BC please help with discussion on 482~498. Thanks.

I think it should be A and B

A. Retire C. Repurchase Retire: If the CMS application is not compatible and not necessary for business operations, the company could choose to retire it. This would involve decommissioning the application and not replacing it. Repurchase: This strategy, also known as "drop and shop", involves moving to a different product. The company could choose to replace the incompatible CMS with a cloud-compatible CMS. This could be a SaaS solution or a CMS designed to run in the cloud. This strategy typically requires less effort than rehosting, replatforming, or refactoring, as it involves setting up a new system rather than modifying the existing one.

I think it's B and C

Please someone say what is the correct answer. I don't believe in any of those given "correct" answers as most of them are plain wrong