Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam CLF-C02 Topic 3 Question 28 Discussion

Actual exam question for Amazon's CLF-C02 exam
Question #: 28
Topic #: 3
[All CLF-C02 Questions]

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.

Which migration strategies will help the company to migrate the CMS application with the LEAST effort? (Select TWO.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Rehosting ('lift and shift') is a migration strategy where applications are moved to the cloud with minimal changes, making it the least effort-intensive method for applications incompatible with the cloud. Repurchasing involves moving to a different product, often a SaaS solution, which can also minimize migration effort by avoiding the need for application-level changes. Retiring, replatforming, and refactoring require significant effort either in terms of analyzing and shutting down the application, making changes to the underlying platform, or redesigning the application architecture, respectively. References:

AWS Migration Strategies


Contribute your Thoughts:

Hillary
2 months ago
Ah, the classic 'lift and shift' (B) and 'lift, tinker, and shift' (D) strategies. Always a safe bet when you don't want to put in too much effort. Hey, at least the CMS won't have to worry about getting seasick during the migration!
upvoted 0 times
Keena
1 months ago
Sounds good to me. Let's make sure the CMS application sails smoothly into the AWS Cloud!
upvoted 0 times
...
Sabra
1 months ago
Agreed, those options will require the least effort and ensure a smoother migration process.
upvoted 0 times
...
Stephaine
2 months ago
I think we should go with the rehost (B) and replatform (D) strategies for the CMS application.
upvoted 0 times
...
...
Remedios
2 months ago
But retiring and replatforming seem like the most straightforward options to me.
upvoted 0 times
...
Hubert
2 months ago
I disagree, I believe options B and E would require less effort.
upvoted 0 times
...
Remedios
2 months ago
I think we should choose options A and D.
upvoted 0 times
...
Dana
2 months ago
I think repurchasing a new CMS is a bit extreme. Why spend the money when you can just migrate the existing one? B and D are the way to go.
upvoted 0 times
Natalya
1 months ago
Rehosting and replatforming are definitely the best options to minimize effort during the migration process.
upvoted 0 times
...
Bea
1 months ago
I think focusing on rehosting and replatforming will be the most efficient way to migrate the CMS application.
upvoted 0 times
...
Silvana
2 months ago
Rehosting and replatforming would definitely save time and effort compared to repurchasing.
upvoted 0 times
...
Vallie
2 months ago
I agree, repurchasing seems unnecessary. Rehosting and replatforming are more practical options.
upvoted 0 times
...
...
Carin
3 months ago
I'm not sure retiring the CMS is a good idea. That would just mean replacing it entirely, which might be more work than migrating it. E could be an option, but it might be overkill for this situation.
upvoted 0 times
Gregoria
2 months ago
B) Rehost
upvoted 0 times
...
Marguerita
2 months ago
A) Retire
upvoted 0 times
...
...
Rosio
3 months ago
B and D seem like the best options here. Rehosting the CMS to the cloud and then replatforming it would require the least effort to get it running in the cloud.
upvoted 0 times
Lisbeth
2 months ago
Definitely, those two options would minimize the effort needed for the migration process.
upvoted 0 times
...
Lisbeth
3 months ago
I agree, rehosting and replatforming would be the most efficient way to migrate the CMS application to the AWS Cloud.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77