A global maritime cargo shipping firm is evaluating its application portfolio for migration to the AWS Cloud. During the analysis, the migration team identifies two specific workloads:
1. A bespoke legacy port operations scheduler running on an outdated, highly customized IBM AIX Unix operating system that cannot be virtualized in standard x86 environments. The firm plans to keep this scheduler operational on-premises for the next two years.
2. A monolithic core logistics dispatch system. The team plans to migrate the application server as-is, but will migrate its underlying commercial relational database to Amazon Aurora PostgreSQL to reduce licensing costs and management overhead, without modifying the application's core code.
Which two of the following migration strategies represent the correct approach for these workloads?
- Retaining for the port operations scheduler, as it will remain on-premises due to platform incompatibility and business requirements.Cevap
- Replatforming for the logistics dispatch system, as the database is moved to a managed database service (Amazon Aurora) to optimize operations and reduce licensing costs without modifying the core application code.Cevap
- CRehosting for the logistics dispatch system, as the application and its database are migrated to AWS without any modifications to their configuration or platform components.
- DRefactoring for the logistics dispatch system, as changing the underlying database engine to Amazon Aurora requires a complete rewrite of the application's architecture to be cloud-native.
- ERepurchasing for the port operations scheduler, as the unsupported Unix system must be retired and replaced with a modern commercial off-the-shelf software product.