ISC · Information Systems and Data Management · 6 practice questions
Availability vs. Security, Confidentiality, and Integrity
Availability means the system can be used as committed, after applying stated downtime exclusions. Below: sort independent North portal cases against a 24/7 promise that excludes scheduled maintenance announced at least 24 hours ahead.
Try one first
Hint
Focus on what actually went wrong: Was the main problem unauthorized access, incorrect processing, disclosure of data, or inability to use the system?
Answer C. Availability addresses whether systems, products, or services are accessible for operation and use as committed or agreed. Here, the key problem is that the website could not be accessed for four hours due to insufficient capacity. Because the facts rule out unauthorized access and incorrect processing, availability is the best classification.
Why not A: This is tempting because outages are often associated with cybersecurity concerns. However, the stem does not describe unauthorized access, intrusion, or other security compromises; the primary issue is downtime, which points to availability.
Why not B: Processing integrity concerns whether processing is complete, valid, accurate, timely, and authorized. The question states completed transactions were not processed incorrectly once the system resumed, so the problem is lack of access rather than incorrect processing.
Why not D: Confidentiality involves preventing unauthorized access to or disclosure of information. The stem explicitly says no customer data was accessed by unauthorized parties, so confidentiality was not violated.
Sort it
The portal is unusable during time covered by North's availability promise.
The control or gap primarily affects continued operation or recovery, without describing an actual outage.
The primary issue is unauthorized access, disclosure, or incorrect processing rather than uptime or recovery.
Scheduled maintenance meets North's requirement for at least 24 hours of advance notice.
| Item | Goes to |
|---|---|
| A traffic surge makes North's portal unreachable for four hours; completed orders remain accurate. | Availability failureCustomers cannot use the promised service. Accurate completed orders do not excuse downtime. |
| North's portal accepts incomplete orders and invalid quantities while remaining online. | Other trust services concernThis is processing integrity: input controls do not ensure complete, valid processing. |
| North tests automatic failover to a redundant portal server. | Availability control or weaknessFailover testing supports continued service after a server failure. |
| North takes the portal offline for scheduled maintenance announced 24 hours ahead. | Permitted downtimeThe maintenance meets the stated notice requirement, so this downtime is excluded from the promise. |
| North transmits confidential customer information to its fulfillment vendor without encryption. | Other trust services concernThe primary concern is protecting confidential information in transit, not keeping the portal usable. |
| A network configuration error makes North's portal inaccessible for eight hours outside scheduled maintenance. | Availability failureThe cause is a configuration error, but the failed commitment is system access. |
| North backs up portal data nightly but has no alternate processing site or tested disaster recovery procedures. | Availability control or weaknessRecoverable data does not ensure that North can restore portal operations quickly. |
| North takes the portal offline for scheduled maintenance announced only 12 hours ahead. | Availability failureThe notice falls short of 24 hours. Calling the outage scheduled maintenance does not satisfy the exclusion. |
| North does not review privileged portal access, so former administrators retain access. | Other trust services concernThe direct weakness is security access control, not uptime or recovery. |
| North's portal runs on one production server with no redundant server or failover. | Availability control or weaknessThe single point of failure threatens continued service, even before an outage occurs. |
| North's sole portal server fails during normal operations; stored data remains intact, but customers cannot connect. | Availability failurePreserved data does not make the portal accessible. Service is unavailable during a promised period. |
| North has never tested restoring its portal from backups. | Availability control or weaknessUntested restoration creates uncertainty about recovering usable service after a failure. |
Key points
- Remember: intact data does not make an unreachable portal available.
- Judge scheduled maintenance against the notice requirement, not just its label.
- Backups preserve recoverable data; they do not provide immediate processing capacity.
How the exam traps you
- Treating an outage as processing integrity because customers cannot submit orders. If the portal is unreachable, classify the access failure as availability.
- Assuming all scheduled maintenance is excluded downtime. Check whether North gave at least 24 hours of advance notice.
- Assuming nightly backups eliminate availability risk. Check for alternate processing capacity and tested recovery.
Question 2
Hint
Focus on the specific control gap, not on the controls that are already in place.
Answer D. Availability concerns whether a system is accessible for operation and use as committed or agreed. The lack of a tested disaster recovery plan and no redundancy creates a risk that the system will be unusable after an outage, preventing payroll processing. While encryption and access controls address other categories, the main weakness described is downtime and service interruption.
Why not A: This is tempting because the stem mentions encryption and access controls, which are security controls. However, those controls are described as present; the deficiency described (no DR plan or redundancy) creates unavailability, not an increased risk of unauthorized access.
Why not B: Processing integrity relates to whether processing is complete, accurate, valid, and timely. Although delayed payroll could affect timeliness, the root problem described is system unavailability (inability to run payroll), not a failure in processing accuracy or validity.
Why not C: Payroll data confidentiality is important and encryption supports confidentiality, so this distractor is plausible. The stem's control gap, though, is about restoring service after a failure rather than preventing unauthorized disclosure, so confidentiality is not the primary classification.
Question 3
Hint
Focus on the deficiency that most directly affects uptime, resilience, or recovery after a disruption.
Answer D. Availability concerns whether the system is accessible for operation and use as required. A lack of tested failover capability directly threatens uptime and the ability to recover from a hardware failure, making this primarily an availability issue.
Why not A: This is tempting because improper privileged access can lead to serious problems, but it is primarily a security (access control/confidentiality/integrity) issue rather than an availability problem focused on uptime or recovery.
Why not B: This reflects a processing integrity control weakness (accuracy and completeness of processing). The core risk is incorrect or incomplete transaction data, not whether the system is accessible or resilient.
Why not C: This option concerns protection of data in transit and is primarily a confidentiality/control-of-data issue. While it affects data security, it does not directly threaten system availability or recoverability after an outage.
Question 4
Hint
Separate data recovery from operational readiness. Ask what control is missing if the company needs the system running again quickly.
Answer A. This scenario implicates availability: backups help with data recovery, but without an alternate processing site and tested recovery procedures the company may not restore operations quickly. The most likely consequence is prolonged downtime even if data can eventually be recovered.
Why not B: Tempting if a candidate confuses security categories. However, inability to use the system is an availability problem; confidentiality concerns involve unauthorized disclosure, not loss of access after a disaster.
Why not C: Backups enable data restoration but do not provide processing capacity or automatic failover. Without an alternate site or tested failover, significant downtime is still likely.
Why not D: Offsite backups reduce the risk of total data loss; the stem implies data are backed up nightly offsite, so total loss is not the most likely outcome. The bigger issue is restoring operational availability.
Question 5
Hint
Focus on what backups do versus what redundancy or failover does.
Answer C. Availability concerns whether the system and its services are accessible when needed. With a single production server and no failover, a server outage can render the application unavailable to customers even if the stored data itself is intact. Nightly backups help recover data but do not keep the application running during an outage.
Why not A: Inaccuracy relates to integrity or processing errors. The question states stored billing data is not corrupted, so prior transactions being inaccurate is not the direct result of the server going offline.
Why not B: This distractor confuses availability with confidentiality/security. Unauthorized access is primarily a confidentiality issue and is not the most direct consequence of lacking server redundancy.
Why not D: Backups assist with data recovery after a failure but do not prevent downtime or provide continuous service; preventing interruption requires redundancy or automatic failover.
Question 6
Hint
Focus on the specific trust services category that deals with whether a system is available for use as promised, not just on whether strong IT controls exist.
Answer B. Availability concerns whether a system is accessible for operation and use as agreed. The company promised that scheduled maintenance would be announced at least 24 hours in advance but is not providing that notice, so it is failing to meet its availability commitment. Other controls (redundancy, backups) do not change the conclusion that availability obligations are not being met.
Why not A: This distractor tempts candidates who focus on communication, but confidentiality is about preventing unauthorized access or disclosure of information. The fact pattern describes lack of notice about downtime, not exposure of sensitive data, so confidentiality is not the primary issue.
Why not C: Processing integrity relates to completeness, accuracy, and validity of processing. Backups concern recovery and resilience, but the core problem here is system availability (the system is taken offline without the promised notice), not incorrect or invalid processing.
Why not D: This option confuses the presence of controls with whether commitments are met. Even with redundancy and backups, the company is not honoring its stated notification requirement and is taking the system offline, so an availability issue exists.
Common questions
Is a system outage an availability or confidentiality issue?
An unreachable portal is primarily an availability issue when it breaks the service promise. Confidentiality concerns unauthorized disclosure, not authorized users losing access.
Does scheduled maintenance count as an availability failure?
Not when it meets the stated exclusion. North's scheduled maintenance is excluded only if announced at least 24 hours ahead.
Do nightly backups ensure system availability?
No. North may recover its data but still face extended downtime without alternate processing capacity and tested recovery procedures.
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
- When to Trigger Failover: RTO and RPO
- Choose Disaster Recovery Architecture by RTO and RPO
- System Availability: Redundancy and Automatic Failover
- How to Calculate SLA Uptime at 99.95% Availability
- RTO vs RPO: Synchronous vs Asynchronous Replication
- System Availability: Why Backups Do Not Prove Recovery
- Availability Calculation: MTBF, MTTR, and Redundancy
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.