Soru

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

A multinational energy conglomerate is planning to decommission its on-premises data center and migrate its smart grid monitoring and billing platform to AWS. The platform consists of 44 distinct components:

1. Web Dashboard: An application that runs on Apache HTTP Server on Red Hat Enterprise Linux (RHEL) 6.86.8. Corporate security policies require all cloud-deployed workloads to run on a hardened RHEL 88 or RHEL 99 image. The static HTML/JS assets and configuration can be deployed to the new OS version without code changes.
2. Telemetry Ingestion Worker: A Python daemon that processes incoming queue messages. It currently runs on a single virtual machine. The architecture team wants to run this daemon as a containerized task using Amazon ECS on AWS Fargate to eliminate server management.
3. Billing Database: An Oracle Database 19c19c Enterprise Edition with extensive PL/SQL stored procedures and spatial indexes. The business wants to migrate this database to Amazon Aurora PostgreSQL to eliminate Oracle licensing costs. A dedicated migration team is allocated to convert the schema and rewrite the stored procedures.
4. Legacy Field Device Link: A proprietary C-based utility that communicates with legacy field RTUs via a physical dial-up serial modem connected to an on-premises PCI card. The proprietary protocol cannot be emulated or routed over IP networks, and the manufacturer has ceased support.

Which combination of migration strategies (77 Rs) represents the most appropriate path for each component to meet the company's requirements?

  1. A
    Rehost the Web Dashboard; Refactor the Telemetry Ingestion Worker; Refactor the Billing Database; Retain the Legacy Field Device Link.
  2. Replatform the Web Dashboard; Replatform the Telemetry Ingestion Worker; Refactor the Billing Database; Retain the Legacy Field Device Link.Cevap
  3. C
    Replatform the Web Dashboard; Replatform the Telemetry Ingestion Worker; Replatform the Billing Database; Retire the Legacy Field Device Link.
  4. D
    Refactor the Web Dashboard; Replatform the Telemetry Ingestion Worker; Rehost the Billing Database; Rehost the Legacy Field Device Link.

Cevap

Replatform the Web Dashboard; Replatform the Telemetry Ingestion Worker; Refactor the Billing Database; Retain the Legacy Field Device Link.
The correct strategy combination is Replatform the Web Dashboard, Replatform the Telemetry Ingestion Worker, Refactor the Billing Database, and Retain the Legacy Field Device Link. The Web Dashboard requires upgrading the operating system from RHEL 6.8 to a supported version (RHEL 8/9) without changing application code, which constitutes a Replatform strategy. The Telemetry Ingestion Worker is packaged into a container and moved to AWS Fargate to reduce management overhead, representing a Replatform strategy. The Billing Database undergoes a heterogeneous migration from Oracle to Amazon Aurora PostgreSQL, requiring schema conversion and PL/SQL code rewrite, which is classified as a Refactor (Re-architect) strategy. The Legacy Field Device Link relies on physical hardware (a dial-up modem connected to a PCI card) that cannot be emulated or virtualized on AWS, meaning it must be Retained on-premises.

Adım Adım Çözüm

1
Analyze the Web Dashboard component requirements.
The Web Dashboard runs on an unsupported OS (RHEL 6.8) and must run on a hardened RHEL 8/9 image without code changes.
Since the OS is upgraded but the application code is not rewritten, this falls under a Replatform strategy rather than a simple Rehost or Refactor.
2
Analyze the Telemetry Ingestion Worker requirements.
The worker daemon is containerized and deployed to Amazon ECS on AWS Fargate to reduce administrative overhead without modifying the application code.
Moving a workload to a managed/serverless container runtime (like Fargate) without changing its core architecture is classified as a Replatform strategy.
3
Analyze the Billing Database requirements.
The database engine is migrated from Oracle to Amazon Aurora PostgreSQL, requiring schema conversion and PL/SQL code rewrite.
Heterogeneous database migrations that involve schema conversions and application code/SQL adjustments are classified as Refactor (Re-architect) due to the architectural and code modifications required.
4
Analyze the Legacy Field Device Link requirements.
The link depends on physical dial-up modem hardware connected to a PCI card, and the protocol cannot be emulated or routed over IP networks.
Since standard cloud infrastructure cannot emulate or connect physical PCI modem hardware, and the application cannot be modified, this component must be kept on-premises, which is a Retain strategy.

Anahtar Kavram

Selecting the correct migration strategies from the 7 Rs framework based on application constraints, OS support lifecycle, target engine compatibility, and physical hardware dependencies.
Bu soruyu puanla