Cyber Security Quiz: Cia Triad
10 questions · exam conditions
0:00
Cia TriadQuestion 1 of 10

A software vendor publishes an installer and its SHA-256 hash on the same web server. An attacker who compromises the server replaces both the installer and the displayed hash. The vendor then changes its process so that an offline signing key signs a release manifest containing the installer hash.

What is the most accurate security effect of the revised process?

It makes the installer confidential in transit but leaves authenticity dependent on the web server.
It guarantees installer availability because users can reconstruct the installer from the signed manifest.
It lets users detect unauthorized replacement if they independently trust the signing key, but it does not conceal the installer.
It prevents a compromised build system from creating malicious installers because every release manifest is digitally signed.
← Back to quizzes

Cyber Security Quiz

Cyber Security Quiz: Cia Triad

Practice Cia Triad in Cyber Security with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Cia Triad, giving you a quick way to practice the rules, question types, and explanations that matter most for Cyber Security.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A software vendor publishes an installer and its SHA-256 hash on the same web server. An attacker who compromises the server replaces both the installer and the displayed hash. The vendor then changes its process so that an offline signing key signs a release manifest containing the installer hash.

What is the most accurate security effect of the revised process?

  1. It makes the installer confidential in transit but leaves authenticity dependent on the web server.
  2. It guarantees installer availability because users can reconstruct the installer from the signed manifest.
  3. It lets users detect unauthorized replacement if they independently trust the signing key, but it does not conceal the installer. (correct answer)
  4. It prevents a compromised build system from creating malicious installers because every release manifest is digitally signed.
Explanation: When a question involves digital signatures and file integrity, your job is to precisely map what each security control actually provides — and what it doesn't. The CIA triad (Confidentiality, Integrity, Authenticity, Availability) is your framework here. The revised process uses an offline signing key to sign a manifest containing the installer's hash. The critical word is offline — the signing key never touches the compromised web server. Even if an attacker replaces the installer and its displayed hash on the server, they cannot forge a valid signature without the private key. A user who independently trusts the vendor's public key can verify the signature, detect the mismatch between the signed hash and the tampered installer, and refuse it. Crucially, signing provides authenticity and integrity, not confidentiality — the installer contents remain visible to anyone who downloads them. This makes C the most accurate description. A is wrong because digital signing doesn't encrypt the installer or provide confidentiality in transit — that would require TLS or encryption. Authenticity is no longer dependent on the web server once the signature is verified independently. B is a fabrication. A signed manifest contains a hash of the installer, not the installer itself. You cannot reconstruct binary software from a cryptographic digest — that's not what hashes do. D overstates the protection. Signing attests to what was released, but if the build system is compromised before signing occurs, a malicious artifact could still be signed legitimately. Signing doesn't sanitize upstream pipeline integrity. Study tip: On security exams, watch for answers that conflate integrity/authenticity with confidentiality or availability — these are distinct properties, and digital signatures address only the first two.

Question 2

A document portal normally consults an authorization service before displaying confidential files. Management proposes a fail-open mode: if the authorization service is unavailable, any employee with a valid portal session may view requested files until service is restored.

Which CIA tradeoff does the proposed fail-open mode most directly create?

  1. It favors integrity over availability by preventing authorization records from being changed during the outage.
  2. It favors confidentiality over availability by blocking file access when authorization cannot be confirmed.
  3. It favors integrity over confidentiality by allowing authenticated employees to correct authorization failures.
  4. It favors availability over confidentiality by continuing access without confirming each employee's authorization. (correct answer)
Explanation: When you see a question about system design decisions and security, ask yourself: which of the three CIA pillars — Confidentiality, Integrity, and Availability — is each design choice prioritizing or sacrificing? That lens makes this question straightforward. The proposed fail-open mode keeps the portal running even when the authorization service is down, meaning employees can access files without their permissions being verified. The system is choosing to stay available at the cost of confidentiality — sensitive files may reach employees who aren't actually authorized to see them. That's a classic availability-over-confidentiality tradeoff, which makes D the correct answer. A is wrong on two levels: fail-open doesn't protect authorization records from modification, and integrity isn't meaningfully involved here at all. The scenario is about reading files, not changing them or their associated records. B describes the opposite design — a fail-closed or fail-secure mode, where access is blocked when authorization can't be confirmed. That approach favors confidentiality over availability, which is actually the safer security posture, but it's not what management proposed. C introduces integrity again without justification; allowing employees to view files during an outage has nothing to do with correcting authorization failures or modifying data. A handy study tip: on security exams, "fail-open" almost always signals an availability-over-confidentiality tradeoff, while "fail-closed" (or "fail-secure") signals the reverse. Memorize these two terms and their security implications — they appear frequently in questions about system resilience, access control, and risk management.

Question 3

A hospital email gateway quarantines every encrypted attachment because it cannot inspect the contents for patient data. This prevents staff from bypassing data-loss prevention controls, but it also delays encrypted pathology reports sent between authorized clinicians.

Which statement best characterizes the gateway policy?

  1. It improves integrity by validating report contents, while reducing confidentiality through centralized inspection.
  2. It improves availability by ensuring reports remain queued, while weakening integrity through delivery delays.
  3. It prioritizes confidentiality controls, but it can reduce availability of information to authorized recipients. (correct answer)
  4. It prioritizes integrity controls, but it can reduce confidentiality because authorized reports are quarantined.
Explanation: When you see a question involving competing security goals, immediately reach for the CIA triad — Confidentiality, Integrity, and Availability. The key is identifying which property each policy action actually targets, then recognizing the trade-off it creates. Here, the gateway quarantines encrypted attachments because it cannot inspect them. The goal isn't to validate the data's accuracy — it's to prevent unauthorized data disclosure by blocking content that evades DLP inspection. That's a confidentiality control. The unintended consequence is that legitimate, authorized clinicians don't receive time-sensitive pathology reports promptly — that's a hit to availability, which means the right information reaching the right people at the right time. This makes C the best answer: the policy prioritizes confidentiality controls at the cost of availability to authorized recipients. A is wrong on two counts: the gateway isn't validating report contents (that would be integrity), and quarantining protects confidentiality rather than reducing it. B misidentifies "queuing" as an availability improvement — a delayed or quarantined report isn't available; it's withheld. Availability means timely access, not storage in a queue. D claims the policy prioritizes integrity, but there's no mechanism here checking that reports are accurate or unaltered. Integrity controls involve hashing, digital signatures, or checksums — none of which apply to this gateway's behavior. Your study tip: on security exam questions, watch for policies that block or restrict access — those almost always touch confidentiality. Any time authorized users can't get something they need, that's an availability impact. Don't let the word "quarantine" trick you into thinking "integrity."

Question 4

To withstand a request-flooding attack, a public service limits each source IP address to 20 requests per minute. The attack subsides, but 300 employees at a branch office share one public IP address and many of their legitimate requests are rejected.

Which statement best describes the result?

  1. The control improves confidentiality by hiding branch traffic, but it weakens integrity by rejecting valid requests.
  2. The control improves integrity by distinguishing attack traffic, but it weakens confidentiality for shared-IP users.
  3. The control protects aggregate availability from flooding, but it reduces availability for legitimate users behind shared addresses. (correct answer)
  4. The control protects confidentiality from flooding, but it reduces integrity because rejected requests are automatically altered.
Explanation: Whenever you see a question involving security controls and unintended side effects, anchor your thinking to the CIA triad — Confidentiality, Integrity, and Availability — and ask which pillar the control is actually targeting and which it accidentally impacts. Here, rate-limiting per source IP is a classic availability protection: it prevents a flood of requests from overwhelming a service. That's the intended benefit. The unintended cost surfaces because 300 employees share one public IP address through NAT, so their combined legitimate traffic easily exceeds the 20-requests-per-minute threshold. Legitimate users get blocked — meaning availability is reduced for them. The control simultaneously protects aggregate availability (from attackers) and degrades it for a specific group (branch employees). Answer C captures both sides of this tradeoff precisely. A is wrong because rate-limiting has nothing to do with confidentiality — it doesn't hide traffic or protect data from disclosure — and rejecting requests doesn't affect integrity. B is wrong for a similar reason: distinguishing attack traffic is an availability concern, not an integrity one, and shared-IP users lose availability, not confidentiality. D is wrong on both counts: flooding attacks don't threaten confidentiality, and rejected requests are simply dropped — they aren't "altered," which would be an integrity violation. A useful study tip: on security exams, availability questions often involve denial-of-service, rate-limiting, and redundancy scenarios. If you see flooding attacks or rejected requests, your first instinct should be to think availability, not confidentiality or integrity. Misidentifying the affected CIA pillar is the most common trap in questions like this.

Question 5

Ransomware encrypts a company's production database after attackers copy customer records to an external server. Administrators restore the database from an offline, immutable backup whose contents are verified against a trusted pre-incident snapshot.

Which statement best describes the CIA objectives achieved by the restoration?

  1. It restores availability and supports integrity, but it does not reverse the earlier confidentiality breach. (correct answer)
  2. It restores confidentiality and availability, but immutable backups cannot provide evidence of data integrity.
  3. It restores integrity and confidentiality, but availability remains lost because production data was previously encrypted.
  4. It restores all three objectives because a verified backup replaces both the encrypted and exfiltrated copies.
Explanation: When analyzing an incident through the CIA triad lens, you need to evaluate each pillar — Confidentiality, Integrity, and Availability — independently against what actually happened, not just what the recovery accomplished. Here, two distinct events occurred: the ransomware encrypted the database (an availability and integrity attack), and the attackers exfiltrated customer records before encryption (a confidentiality breach). The restoration addresses some of these, but not all. The verified, immutable backup confirms the restored data matches a trusted pre-incident state, which restores integrity. Bringing the database back online restores availability. However, the customer records that were already copied to the attacker's external server are still in unauthorized hands — no backup restoration can "un-leak" data. The confidentiality breach persists. This makes A the correct answer. Choice B is wrong because it claims confidentiality is restored, which is impossible — the exfiltrated data remains compromised regardless of what happens internally. It also falsely claims immutable backups can't support integrity verification; in fact, comparing against a trusted snapshot is a core integrity mechanism. Choice C incorrectly states availability remains lost — restoring from backup is precisely how availability is recovered. Choice D is the most dangerous distractor: it conflates replacing an encrypted local copy with reversing exfiltration. Replacing the encrypted database doesn't affect the attacker's external copy at all. A useful study habit: always separate what the attack did from what the recovery does. On exam questions involving multi-stage incidents, each CIA pillar may be affected differently — and restoration fixes local damage, never remote exfiltration.

Question 6

A hospital encrypts all patient records. The decryption keys are held by a key-management service in one data center. During a network outage, the records remain encrypted and unmodified, but clinicians cannot retrieve them. The hospital proposes a replicated key-management service in two regions with identical access policies.

Which assessment of the proposal is most accurate?

  1. It primarily improves integrity because replicated keys can detect unauthorized changes to patient records.
  2. It primarily improves availability, while potentially increasing confidentiality risk through a larger attack surface. (correct answer)
  3. It primarily improves confidentiality because distributing keys prevents either region from decrypting records alone.
  4. It improves all three CIA objectives equally because regional replication eliminates the original single point of failure.
Explanation: When a question describes a change to system architecture, train yourself to evaluate it through the CIA triad lens — Confidentiality, Integrity, and Availability — and ask: what problem does this change solve, and what new problems does it create? Here, the core issue is that a single key-management service caused clinicians to lose access during an outage. The proposed fix — replicating the service across two regions — directly addresses that single point of failure, meaning records become accessible even if one region goes down. That is a textbook availability improvement. However, replication also means the decryption keys now exist in more locations, more network paths, and more infrastructure components. Each additional copy is a potential target, so the attack surface grows, introducing confidentiality risk. Answer B captures both effects accurately and is the correct choice. Answer A is wrong because replication has nothing to do with detecting unauthorized changes — that describes integrity mechanisms like hashing or digital signatures, not key distribution. Answer C misreads the proposal entirely: both regions hold identical keys with identical access policies, meaning either region can independently decrypt records. That actually weakens confidentiality compared to a single-location model, rather than protecting it. Answer D is tempting because replication does eliminate the single point of failure, but it does not improve integrity at all (nothing in the proposal addresses data modification), so claiming all three CIA objectives improve equally is factually unsupported. A useful rule of thumb: redundancy improves availability but multiplies attack surface. Whenever a proposal involves copying or distributing sensitive material, availability goes up and confidentiality risk often follows.

Question 7

An internal reporting site uses a content delivery cache for confidential reports. Authorization is checked only when a report enters the cache, and cached copies remain available for 30 minutes. An employee's access is revoked, but the employee can still retrieve a previously cached report by its URL.

Which change best addresses the demonstrated CIA tradeoff while retaining most caching benefits?

  1. Sign each cached report so revoked employees can verify that its contents have not changed.
  2. Encrypt the connection to the cache so report URLs and contents are protected while in transit.
  3. Increase cache duration so reports remain available even when the authorization service is offline.
  4. Revalidate authorization on each request while continuing to serve approved content from the cache. (correct answer)
Explanation: When you see a question about caching and access control, think about the CIA triad — specifically the tension between Confidentiality (only authorized users see data) and Availability (systems remain fast and accessible). Caching improves availability and performance, but if authorization is only checked once at cache entry, revoked users can still access stale content. The challenge is closing that security gap without eliminating the performance benefits of caching. Option D resolves this precisely: by revalidating authorization on every request while still serving content from cache, you get the best of both worlds. The cache still handles the heavy lifting of storing and delivering report data quickly, but the authorization check ensures a revoked employee's next request is denied — even if the cached content exists. This is sometimes called a cache-with-revalidation pattern, and it directly addresses the confidentiality breach described in the passage. Option A is a distractor that conflates integrity with confidentiality. Signing reports proves the content hasn't been tampered with, but it does nothing to prevent a revoked employee from reading it. Option B addresses transit security (encrypting the connection), which protects data from eavesdroppers on the network — but the attack here happens after delivery, not during it. The revoked employee already has the URL and can request the content directly. Option C is actively harmful: extending cache duration makes the problem worse by keeping unauthorized access available even longer. A useful pattern to remember: when a question asks about fixing an authorization bypass, look for the answer that adds or enforces an access check at request time, not one that protects data integrity or encrypts the channel.

Question 8

A payment service writes each transaction synchronously to a central audit server. When that server fails, payment processing stops. Engineers propose writing audit events to a locally append-only, digitally signed queue and forwarding them to the central server asynchronously.

Which assessment of the proposal is most accurate?

  1. It improves payment availability and preserves evidence of alteration, although destruction of a local queue could still remove events before central forwarding occurs. (correct answer)
  2. It improves confidentiality because locally signed events cannot be read by administrators until after they have been forwarded to the central audit server.
  3. It guarantees audit integrity because digital signatures prove that every transaction generated a corresponding audit event that cannot be omitted.
  4. It reduces payment availability because asynchronous forwarding requires both the local queue and the central audit server to be simultaneously online.
Explanation: When evaluating architectural changes to security-sensitive systems, you need to assess impacts across three dimensions simultaneously: availability, integrity, and confidentiality — and recognize that no single control is ever perfect. The proposed local queue breaks the tight coupling between payment processing and the central audit server. If the central server goes down, payments can still be processed and events are buffered locally — a clear availability improvement. The append-only structure with digital signatures means any tampering with queued records will be detectable, since altering a signed event invalidates its signature. This preserves evidence of alteration, which is exactly what A claims. However, A correctly acknowledges a real residual risk: if the local machine is destroyed (hardware failure, fire, malicious wipe) before forwarding completes, those audit events are permanently lost. This is an honest, well-scoped assessment — which is why A is correct. B is wrong because digital signatures address integrity, not confidentiality. Signing an event does not encrypt it or prevent administrators from reading it locally; those are entirely separate controls. C is wrong because it overclaims. Digital signatures prove events haven't been altered, but they cannot prove that every transaction generated an audit event in the first place. A compromised or buggy system could simply skip writing to the queue — no signature exists on an event that was never created. D is wrong because it misunderstands asynchronous architecture entirely. The whole point of async forwarding is that local processing and central forwarding are decoupled, so both systems do not need to be online simultaneously. Study tip: On security architecture questions, watch for answers that confuse integrity (tamper evidence) with completeness (proof nothing was omitted) — they are related but distinct properties.

