Examkin

Question

Difficulty: Very hardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate its core media management and delivery platform to AWS within a strict 6-month timeline. The platform consists of four distinct components:

1. A Transcoding Engine running on-premises Windows Server VMs. It relies on custom GPU-accelerated libraries requiring specific OS kernel modifications. To meet the deadline, it must be migrated with no changes to the OS environment or application code.
2. A User Profiles Database running on self-managed PostgreSQL instances. The enterprise wants to eliminate the administrative overhead of OS patching and backup management but must keep the PostgreSQL database engine without modifying the application code or schema.
3. A Legacy Licensing Server that uses a physical USB hardware security dongle connected directly to an on-premises host. The software vendor does not support network-based or virtual licensing mechanisms.
4. A Metadata Catalog running on a commercial Oracle Database. The enterprise wants to eliminate licensing costs and modernize the database tier. The migration team has verified that the schema and application SQL queries can be converted to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT), and has allocated development resources to rewrite the incompatible application code.

Which combination of migration strategies represents the most appropriate alignment with the AWS 7 Rs framework for these components?

  1. Transcoding Engine: Rehost; User Profiles Database: Replatform; Legacy Licensing Server: Retain; Metadata Catalog: RefactorAnswer
  2. B
    Transcoding Engine: Rehost; User Profiles Database: Replatform; Legacy Licensing Server: Retain; Metadata Catalog: Replatform
  3. C
    Transcoding Engine: Replatform; User Profiles Database: Rehost; Legacy Licensing Server: Retire; Metadata Catalog: Refactor
  4. D
    Transcoding Engine: Rehost; User Profiles Database: Refactor; Legacy Licensing Server: Retain; Metadata Catalog: Replatform

Answer

Transcoding Engine: Rehost; User Profiles Database: Replatform; Legacy Licensing Server: Retain; Metadata Catalog: Refactor
The correct strategy alignment maps each component to its ideal 7 Rs path based on the constraints: Rehosting the Transcoding Engine preserves custom OS-level GPU configurations under tight timelines; Replatforming the User Profiles Database shifts management overhead to Amazon RDS without modifying code; Retaining the Licensing Server is necessary due to physical USB hardware licensing restrictions; Refactoring the Metadata Catalog allows database modernization and cost savings by migrating from Oracle to Aurora PostgreSQL, which requires schema conversion and code rewrite.

Step-by-Step Solution

1
Analyze the requirements for the Transcoding Engine.
Identify that the Transcoding Engine has OS kernel-level modifications and custom GPU requirements, and must be migrated without changes. This aligns with the Rehost (lift-and-shift) strategy to Amazon EC2 GPU instances.
Rehosting allows quick migration of workloads without application or OS-level modifications.
2
Analyze the requirements for the User Profiles Database.
Identify that the database engine remains PostgreSQL but needs to move to a managed service to reduce administrative overhead without database schema or application code changes. This aligns with the Replatform (lift, tinker, and shift) strategy to Amazon RDS for PostgreSQL.
Replatforming replaces the infrastructure hosting platform with a managed service (RDS) without changing the core application code or database engine.
3
Analyze the constraints of the Legacy Licensing Server.
Determine that the Licensing Server requires physical hardware (USB dongle) that cannot be migrated to the virtualized cloud environment and cannot use network licensing. This aligns with the Retain strategy.
Workloads with physical dependencies that cannot be virtualized or migrated must be retained on-premises.
4
Analyze the requirements for the Metadata Catalog.
Identify that migrating from Oracle to Amazon Aurora PostgreSQL requires schema conversion (AWS SCT) and application code modification to eliminate licensing costs and modernize the application. This aligns with the Refactor (re-architect) strategy.
Refactoring involves modifying the application and database architecture to adopt cloud-native features, which includes database engine changes and schema rewrites.

Key Concept

Selecting the appropriate AWS 7 Rs migration strategy (Rehost, Replatform, Refactor, Retain, Retire, Repurchase, Relocate) based on technical dependencies, business constraints, and database engines.
Estimated Time:3m 0s
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic