PracticeISCFree practice exam

ISC · Information Systems and Data Management · 9 practice questions

How to Calculate SLA Uptime at 99.95% Availability

Calculate availability using the contract's measurement period, service boundary, and downtime exclusions. Below: CloudWorks' monthly numbers show why excluding valid maintenance still leaves a breach of its 99.95% uptime commitment.

The ruleAllowed 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.

Try one first

CloudWorks' hosting contract guarantees 99.95% availability measured over each calendar month. The contract also states that scheduled maintenance windows (up to 4.0 hours per month) are excluded from availability calculations if CloudWorks provides at least 48 hours' advance notice. In a 30-day month (720 hours), CloudWorks gave 72 hours' notice and performed scheduled maintenance lasting 3.0 hours. During the same month CloudWorks had an unplanned power outage of 1.5 hours, an unexpected failover during a software update that caused 0.75 hours of user-visible downtime, and an unannounced backup-restore test that caused 1.0 hour of user-visible downtime. Based on the contract and these events, which of the following is the best-supported conclusion?
Hint

Exclude properly‑notified scheduled maintenance (check the 48‑hour notice rule), then divide unexcluded downtime by 720 hours to compute the monthly availability percentage and compare to 99.95%.

Numbers to know

CloudWorks' monthly availability commitmentEvaluate compliance for each calendar month.99.95%
Monthly measurement denominatorThe 30-day month contains 720 hours. This calculation retains the full monthly denominator.43,200 minutes
Permitted downtime fraction1 − 0.9995 = 0.0005, or 0.05%. Keep the decimal places straight.0.0005
Allowed monthly downtime43,200 × 0.0005. Counted downtime above this amount breaches the commitment.21.6 minutes
Minimum maintenance noticeAdvance notice is required for the scheduled-maintenance exclusion.48 hours
Actual maintenance noticeCloudWorks met the notice requirement.72 hours
Monthly maintenance exclusion capThe contract permits up to 4 hours of qualifying scheduled maintenance.240 minutes
Excluded scheduled maintenanceThe 3-hour maintenance met the notice requirement and stayed below the cap.180 minutes
Counted power outageThe 1.5-hour unplanned outage has no stated exclusion.90 minutes
Counted failover interruptionThe unexpected software-update failover caused user-visible downtime.45 minutes
Counted backup-restore testThe unannounced test caused user-visible downtime and does not qualify for exclusion.60 minutes
Total counted downtime90 + 45 + 60 = 195 minutes. Do not add the excluded maintenance.195 minutes
Actual monthly availability(43,200 − 195) ÷ 43,200 × 100. Approximately 99.55%, below 99.95%.99.5486%
Downtime above the allowance195 − 21.6 = 173.4 minutes. CloudWorks breached the monthly SLA.173.4 minutes

Key points

  • Remember: Compare counted downtime with allowed downtime, not with the length of the maintenance exclusion.
  • Convert every outage to minutes before adding or comparing amounts.
  • Evaluate this calendar month separately; another month's uptime cannot offset its breach.
  • Keep the contract's denominator: this example uses all 43,200 monthly minutes.

How the exam traps you

  • Count all 375 outage minutes, including qualifying maintenance. Exclude the 180 maintenance minutes because notice and cap conditions were met.
  • Count only the 90-minute power outage because the other interruptions were internal. The failover and backup test caused user-visible downtime, so their 105 minutes also count.
  • Treat approximately 99.55% availability as meeting 99.95%. Compare 195 counted minutes with the 21.6-minute allowance. The monthly SLA was breached.

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

An enterprise is establishing availability targets for two systems: a customer-facing billing system whose downtime would cause immediate revenue loss and regulatory reporting failures if unavailable for more than 30 minutes, and an internal knowledge base whose downtime causes only employee inconvenience. Both systems have similar user counts. Which single factor should primarily govern the selection of availability targets for these systems?
Hint

Which choice quantifies how 'bad' downtime would be and how quickly services must be restored, rather than describing load, contracts, or budget?

Question 3

Nimbus hosts an online order-management platform for business customers. Customer contracts state that the platform will be available 99.9% of the time, scheduled maintenance must be announced in advance, and service must be restored within 4 hours after a major outage. Assume Nimbus is evaluating the system's availability objective only. Which factor should most directly govern Nimbus's design of availability controls?
Hint

