PracticeISCFree practice exam

ISC · Information Systems and Data Management · 168 practice questions

System availability: RTO, RPO, uptime SLAs, and resilient designs

Master four moves: read the commitment, compute allowed downtime, pick an architecture that fits RTO/RPO, and trigger failover before you miss the SLA.

Mixed drill

Questions from every rule below, shuffled. You get the explanation after each one, and at the end, the rules to review.

The rules, one page each

  1. When to Trigger Failover: RTO and RPOStep by step

    Under 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.

  2. Choose Disaster Recovery Architecture by RTO and RPOSide by side

    RTO limits time to restore service; RPO limits acceptable data loss. Accept a disaster recovery design only if it meets both limits for the required outage scope.

  3. System Availability: Redundancy and Automatic FailoverStep by step

    Use redundant instances with health checks and automatic failover to reduce downtime from server failures. Patch instances in stages, and remove single points of failure in the database, load balancing, and network paths.

  4. How to Calculate SLA Uptime at 99.95% AvailabilityNumbers to know

    Allowed downtime equals (1 − promised availability) × the contract's measurement denominator. Count interruptions to the committed service unless an explicit exclusion applies, including all notice, timing, and cap conditions.

  5. RTO vs RPO: Synchronous vs Asynchronous ReplicationContrasting cases

    Compare 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.

  6. System Availability: Why Backups Do Not Prove RecoveryWhat next?

    A recovery test supports the restoration commitment only if it covers the steps needed to resume committed operations. Backup completion and restored application services alone do not demonstrate timely recovery for users.

  7. Availability vs. Security, Confidentiality, and IntegritySort it

    Availability concerns operation and use as committed, including uptime and recovery. Classify downtime against the stated commitment and its exclusions; classify controls by whether they primarily support continued operation or restoration.

  8. Availability Calculation: MTBF, MTTR, and RedundancyWorked example

    Component availability is A = MTBF/(MTBF + MTTR). With independent failures and instantaneous failover, parallel availability is 1 − ∏(1 − A_i); availability across independent required series tiers is ∏A_i.

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 system availability. No account needed to start.

Open the free simulator →

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.