A global logistics provider is planning to migrate its legacy supply chain orchestration system to AWS. The migration must be completed within , and the target architecture must optimize cost and minimize administrative overhead where possible. A Solutions Architect has discovered the following three key workloads during the assessment phase:
1. Proprietary Message Broker: A self-managed RabbitMQ cluster running on CentOS virtual machines. The broker utilizes custom-compiled, third-party Erlang modules for legacy protocol translation. The source code for these custom modules has been lost, preventing recompilation.
2. Analytical Data Warehouse: A Oracle Data Warehouse that relies heavily on Oracle-specific analytical functions, stored procedures, and materialized views. The business intends to migrate this workload to Amazon Redshift to eliminate costly license agreements and improve analytical performance, which will require redesigning the database schema and rewriting downstream reporting queries.
3. Legacy Document Archiving Service: An archiving daemon written in C that runs on legacy Solaris SPARC hardware. The daemon writes static PDF files to a shared NFS mount. This system is scheduled to be completely decommissioned in when a new cloud-native Software-as-a-Service (SaaS) document management platform is fully rolled out.
Which of the following migration strategies represent the most appropriate alignment with the framework for these workloads? (Select TWO.)
- AReplatform the Proprietary Message Broker to Amazon MQ for RabbitMQ to eliminate operating system patching and cluster management overhead.
- Refactor (Re-architect) the Analytical Data Warehouse by using the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) to migrate the schema and data to Amazon Redshift.Cevap
- CReplatform the Analytical Data Warehouse by using AWS DMS to load the data directly into Amazon Redshift, since database engine conversions to managed target services are classified as replatforming.
- Retain the Legacy Document Archiving Service on-premises and establish a hybrid network connection to allow migrated cloud workloads to interface with the shared NFS mount until it is decommissioned.Cevap
- ERehost the Legacy Document Archiving Service by utilizing AWS Application Migration Service (AWS MGN) to replicate the Solaris SPARC virtual machines directly into an Amazon EC2 environment.