AWS Certified Cloud Practitioner (CLF-C02)Cloud ConceptsHard
A university is looking to migrate its student information system to AWS. The system currently runs on an aging, highly customized database that is not easily portable to cloud-native managed services without significant code changes. The university wants to preserve the existing database for now, but move the application servers to AWS to gain elasticity. Which migration strategy (one of the 7 Rs) is most appropriate for the database in this scenario?
- ARehost
- BReplatform
- CRetain
- DRefactor
Show answer & explanationAnswer & explanation
Correct answer: C. Retain
The 'Retain' strategy is appropriate when an application (or a component like a database) cannot or should not be migrated to the cloud due to specific constraints like high customization, regulatory requirements, or lack of cloud-native alternatives without significant re-engineering. In this case, the aging, highly customized database that is not easily portable should be retained on-premises for now.
Why the other options are wrong
- A. Rehost would involve lifting and shifting the database as-is to EC2, which might still be challenging for a 'highly customized' and 'aging' database.
- B. Replatform implies some cloud-native optimization, which is difficult for this database without 'significant code changes'.
- D. Refactor would involve significant re-architecting, which the university wants to avoid for the database at this stage.
Retain (7 Rs)
A migration strategy where certain applications or components are kept in their existing on-premises environment, often due to specific technical, business, or regulatory constraints that make cloud migration unfeasible or undesirable.
- Used for applications that are too complex to migrate.
- May be temporary until a suitable cloud solution exists.
- Often involves systems with specialized hardware or compliance needs.
Memory trick: Seven paths to the cloud, each with unique turns.