PracticeISCFree practice exam

ISC · Information Systems and Data Management · 6 practice questions

When to Trigger Failover: RTO and RPO

Trigger failover when a reliable estimate shows primary recovery will miss the RTO, not when the deadline arrives. Below: follow an outage from the first recovery estimate to the failover decision, checking data loss and cutover time.

The ruleUnder an expectation-based failover policy, initiate failover as soon as projected primary recovery exceeds the RTO. Confirm that the recovery copy meets the RPO and include failover execution time in the recovery timeline.

Try one first

A company's availability policy states that the disaster recovery site must be activated when a production outage is expected to exceed 2 hours. At 9:00 a.m., the primary application server fails. By 9:20 a.m., IT determines that restoring the server will likely take about 3 hours. Which action is most appropriate under the company's availability policy?
Hint

Focus on exactly what event triggers the policy: is it elapsed downtime, or the expectation that downtime will exceed a stated limit?

Step by step

  1. Set the recovery deadline

    A retailer's order-entry platform stops processing at 8:00 a.m.; its RTO is four hours and its RPO is 15 minutes. Service must therefore be restored by noon.

  2. Read the initial estimate

    At 8:25 a.m., operations expects primary recovery by 11:00 a.m. That estimate is within the RTO, so it does not trigger the plan's expectation-based failover rule.

  3. Recognize the decision-changing update

    At 9:10 a.m., operations revises primary recovery to 1:30 p.m., beyond the noon deadline. This update triggers failover now, even though four hours have not elapsed.

  4. Check the recovery copy

    The alternate environment has intact replicated data through 7:55 a.m., five minutes before processing stopped. That recovery point satisfies the 15-minute RPO.

  5. Include cutover time and act

    The alternate environment supports all critical functions and takes 35 minutes to activate. Initiating failover at 9:10 a.m. restores service at 9:45 a.m.; waiting until noon would miss the RTO.

Key points

  • Remember: the RTO is a recovery deadline, not a waiting period before failover starts.
  • A revised recovery estimate can trigger failover even when the earlier estimate supported continued local recovery.
  • Meeting the RPO does not remove the need to meet the RTO.

How the exam traps you

  • Wait until noon because the four-hour RTO has not expired. Act at 9:10 a.m., when the revised estimate first predicts recovery beyond noon.
  • Keep waiting because the recovery copy meets the RPO. RPO limits data loss. It does not extend the downtime allowed by the RTO.
  • Treat initiating failover as restoring service. Include the 35-minute cutover: starting at 9:10 a.m. restores service at 9:45 a.m.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

A financial services firm runs a production transaction system in a primary data center with a geographically separate DR site receiving asynchronous database replication (observed lag 10-20 minutes). The SLA requires RPO = 5 minutes and RTO = 1 hour. At 08:00 monitoring detected intermittent primary storage-controller write errors causing recent write failures; DBAs report possible corruption limited to recent transactions. Replication to DR remains active but, because it is asynchronous, some recent writes may not be replicated and corrupted writes could already exist on the DR copy. Transaction logs and recent incremental backups are available, and DBAs estimate a point-in-time recovery to a clean state can be completed within the 1-hour RTO if new writes are suspended. What immediate response is required?
Hint

Compare the SLA RPO (5 minutes) to the observed asynchronous replication lag (10-20 minutes) and weigh the risk of propagating recently corrupted writes against the DBAs' ability to recover within the RTO.

Question 3

A cloud-based billing service commits to customers that its production system will be available for processing 24/7, with a recovery time objective of 2 hours and a recovery point objective of 15 minutes for a production-region failure. In Year 2, the primary region goes offline after a cooling-system failure. Monitoring shows no evidence of unauthorized access, database integrity checks on the warm standby region are clean, and replication lag at the time of failure was 4 minutes. The standby environment has been tested and approved for production use. Assume no law or contract requires customer notification before recovery actions begin. Which response is most appropriate to satisfy the system availability objective?
Hint

Focus on what the availability commitment is actually promising and which action best meets the stated recovery objectives under the facts given.

Question 4

Alvar Tech operates a customer portal from a primary data center (DC1) with a passive disaster‑recovery site (DC2). DC2 receives asynchronous replication from DC1 (RPO up to 5 minutes). The company's SLA is 99.9% and the RTO is 60 minutes. An automated failover capability exists but is disabled during business hours (09:00-17:00) to reduce split‑brain risk. On Day 1, at 11:05 monitoring reports increased errors and database latency at DC1; at 11:15 the DC1→DC2 replication heartbeat becomes intermittent; at 11:20 the heartbeat is lost and DC1 is unreachable from external monitoring. Operations cannot restore DC1 within a few minutes. Considering the environment and availability objectives, which of the following is the most appropriate timing/trigger to initiate failover to DC2?
Hint

Separate transient/component alerts from a confirmed site outage; weigh asynchronous RPO, the disabled automated‑failover policy during business hours, and the 60‑minute RTO when choosing when to cut over.

Question 5

A company's critical payment-processing system has a documented RTO of 4 hours and an RPO of 1 minute. The primary database in the on‑premises data center uses synchronous replication to a local hot-standby (on the same campus) and also replicates asynchronously to a remote DR site that can lag up to 15 minutes. The primary data center's database storage subsystem experienced a catastrophic failure and cannot be brought online quickly. The local hot-standby is healthy but passive; promotion is estimated to take about 30 minutes. Failing over to the remote asynchronous DR site would take about 60 minutes; restoring from offsite backups would take about 12 hours. Which is the most appropriate immediate treatment to restore availability while adhering to the company's RTO and RPO?
Hint

Compare the RPO to replication lag (synchronous vs asynchronous) and compare each option's estimated recovery time to the RTO.

Question 6

A company's approved availability objective for its customer portal is restoration of service within 60 minutes of a disruption. The portal has a hot-site failover process that takes 25 minutes to execute and validate once initiated. The disaster recovery runbook therefore requires management to trigger failover once projected primary-site restoration exceeds 35 minutes from the start of the disruption. At 10:00, the portal goes down due to a primary-site storage failure. At 10:08, internal IT estimates local recovery will take 20 more minutes. At 10:12, the storage vendor revises the estimate to no less than 40 additional minutes, with timing still uncertain. Replication to the hot site is current, and assume there are no integrity or security issues that would independently change the response. When should management most appropriately trigger failover?
Hint

Work backward from the 60-minute restoration objective by subtracting the time required to complete failover and validation.

Drill all 168 System availability questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

Common questions

Should failover start before the RTO expires?

Yes, when the policy uses expected recovery time as its trigger. Here, the 9:10 a.m. estimate shows primary recovery will miss noon, so management should act then.

Does meeting the RPO mean failover can wait?

No. The recovery copy is only five minutes behind the outage, satisfying the 15-minute RPO, but projected primary recovery still exceeds the four-hour RTO.

Does failover time count toward the RTO?

Yes. The RTO covers the outage through service restoration, not just the time before failover begins. Here, the 35-minute cutover ends at 9:45 a.m., before the noon deadline.

Watch it solved

A full CPA ISC task-based simulation on System availability, worked step by step.

System Availability & RTO/RPO | CPA ISC Simulation (TBS) on YouTube

Practice ISC like the real exam

The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.

Open the free simulator →

More on System availability

All System availability practice →

Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.