Soru

Zorluk: ZorAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate a three-tier application to AWS within a strict 6-month timeline. The application components and constraints are as follows:

* Web Tier: IIS web servers currently running on Windows Server 2012 R2. The enterprise wants to upgrade the operating system to Windows Server 2022 during the migration to maintain support, but lacks developer capacity to perform any application code modifications.
* Database Tier: An on-premises Oracle Database 12c instance. To eliminate licensing costs, the enterprise wants to migrate to Amazon Aurora PostgreSQL and has hired a systems integrator to rewrite the stored procedures and application database access code.
* Reporting Tier: A proprietary application running on legacy Solaris SPARC hardware. The vendor is defunct, the application cannot run on x86 architectures, and rebuilding it will take 18 months. The application is only used to generate historical quarterly archives, and the enterprise can extend the physical hardware lease on-premises.

Which combination of migration strategies (7 Rs) represents the most appropriate path for each tier?

  1. Replatform the web tier, Refactor the database tier, and Retain the reporting tierCevap
  2. B
    Replatform the web tier, Replatform the database tier, and Retain the reporting tier
  3. C
    Rehost the web tier, Refactor the database tier, and Retire the reporting tier
  4. D
    Refactor the web tier, Refactor the database tier, and Rehost the reporting tier

Cevap

Replatform the web tier, Refactor the database tier, and Retain the reporting tier
The correct strategy maps Replatform to the web tier, Refactor to the database tier, and Retain to the reporting tier. Upgrading the OS to Windows Server 2022 without modifying application code constitutes a Replatform strategy. A heterogeneous migration from Oracle to Aurora PostgreSQL involves converting database schemas and rewriting application-level code, which constitutes Refactoring. Retaining the reporting tier on-premises is appropriate because the SPARC architecture cannot be migrated directly to AWS x86 infrastructure, rebuilding it violates the 6-month timeline, and the business still requires its outputs.

Adım Adım Çözüm

1
Evaluate the Web Tier requirements.
Identify that the OS must be upgraded (Windows Server 2012 R2 to 2022) but the code cannot be modified.
Upgrading the underlying operating system or platform version without changing the core application architecture or code is a classic Replatform (lift-tinker-and-shift) migration path.
2
Evaluate the Database Tier requirements.
Identify that a heterogeneous migration is planned (Oracle to Amazon Aurora PostgreSQL) requiring schema conversion and code rewrites.
Moving from Oracle to PostgreSQL requires changing the database engine, converting schemas, and rewriting application queries/stored procedures, which constitutes a Refactor (re-architect) strategy.
3
Evaluate the Reporting Tier requirements.
Identify that the tier runs on Solaris SPARC (non-x86), cannot run on standard AWS x86 platforms, rebuilding takes 18 months (exceeding the 6-month window), and the system is still needed for quarterly reporting.
Since the workload cannot be migrated to AWS due to hardware architecture constraints and timeline, but must remain operational, the system should be kept on-premises, representing a Retain strategy.

Anahtar Kavram

Selecting migration strategies based on the AWS 7 Rs framework (Rehost, Replatform, Refactor, Repurchase, Retain, Retire, Relocate) by analyzing workload constraints, platform architecture, and target architectures.
Bu soruyu puanla