An enterprise is planning to migrate its commercial underwriting application portfolio to AWS. A solutions architect is performing the initial portfolio assessment to determine the appropriate migration strategy (7 Rs) for the following application components:
1. Transactional Database: Runs on IBM Db2. The target is Amazon Aurora PostgreSQL to eliminate commercial licensing costs. This migration requires comprehensive schema conversion and modifications to SQL queries and stored procedures within the application code to handle database engine differences.
2. Web Portal Tier: Runs on IBM WebSphere Application Server on AIX. The business wants to containerize the application to run on Amazon ECS on AWS Fargate to reduce OS licensing costs, without modifying any underlying Java application code.
3. Legacy Archival System: Runs on a legacy version of Windows Server. The software requires a physical USB security dongle plugged into the host server to function. The vendor is out of business, and no virtual or software-based licensing option exists.
4. Internal Reporting Database: Runs on Microsoft SQL Server 2019 on Windows Server 2019. It has low utilization, and the company wants to move it to a managed database service on AWS with minimal administrative effort while maintaining the exact same database engine.
Which migration strategies should the solutions architect select for these components? (Select TWO.)
- Migrate the transactional database from IBM Db2 to Amazon Aurora PostgreSQL using a Refactoring (Re-architecting) strategy.Cevap
- Retain the legacy archival system on-premises.Cevap
- CMigrate the transactional database from IBM Db2 to Amazon Aurora PostgreSQL using a Replatforming strategy.
- DRehost the legacy archival system by importing the Windows Server virtual machine into Amazon EC2.
- ERehost the Web Portal Tier directly to Amazon ECS on AWS Fargate.