PracticeISCFree practice exam

ISC · Information Systems and Data Management · 10 practice questions

RTO vs RPO: Synchronous vs Asynchronous Replication

Recovery time must meet RTO, and maximum potential transaction loss must meet RPO. Below, compare a base scenario with versions that change only replication or failover.

The ruleCompare recovery time to RTO and maximum potential loss to RPO. Synchronous replication storing durable commits at both sites supports RPO = 0; asynchronous replication meets RPO only if maximum lag fits the loss window.

Try one first

Company X runs a critical OLTP system in a primary datacenter with a warm standby in a secondary datacenter. Currently replication is asynchronous (RPO ≈ 5 minutes) and failover is manual (RTO ≈ 30 minutes). Management plans to move to synchronous replication with automatic failover in an active‑active configuration across two datacenters connected by a high‑speed, low‑latency link. Assuming the link and implementation are reliable and correct, what is the most likely immediate effect on RPO, RTO, and transaction commit latency?
Hint

Consider whether a transaction can be acknowledged before the remote site confirms it and whether failover remains manual or becomes automatic.

Same scenario, one fact changes

Base case

NovaPay runs a primary database at Site A and a standby at Site B. Its targets are RTO ≤ 15 minutes and RPO ≤ 1 minute. Asynchronous replication has a maximum lag of 5 minutes. After Site A fails, automatic failover restores full service in 10 minutes. Site B is the only recovery source.

Answer: RTO is met; RPO is not.

Recovery takes 10 minutes, within the 15-minute RTO. Potential transaction loss reaches 5 minutes, exceeding the 1-minute RPO.

Before you open each one, predict the answer.

Change 1Replace asynchronous replication with synchronous replication that durably stores committed transactions at both sites.

Answer: Both RTO and RPO are met.

Recovery remains 10 minutes. Durable commits at both sites support zero committed-transaction loss, within the 1-minute RPO.

Change 2Replace 10-minute automatic failover with manual failover that restores full service in 25 minutes.

Answer: Neither RTO nor RPO is met.

Recovery takes 25 minutes, exceeding the 15-minute RTO. The unchanged 5-minute maximum lag still exceeds the 1-minute RPO.

Change 3Reduce maximum asynchronous replication lag from 5 minutes to 1 minute.

Answer: Both RTO and RPO are met.

Recovery remains 10 minutes. Maximum potential transaction loss is 1 minute, exactly the permitted RPO.

Key points

  • Remember: Fast recovery does not prove that recent transactions are safe; test RTO and RPO separately.
  • Compare maximum replication lag, not average lag, with the permitted transaction-loss window.
  • A recovery time or loss window exactly equal to its stated maximum meets that target.

How the exam traps you

  • Treating automatic failover as proof that no transactions can be lost. Check replication separately. Automatic failover can restore service while recent committed transactions are missing.
  • Concluding that meeting either RTO or RPO means the design meets both. Make two comparisons. Both must pass.
  • Assuming asynchronous replication always fails RPO. Compare maximum lag with the allowed loss window. A one-minute lag meets a one-minute RPO.

Now the same facts as questions

Each question changes one fact from the one before. Watch which change flips the answer.

Question 1

NovaPay runs a primary database at Site A and a standby at Site B. Its targets are RTO ≤ 15 minutes and RPO ≤ 1 minute. Asynchronous replication has a maximum lag of 5 minutes. After Site A fails, automatic failover restores full service in 10 minutes. Site B is the only recovery source. Which targets are met?

Question 2

Same facts, except replication is synchronous and durably stores committed transactions at both sites. Which targets are met?

Question 3

Same facts, except manual failover replaces automatic failover and restores full service in 25 minutes. Which targets are met?

Question 4

Same facts, except maximum asynchronous replication lag is 1 minute instead of 5 minutes. Which targets are met?

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

An entity's system availability commitment for its online order platform states that, after a primary-region outage, service must be restored in the disaster-recovery (DR) region within 60 minutes, and no more than 15 minutes of committed transaction data may be lost. The entity has the following capabilities and controls: - Application servers in the DR region can be rebuilt from approved images in 25 minutes. - DNS failover to the DR region has been tested twice in Year 2, with cutover completed 18 minutes after outage declaration. - The DR database can be brought online from replicated logs in under 5 minutes. - The production database ships transaction logs asynchronously to the DR region every 20 minutes. - Immutable nightly backups are retained, and quarterly restore tests have succeeded. Assume outage declaration occurs immediately when the primary region fails, and no other replication, journaling, or transaction-capture controls exist. Which conclusion is best supported?
Hint

Separate the recovery-time requirement from the allowable-data-loss requirement, and test each one against the facts independently.

Question 3

A mid-size retailer operates an e-commerce application across two geographically separated data centers (DC‑East and DC‑West). Web and application servers are active in both sites behind a global load balancer. The production database in DC‑East is synchronously mirrored to DC‑West so that committed transactions are present in both sites in real time. The organization's availability objectives are RTO = 30 minutes and RPO = 0 (no data loss). At 10:00, DC‑East experienced a power failure that knocked out 75% of its web/app servers. The load balancer detected the failures and redirected traffic to DC‑West; automatic failover completed in 12 minutes. DC‑West continued processing transactions and contains all committed transactions that existed at failover. After failover, average response times doubled and the performance SLA was violated. Based on these facts, how should the system availability status immediately after failover be classified?
Hint

Compare the replication mode and failover time to the stated RPO/RTO objectives; distinguish availability objectives (RTO/RPO) from performance SLAs.

Question 4

A company's online ordering platform runs in a single primary data center. The production database is asynchronously replicated to a remote disaster‑recovery (DR) site once daily at 2:00 AM. There is no hot standby and failover is manual (recent manual failovers have taken about 12 hours). If the primary data center suffers a catastrophic failure at 1:00 AM (one hour before the scheduled nightly replication), which consequence is most directly attributable to the once‑daily asynchronous replication policy?
Hint

Ask which risk is controlled by replication frequency (the data‑loss window/RPO) versus which are controlled by failover design (downtime/RTO).

Question 5

Alpha Corp currently operates a critical transaction system from a single primary data center. Their disaster recovery approach is nightly full backups sent offsite and a cold standby; after a data-center failure, restoration and cold-site provisioning historically take about 20-24 hours, and data loss can be up to one nightly period. Management replaces this with near-real-time asynchronous replication to a geographically separate hot standby and implements automated failover to that standby. Which of the following effects on system availability metrics is most likely?
Hint

Compare the old 20-24 hour recovery and data-loss window from nightly backups with the near-real-time replication and automated failover when assessing changes to RTO and RPO.

Question 6

Company X operates a primary datacenter and a geographically remote standby in a single‑primary configuration. To avoid increasing write latency, transaction data is replicated asynchronously from the primary to the standby; the standby is configured for automated failover. Under normal conditions replication lag is usually under 10 seconds but can spike to about 30 seconds during peak load. If the primary fails unexpectedly during a peak-load spike, which of the following is the most likely effect on system availability and data integrity?
Hint

Ask whether 'asynchronous' guarantees the standby has every committed write at the instant the primary fails; consider the replication lag provided.

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

What is the difference between RTO and RPO?

RTO limits how long recovery may take. RPO limits how much recent transaction data may be lost, measured as a time window.

Does synchronous replication meet both RTO and RPO?

Durably storing commits at both sites supports RPO = 0. Recovery time still needs a separate comparison with RTO.

Can asynchronous replication meet a one-minute RPO?

Yes, if its maximum lag is no more than one minute. A five-minute maximum lag cannot guarantee that target, even with automatic failover.

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.