Soru

Zorluk: Çok zorAssess and Select Migration Strategy (7 Rs)

A global logistics provider is planning to migrate its legacy supply chain orchestration system to AWS. The migration must be completed within 6 months6\text{ months}, 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 77 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 50 TB50\text{ TB} 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 9 months9\text{ months} 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 7 Rs7\text{ Rs} framework for these workloads? (Select TWO.)

  1. A
    Replatform the Proprietary Message Broker to Amazon MQ for RabbitMQ to eliminate operating system patching and cluster management overhead.
  2. 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
  3. C
    Replatform 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.
  4. 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
  5. E
    Rehost 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.

Cevap

The correct strategies are to Refactor (Re-architect) the Analytical Data Warehouse using AWS SCT and AWS DMS to migrate the schema and data to Amazon Redshift, and to Retain the Legacy Document Archiving Service on-premises while establishing a hybrid network connection for access.
Refactoring the Analytical Data Warehouse is correct because migrating from an Oracle Data Warehouse to Amazon Redshift is a heterogeneous migration that requires rewriting database schema and downstream analytical queries. Retaining the Legacy Document Archiving Service on-premises is correct because the system runs on Solaris SPARC hardware (which cannot run directly on standard AWS x86/ARM compute) and is scheduled for decommissioning within 9 months, rendering migration efforts unnecessary and cost-ineffective.

Adım Adım Çözüm

1
Evaluate the migration options for the Proprietary Message Broker under the 7 Rs framework.
The message broker requires custom Erlang modules for which source code is lost. Because Amazon MQ is a managed service that does not support custom Erlang modules or OS-level plugins, replatforming to Amazon MQ is not viable. The broker must be rehosted on EC2 to preserve the custom CentOS setup.
Identify the technical blocker (custom modules with lost source code) that prevents moving to a managed service.
2
Evaluate the migration classification for the Analytical Data Warehouse.
Migrating a 50 TB Oracle Data Warehouse to Amazon Redshift involves a heterogeneous database engine conversion, schema redesign using AWS SCT, and modifying application/query code. Under AWS framework guidelines, this is classified as Refactoring (Re-architecting).
Distinguish between Replatforming (minor optimization, same engine/minor adjustments) and Refactoring (architectural/engine changes requiring schema rewrites).
3
Evaluate the constraints of the Legacy Document Archiving Service.
The service runs on Solaris SPARC (incompatible with standard x86-64 EC2 platforms directly) and will be decommissioned in 9 months. Emulating SPARC on AWS or refactoring the daemon is not cost-effective for a short lifecycle, meaning it should be Retained on-premises with hybrid access.
Determine the optimal strategy based on the remaining lifetime of the system and architecture compatibility constraints.

Anahtar Kavram

Selecting migration strategies within the 7 Rs framework based on architecture platform compatibility, managed service limitations, and system lifecycle constraints.
Bu soruyu puanla