1Z0-1123-25 Question 5
Single answerA multinational retailer wants to migrate its mission-critical e-commerce platform from on-premises to Oracle Cloud Infrastructure (OCI). The platform includes multiple virtual machines and an Oracle Database connected to a back-end inventory system. The company needs to minimize code changes, maintain a one-hour downtime window for cutover, and quickly decommission the on-premises hardware. Which migration approach would best meet these requirements?
- A
Re-architect into microservices on Oracle Container Engine for Kubernetes (OKE) and migrate data to Oracle Autonomous Database.
- B
Perform a lift-and-shift migration of the virtual machines and database to OCI using similar VM shapes and Database Cloud Service.
- C
Refactor the application for a serverless architecture using Functions and use Data Pump for an offline database migration.
- D
Implement a disaster recovery environment in OCI first, then fail over production after a 72-hour soak period.
Show answer and explanation
Correct answer: B
Explanation
When minimal application code changes and rapid migration are top priorities, a lift-and-shift strategy is typically the most practical. It moves the existing infrastructure directly into OCI with minimal reconfiguration. Oracle Cloud Infrastructure provides flexible Compute shapes and Database Cloud Service capabilities to closely match on-premises resource configurations. This reduces refactoring, shortens downtime, and enables a faster path to production. For more details, refer to the Oracle Cloud Infrastructure documentation on migration strategies and best practices, which outlines how to plan, execute, and validate workload migrations with minimal disruption.
- A. Incorrect.
Option A is incorrect because a microservices approach would require significant code re-engineering, which conflicts with the requirement to minimize code changes.
- B. Correct.
Option B is correct. A lift-and-shift migration allows moving existing VMs and the database with minimal modification, fitting the strict downtime window and allowing quick hardware decommissioning. This approach also streamlines the migration process by preserving the existing architecture.
- C. Incorrect.
Option C is incorrect because refactoring into a serverless architecture demands considerable development effort and testing, which contradicts the requirement to minimize code changes and deliver a quick migration.
- D. Incorrect.
Option D is incorrect because it introduces a separate DR environment and requires a 72-hour validation period, which is not suitable for the stated one-hour cutover downtime requirement.