Amazon CLF-C02 Exam - Topic 3 Question 28 Discussion

Actual exam question for Amazon's CLF-C02 exam

Question #: 28
Topic #: 3

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.)

ARetire

BRehost

CRepurchase

DReplatform

ERefactor

Show Suggested 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

by Lavina at Sep 14, 2024, 08:56 AM

Limited Time Offer

25%

Off

Get Premium CLF-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Rosendo

5 months ago

Retiring it sounds risky, what if they need it later?

upvoted 0 times

...

Natalya

5 months ago

I think repurchasing might be a better choice for long-term.

upvoted 0 times

...

Brendan

5 months ago

Wait, can you really rehost a CMS that's incompatible?

upvoted 0 times

...

Eden

5 months ago

Totally agree, those require the least changes.

upvoted 0 times

...

Oretha

6 months ago

Rehosting and replatforming are the easiest options!

upvoted 0 times

...

Doretha

6 months ago

I feel like retiring the application isn't really a migration strategy, but I guess it could be an option if they decide to move on from the CMS altogether.

upvoted 0 times

...

Walton

6 months ago

I’m a bit confused about replatforming; it sounds like it could require some changes, which might not align with the least effort goal.

upvoted 0 times

...

Callie

6 months ago

I remember practicing a similar question, and I think repurchase could be a viable strategy if the CMS has a cloud-compatible alternative.

upvoted 0 times

...

Brittni

6 months ago

I think rehosting might be a good option since it involves moving the application without major changes, but I'm not entirely sure if it's the least effort.

upvoted 0 times

...

Tyisha

6 months ago

Okay, I've got it! Rehost and Repurchase are the two migration strategies that will require the least effort to move the incompatible CMS app to the cloud. Rehost is a simple lift-and-shift, and Repurchase means finding a new cloud-native CMS solution.

upvoted 0 times

...

Herman

6 months ago

Hmm, I'm a bit unsure about this one. I think Rehost and Repurchase are the way to go, but I'm not 100% confident. I'll need to double-check the definitions of each migration strategy to make sure I'm choosing the right ones.

upvoted 0 times

...

Fletcher

6 months ago

I'm leaning towards Rehost and Repurchase as the two best options here. Rehost would just lift and shift the app to the cloud, while Repurchase would involve finding a new cloud-based CMS solution. Both seem like they'd require less work than the other choices.

upvoted 0 times

...

Theodora

6 months ago

Hmm, this one's tricky. The CMS app is incompatible with the cloud, so I'm thinking Rehost or Repurchase might be the easiest options.

upvoted 0 times

...

Cherry

7 months ago

Okay, let's see. Retire doesn't seem like a good fit since we want to migrate the app, not just get rid of it. Replatform and Refactor sound like they'd require more effort to make the app cloud-compatible.

upvoted 0 times

...

Lizette

7 months ago

I'm a bit confused here. The question says the administrator expanded the volume, but now needs to expand the file system. I'm not sure if that means I need to use a different command to just expand the file system.

upvoted 0 times

...

Hillary

2 years 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 year ago

Sounds good to me. Let's make sure the CMS application sails smoothly into the AWS Cloud!

upvoted 0 times

...

Sabra

1 year ago

Agreed, those options will require the least effort and ensure a smoother migration process.

upvoted 0 times

...

Stephaine

1 year ago

I think we should go with the rehost (B) and replatform (D) strategies for the CMS application.

upvoted 0 times

...

Remedios

2 years ago

But retiring and replatforming seem like the most straightforward options to me.

upvoted 0 times

...

Hubert

2 years ago

I disagree, I believe options B and E would require less effort.

upvoted 0 times

...

Remedios

2 years ago

I think we should choose options A and D.

upvoted 0 times

...

Dana

2 years 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 year ago

Rehosting and replatforming are definitely the best options to minimize effort during the migration process.

upvoted 0 times

...

Bea

1 year ago

I think focusing on rehosting and replatforming will be the most efficient way to migrate the CMS application.

upvoted 0 times

...

Silvana

2 years ago

Rehosting and replatforming would definitely save time and effort compared to repurchasing.

upvoted 0 times

...

Vallie

2 years ago

I agree, repurchasing seems unnecessary. Rehosting and replatforming are more practical options.

upvoted 0 times

...

Carin

2 years 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 years ago

B) Rehost

upvoted 0 times

...

Marguerita

2 years ago

A) Retire

upvoted 0 times

...

Rosio

2 years 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 years ago

Definitely, those two options would minimize the effort needed for the migration process.

upvoted 0 times

...

Lisbeth

2 years ago

I agree, rehosting and replatforming would be the most efficient way to migrate the CMS application to the AWS Cloud.

upvoted 0 times

...