Ask what availability is trying to satisfy: the system being operational and usable when users were told it would be.

Question 4

A payroll SaaS provider commits that customers can access and use its system 24/7, except for scheduled maintenance announced at least 72 hours in advance. The provider has redundant application servers and replicated databases across two availability zones. During a peak payroll deadline, an outsourced identity provider that is part of the defined system boundary experiences a 4-hour outage. Customers cannot log in or submit payroll during that period. No payroll data is lost or altered, and after access is restored, queued transactions process correctly. Assume the identity provider's downtime is not excluded from the provider's availability commitment. What is the best-supported consequence of this event?
Hint

Focus on the user's ability to access and use the system as committed, not just on whether data stayed intact or internal infrastructure stayed up.

Question 5

A company operates a mission-critical online payment platform. In Year 1, measured downtime included: (a) scheduled maintenance that requires a full-platform restart one Saturday per week for 2 hours (this maintenance takes all production capacity offline across any existing sites), and (b) unplanned outages averaging 1 hour every 30 days due to hardware/software failures. Nightly backups have an independent restore RTO of 4 hours but have not caused outages. Availability is measured including both planned and unplanned downtime. Management wants to prioritize a single governing factor in Year 2 to most effectively increase overall availability toward a 99.99% annual target. Which factor should management prioritize?
Hint

Convert the weekly and 30‑day downtimes into annual hours and compare which category contributes most to total downtime.

Question 6

An entity's customer portal has a service-level requirement of 99.9% availability each 30-day month. For this question, calculate availability as uptime divided by total minutes in the month, and assume all downtime counts toward the requirement. If the portal was unavailable for 50 minutes during the month, which conclusion is most appropriate?
Hint

Convert the month into total minutes first, then determine how many minutes of downtime 0.1% represents.

Question 7

Orion Hosting's system description states that its production environment availability commitment is 99.9% monthly uptime. The commitment expressly excludes (1) scheduled maintenance announced at least 48 hours in advance and performed during the approved Sunday 1:00 a.m. to 3:00 a.m. window and (2) outages caused solely by customer-managed network or identity-provider components outside Orion's system boundary. Orion does not commit to a specific response-time metric. Assume the month had no other downtime or incidents. Which event should be classified as an availability exception attributable to Orion for that month?
Hint

Focus first on the exact scope of the availability commitment before reacting to the severity or duration of the incident.

Question 8

A company's customer contract states that its online ordering system will be available 24/7, except for scheduled maintenance announced at least 24 hours in advance. Which situation would most likely indicate that the company did not meet its system availability commitment?
Hint

Focus on the stated commitment and its explicit exception, then ask whether the affected system was actually the one covered.

Question 9

A cloud vendor's SLA promises 99.95% uptime per calendar month. For Jan-Jun the measured downtime by month was: Jan (31 days) = 20 min; Feb (28 days) = 25 min; Mar (31 days) = 18 min; Apr (30 days) = 10 min; May (31 days) = 130 min; Jun (30 days) = 35 min. Assume uptime is measured per calendar month as (available minutes − downtime) ÷ available minutes and that all downtime events count (no carve‑outs). Which conclusion about SLA compliance is best supported?
Hint

For each calendar month compute allowed downtime = 0.0005 × (days in month × 1,440). Compare that month's allowed minutes to that month's actual downtime, do not sum or average months.

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

How much downtime does 99.95% uptime allow in a 30-day month?

Using all 43,200 monthly minutes, the allowance is 43,200 × 0.0005 = 21.6 minutes. CloudWorks' 195 counted minutes exceed that limit.

Does scheduled maintenance count against SLA uptime?

Follow the contract's exclusion conditions. CloudWorks excludes its 180 maintenance minutes because 72 hours' notice exceeds the 48-hour minimum and the maintenance stays within the 240-minute cap.

Do excluded maintenance minutes reduce the SLA denominator?

Use the contract's calculation, not a universal assumption. This CloudWorks example retains the full 43,200-minute denominator and removes qualifying maintenance from counted downtime.

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.