Examkin

Soru

Zorluk: ZorAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate a trade clearing platform to AWS. The platform consists of the following components:

* Front-end Web Portal: Runs on Apache HTTP Server on enterprise Linux virtual machines (VMs). No source code is available, but it can be easily installed or packaged.
* Core Transaction Backend: A Java Spring Boot service running on custom on-premises middleware. It requires upgrading to the latest Java runtime to comply with enterprise security policies. The business wants to package it to reduce infrastructure management overhead.
* Backend Database: Runs on Microsoft SQL Server Enterprise Edition. It has heavy dependencies on Windows-specific Active Directory authentication. Due to licensing constraints and a strict 2-hour downtime window, the team cannot migrate this database engine to open-source engines or modify the application database layer.
* Legacy Reporting Service: Runs on an older IBM AIX server. The organization has decided that this reporting tool is no longer needed as reporting functions are moving to a new SaaS platform in 9 months. However, it must remain fully functional on-premises until the SaaS platform goes live.

Which combination of migration strategies represents the most appropriate mapping for these components according to the 7 Rs framework? (Select TWO.)

  1. Replatform the core transaction backend by containerizing it for Amazon ECS on AWS Fargate, and Replatform the database by migrating it to Amazon RDS for SQL Server.Cevap
  2. Retain the legacy reporting service on-premises, and Rehost the front-end web portal to Amazon EC2 using AWS Application Migration Service (MGN).Cevap
  3. C
    Refactor the core transaction backend by containerizing it for Amazon ECS on AWS Fargate, and Replatform the database by migrating it to Amazon Aurora PostgreSQL.
  4. D
    Replatform the legacy reporting service by migrating the workload to an Amazon EC2 instance running Red Hat Enterprise Linux (RHEL), and Rehost the database to Amazon RDS for SQL Server.
  5. E
    Refactor the database by migrating it to Amazon RDS for SQL Server to preserve Windows-specific Active Directory authentication, and Retire the legacy reporting service immediately.
  6. F
    Rehost the front-end web portal by containerizing it to run on AWS Fargate, and Relocate the legacy reporting service to VMware Cloud on AWS.

Cevap

Replatform the core transaction backend by containerizing it for Amazon ECS on AWS Fargate, and Replatform the database by migrating it to Amazon RDS for SQL Server; and Retain the legacy reporting service on-premises, and Rehost the front-end web portal to Amazon EC2 using AWS Application Migration Service (MGN).
The correct combination specifies Replatforming the core transaction backend by containerizing it for Amazon ECS on AWS Fargate, and Replatforming the database by migrating it to Amazon RDS for SQL Server. It also specifies Retaining the legacy reporting service on-premises, and Rehosting the front-end web portal to Amazon EC2 using AWS Application Migration Service (MGN). Containerization of a Spring Boot app without architecture change is Replatforming. Moving SQL Server to Amazon RDS for SQL Server is also Replatforming because it keeps the same database engine but leverages a managed service. Retaining the legacy AIX application is correct because it cannot run on standard x86 cloud architecture and is scheduled for decommissioning within 9 months. Rehosting the web portal using AWS MGN allows lift-and-shift of the Linux VMs without source code or reconfiguration.

Adım Adım Çözüm

1
Analyze the front-end web portal migration requirements.
Since there is no source code available and it runs on enterprise Linux VMs, migrating it as-is using VM-level replication tools represents a classic Rehost strategy.
Rehosting (lift-and-shift) minimizes migration risk and requires no application modifications or code access.
2
Analyze the core transaction backend requirements.
Containerizing the Spring Boot service to run on ECS Fargate without architectural changes is classified as Replatforming.
This optimizes infrastructure management and runtime environment versioning without restructuring the core application code.
3
Analyze the database migration options and constraints.
The SQL Server database has licensing, Active Directory, and 2-hour downtime constraints. Moving it to Amazon RDS for SQL Server is a Replatform strategy.
Moving to a managed database service (RDS) while keeping the same database engine is Replatforming, whereas changing database engines (e.g., to Aurora PostgreSQL) would require schema conversions and application rewrites, which is Refactoring.
4
Analyze the legacy reporting service constraints.
The legacy AIX workload is being decommissioned in 9 months and cannot run on x86 platforms. It must remain functional on-premises until then, indicating a Retain strategy.
Workloads that cannot be easily migrated due to OS constraints (IBM AIX) and are scheduled for decommissioning in the near term should be retained on-premises to avoid unnecessary migration costs and risks.

Anahtar Kavram

Selecting the correct migration strategy (Rehost, Replatform, Refactor, Retain, Retire, Relocate, Re-purchase) for each multi-tier application component based on architecture, OS constraints, licensing, downtime tolerance, and lifecycle plans.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Assess and Select Migration Strategy (7 Rs)

Bu konudan daha fazla soru