Examkin

Soru

Zorluk: ZorAssess and Select Migration Strategy (7 Rs)

A manufacturing enterprise is planning to migrate its legacy Enterprise Resource Planning (ERP) platform and associated satellite services to AWS. The migration must be completed within a strict six-month window, and the solutions architect must minimize ongoing administrative overhead. The application portfolio contains the following workloads:

1. Core ERP Web Tier: A Python Django application hosted on Ubuntu virtual machines. The web tier must be migrated with no modifications to its core business logic, but the enterprise wants to eliminate server management and operating system patching.
2. ERP Database: An on-premises Oracle Database instance using proprietary PL/SQL packages. The enterprise wants to eliminate licensing costs by migrating to Amazon Aurora PostgreSQL and has allocated a dedicated database engineering team to convert the schema and rewrite database code.
3. Legacy Shipping Integration: A Windows-based service running on Windows Server 2012. The application has no active vendor support, and the source code is unavailable. The system must be migrated as-is with a downtime window of less than one hour.
4. Warehouse Inventory Sync Service: A local synchronization utility that interfaces directly with physical Programmable Logic Controller (PLC) hardware via dedicated physical serial ports in the warehouse.

Which combination of migration strategies represents the most appropriate 7 Rs path for each workload component based on these requirements and constraints?

  1. A
    Core ERP Web Tier: Rehost; ERP Database: Replatform; Legacy Shipping Integration: Rehost; Warehouse Inventory Sync Service: Retain
  2. Core ERP Web Tier: Replatform; ERP Database: Refactor; Legacy Shipping Integration: Rehost; Warehouse Inventory Sync Service: RetainCevap
  3. C
    Core ERP Web Tier: Replatform; ERP Database: Refactor; Legacy Shipping Integration: Replatform; Warehouse Inventory Sync Service: Retire
  4. D
    Core ERP Web Tier: Refactor; ERP Database: Replatform; Legacy Shipping Integration: Rehost; Warehouse Inventory Sync Service: Retain

Cevap

Core ERP Web Tier: Replatform; ERP Database: Refactor; Legacy Shipping Integration: Rehost; Warehouse Inventory Sync Service: Retain
The migration strategy mapping of Replatform for the web tier, Refactor for the database, Rehost for the legacy shipping integration, and Retain for the warehouse inventory sync service is correct. Replatforming the web tier to a managed platform or container service removes operating system patching and server management without changing the core business logic. Refactoring the database is required because a heterogeneous migration from Oracle to Aurora PostgreSQL involves converting database schemas and rewriting PL/SQL stored procedures. Rehosting the legacy shipping integration using block-level replication (such as AWS Application Migration Service) allows it to be migrated as-is without source code, meeting the tight downtime window. Retaining the inventory sync service is necessary because it relies on local physical serial ports and hardware connections that cannot be virtualized in the cloud.

Adım Adım Çözüm

1
Analyze the web tier migration requirements.
Identify that the web tier needs to be migrated with no core business logic changes while eliminating operating system patching and server management overhead.
This matches a Replatform strategy (e.g., using a managed platform or container service) rather than a Rehost strategy (which keeps operating system management on the customer) or a Refactor strategy (which would modify application code).
2
Analyze the database migration requirements.
Identify that the database is migrating from Oracle to Amazon Aurora PostgreSQL, which involves schema conversion and rewriting proprietary PL/SQL packages.
Because it involves a change in the database engine (heterogeneous migration) requiring code modification and schema translation, it is classified as a Refactor (Re-architect) strategy.
3
Analyze the legacy shipping integration requirements.
Identify that the application has no source code, no vendor support, and must be migrated as-is under a one-hour downtime constraint.
AWS Application Migration Service (MGN) provides block-level replication to lift-and-shift (Rehost) the virtual machine with minimal cutover downtime, making Rehost the ideal choice.
4
Analyze the inventory sync service requirements.
Identify that the service relies on local physical serial ports connected to warehouse PLC hardware.
Because the physical hardware dependencies cannot be virtualized or migrated to the cloud, the service must be Retained on-premises.

Anahtar Kavram

Selecting migration strategies (7 Rs) based on application dependencies, code modification constraints, and business goals.
Bu soruyu puanla

Konular

Assess and Select Migration Strategy (7 Rs)

Bu konudan daha fazla soru