SAP-C02 Question 574
Single answerAn organization wants to migrate its on-premises business-critical application to AWS with minimal downtime and without refactoring the application. The application runs on multiple VMs with a shared database and requires consistent performance. After the migration, the organization plans to begin modernizing the application by leveraging AWS services. Which migration approach should you recommend?
- A
Rehost the application using AWS Application Migration Service (MGN) to lift-and-shift the VMs to Amazon EC2.
- B
Replatform the application by containerizing it using Amazon ECS on AWS Fargate.
- C
Refactor the application as microservices using AWS Lambda and Amazon DynamoDB.
- D
Retire the application and replace it with a SaaS solution.
Show answer and explanation
Correct answer: A
Explanation
The organization's requirement to migrate the application with minimal downtime and no refactoring makes rehosting (lift-and-shift) the optimal approach. AWS Application Migration Service simplifies rehosting by automating the migration of on-premises workloads to Amazon EC2. This approach ensures the application can run on AWS without changes, enabling the organization to later modernize the application as planned.
- A. Correct.
Rehosting with AWS Application Migration Service (MGN) is the best choice for a lift-and-shift migration with minimal downtime and no need for application refactoring. This approach aligns with the requirement to preserve the existing architecture while preparing for modernization later.
- B. Incorrect.
Replatforming by containerizing the application requires changes to the application and its deployment model, which contradicts the requirement for no refactoring and minimal downtime during migration.
- C. Incorrect.
Refactoring the application into microservices involves significant architectural changes and development effort, which is not suitable for the stated requirement of no refactoring and minimal downtime.
- D. Incorrect.
Retiring the application and replacing it with a SaaS solution may not meet the organization's needs, as it involves abandoning the existing application rather than migrating it as required.