1Z0-1123-25 Question 129
Select 3You have deployed a three-tier e-commerce application in the Phoenix region, consisting of multiple compute instances for the application layer, a load balancer, and an Autonomous Database. You must use OCI Full Stack Disaster Recovery Service to fail over to Ashburn with minimal downtime. Which three steps should you implement to achieve a seamless failover experience?
- A
Create a Disaster Recovery (DR) Protection Group in Phoenix that references all relevant application resources (Compute, Load Balancer, and Database).
- B
Assign unique custom IP addresses in both Phoenix and Ashburn so the application uses the same IP address after failover.
- C
Define a DR plan with multiple waves that sequence resources appropriately (e.g., start the database first, then application servers, then update the load balancer).
- D
Use Full Stack DR� non-disruptive testing to validate planned failovers before you finalize the production DR strategy.
- E
Replicate the entire environment in an isolated VCN within the same Phoenix region to reduce latency.
Show answer and explanation
Correct answers: A, C, D
Explanation
In OCI Full Stack Disaster Recovery, you must group all dependent resources into a DR Protection Group, create a DR plan with appropriate waves (reflecting service startup dependencies), and thoroughly test failover scenarios before going live. Refer to Oracle documentation on 'Full Stack Disaster Recovery Service' to learn the recommended practices for setting up cross-region DR protection, sequencing multi-tier application components, and validating your DR plan through non-disruptive failover tests.
- A. Correct.
Correct. A DR Protection Group is fundamental in Full Stack DR. It references all resources (e.g., Compute, DB, Load Balancer) that need coordinated failover. Creating this group in the primary region (Phoenix) is a key first step.
- B. Incorrect.
Incorrect. You cannot simply reuse the same IP addresses across different regions. In cross-region DR, you typically rely on reconfiguring DNS or load balancer endpoints rather than forcing identical IP addresses in primary and DR regions.
- C. Correct.
Correct. Full Stack DR supports multi-wave DR plans so you can specify the sequence in which resources come online. This is crucial for multi-tier applications, ensuring the database is available before the application servers, which are then ready before redirecting traffic via the load balancer.
- D. Correct.
Correct. Full Stack DR provides a non-disruptive test feature (e.g., test failover or planned failover) to validate your DR plan without impacting production. Testing is essential to confirm that failover workflows, dependencies, and DNS updates function as intended.
- E. Incorrect.
Incorrect. Replicating resources in the same region does not provide true disaster recovery. You must host DR in a geographically separate region (e.g., Ashburn) to protect against regional outages.