An enterprise is executing a large-scale migration of its core portfolio to AWS and wants to select the appropriate migration strategies based on the 7 Rs framework. The portfolio contains the following applications:
1. Application 1: A customer billing portal built on a custom Java framework running on Apache Tomcat. The development team has no capacity for code modifications. The enterprise wants to eliminate OS-level patching, configuration management, and server provisioning, and prefers a managed containerized platform like AWS Fargate.
2. Application 2: A risk-analytics engine that uses an on-premises Oracle Database Enterprise Edition. The enterprise wants to migrate the database to Amazon Aurora PostgreSQL to eliminate expensive licensing costs. This will require database schema conversion and application code modifications.
3. Application 3: A legacy inventory forecasting tool running on a specialized IBM AIX Unix server. The software vendor is out of business, the source code is lost, and the software cannot run on x86-64 architecture. The system must remain accessible for regulatory reporting for another 18 months.
4. Application 4: An on-premises enterprise resource planning (ERP) system that has a direct, modern, cloud-based Software-as-a-Service (SaaS) equivalent from the same vendor. The firm has decided to adopt the SaaS version.
Which of the following combinations of migration strategies represent the most appropriate migration paths based on these requirements and constraints? (Select TWO)
- Application 1 should be migrated using the Replatform strategy by deploying the Java application to Amazon ECS on AWS Fargate; Application 2 should be migrated using the Refactor (Re-architect) strategy by converting the database schema and rewriting code to use Amazon Aurora PostgreSQL.Cevap
- BApplication 1 should be migrated using the Refactor strategy by containerizing it; Application 2 should be migrated using the Replatform strategy by converting the database schema to Amazon Aurora PostgreSQL.
- CApplication 3 should be migrated using the Rehost strategy by using AWS Application Migration Service (MGN) to migrate the IBM AIX server to Amazon EC2; Application 4 should be migrated using the Repurchase strategy by transitioning to the vendor's SaaS offering.
- Application 3 should be migrated using the Retain strategy on-premises; Application 4 should be migrated using the Repurchase strategy by transitioning to the vendor's SaaS offering.Cevap
- EApplication 2 should be migrated using the Replatform strategy by deploying the Oracle database to Amazon RDS for PostgreSQL; Application 3 should be migrated using the Retire strategy immediately to eliminate on-premises infrastructure footprint.
- FApplication 1 should be migrated using the Rehost strategy by using AWS Application Migration Service (MGN) to replicate the virtual machines; Application 4 should be migrated using the Refactor strategy by building a custom data integration layer to the SaaS platform.