Question 9

An industrial sensor sends readings through mutually authenticated TLS. An attacker compromises the sensor itself and uses its valid credentials to transmit fabricated temperatures. The monitoring server accepts the readings because the TLS session and message authentication are valid.

Which conclusion is most accurate?

  1. Confidentiality failed because fabricated readings demonstrate that the TLS encryption was successfully bypassed by the attacker during transmission.
  2. Transport confidentiality and integrity may still hold, but they do not ensure the semantic integrity of data originating from a compromised endpoint. (correct answer)
  3. Availability failed because the server received fabricated readings instead of receiving accurate, operationally useful readings from the sensor.
  4. Message integrity remains fully assured because valid credentials prove the temperature values were generated by trusted, unmodified sensor hardware.
Explanation: When analyzing security failures, you need to distinguish between where a security control operates and what it actually protects. Cryptographic controls like TLS secure the communication channel — they don't validate whether the data traveling through that channel is truthful or generated by legitimate hardware. In this scenario, the attacker has compromised the sensor itself, meaning they possess valid credentials and can generate authenticated TLS sessions. The transport layer is doing exactly what it was designed to do: ensuring that data travels encrypted and unaltered between the sensor and server. The problem isn't the channel — it's the source. B is correct because it precisely identifies this gap: transport confidentiality and integrity can remain intact while the semantic integrity of the data (its meaning and truthfulness) is completely undermined. Cryptography cannot vouch for the honesty of a compromised endpoint. A is wrong because TLS encryption was never bypassed — the attacker didn't intercept or modify traffic in transit. They simply used the sensor's legitimate credentials to inject false data at the source. C misidentifies the failure as an availability issue. Availability concerns whether services are accessible; the server received data and processed it normally, so availability was unaffected. D represents a dangerous misconception: valid credentials prove identity (that a known device sent the data), not integrity of the hardware's output or the truthfulness of the readings. A compromised device can still present valid credentials. For your exam, remember this pattern: authentication and encryption operate at the channel level, not the content level. A "trusted" endpoint that has been compromised can weaponize its own legitimacy — this is the core challenge of endpoint security.

Question 10

A replicated inventory system normally requires a majority of replicas to approve each write. During a network partition, engineers propose allowing both isolated sites to accept updates independently and later resolving conflicts using a last-writer-wins rule.

What is the primary CIA implication of this change?

  1. Confidentiality improves because each site sees only the updates submitted within its network partition.
  2. Availability improves, but integrity may weaken because valid concurrent updates can conflict or be discarded. (correct answer)
  3. Integrity improves because the most recent timestamp always identifies the operationally correct inventory value.
  4. Availability weakens because accepting writes at both sites creates an additional dependency on later reconciliation.
Explanation: Whenever you see a question mixing distributed systems design with security, anchor your thinking in the CIA triad — Confidentiality, Integrity, and Availability — and ask which pillar each proposed change actually affects. The scenario describes a shift away from majority-quorum writes (which enforce consistency) toward independent writes at both partitioned sites, reconciled later using last-writer-wins (LWW). This is a classic CAP theorem trade-off: you're sacrificing consistency to gain availability during a partition. Under LWW, whichever update carries the latest timestamp "wins" — but timestamps can be skewed, manipulated, or simply wrong, meaning legitimate updates can be silently overwritten. The system stays up and accepting writes (availability improves), but the accuracy of the inventory data is now at risk (integrity weakens). That's precisely what B captures. A is wrong because network partitioning doesn't change who can see the data — it affects write coordination, not read access or confidentiality controls. Conflating network isolation with access restriction is a common trap. C is wrong because timestamps do not guarantee operational correctness. A more recent timestamp only means the write happened later, not that it represents the true inventory state. LWW can discard valid updates, making integrity worse, not better. D is wrong because accepting writes at both sites actually increases availability — the opposite of what D claims. Post-reconciliation is a complexity cost, but it doesn't make the system less available during the partition. Study tip: On CIA questions involving distributed systems, remember that techniques boosting availability during failures (like LWW or eventual consistency) almost always introduce integrity trade-offs — they're structurally linked.