1Z0-997-25 Question 77
Select 2A financial services organization is running a mission-critical Oracle Database on Oracle Cloud Infrastructure (OCI). They require near-zero data loss in the event of a regional outage and want to minimize production downtime during quarterly patching. They plan to create a remote standby database in a separate OCI region. Which two configuration steps should they implement to meet these requirements?
- A
Use Data Guard Maximum Performance mode for the standby database to achieve the best throughput and minimal latency.
- B
Configure Data Guard in Maximum Availability mode for near-zero data loss and acceptable primary database availability.
- C
Use Data Guard's rolling upgrade feature to patch standby databases first, then switch over to minimize downtime.
- D
Rely solely on daily local backups of the primary database to protect against data loss and perform patches in place.
- E
Host the standby database on a lower-cost shape without enabling real-time redo to reduce overhead.
Show answer and explanation
Correct answers: B, C
Explanation
To achieve near-zero data loss, Oracle recommends configuring the standby in Data Guard Maximum Availability mode, which synchronizes redo data to the standby and balances data protection with availability. Coupling this setup with rolling upgrades allows administrators to patch the standby first and then switch over, reducing downtime for production systems. Refer to Oracle documentation on Data Guard concepts and best practices for more details on protection modes (Maximum Availability vs. Maximum Performance) and the rolling upgrade procedure.
- A. Incorrect.
Option 1 (Incorrect): Maximum Performance mode provides good performance by allowing asynchronous redo transport, but it does not guarantee near-zero data loss. This mode is not ideal for a strict RTO/RPO requirement.
- B. Correct.
Option 2 (Correct): Maximum Availability mode is typically recommended for mission-critical databases demanding near-zero data loss. It attempts to synchronize redo data, but it doesn't shut down the primary if the standby is unreachable, balancing protection with availability.
- C. Correct.
Option 3 (Correct): Data Guard's rolling upgrade (also known as transient logical standby) enables patching the standby system first, then performing a switchover, minimizing production downtime during patching cycles.
- D. Incorrect.
Option 4 (Incorrect): Daily local backups alone do not guarantee near-zero data loss, because there could be up to a day of data at risk. This approach also doesn't address minimizing patch-related downtime, as you would still have to take the production database offline for the patch.
- E. Incorrect.
Option 5 (Incorrect): Hosting the standby on a lower-cost shape without enabling real-time redo (or synchronous/near-synchronous transport) undermines the objective of near-zero data loss, because the redo might not be fully synchronized.