If concurrent update transactions to an account are not processed properly, which of the following will be affected?

Question

Options

• AAccountability
• BAvailability
• CIntegrity
• DConfidentiality

• B
  3% (1)
• C
  90% (28)
• D
  6% (2)

Explanation

Integrity is correct because it refers to the accuracy and consistency of data. When concurrent update transactions on the same account are not properly controlled (e.g., via locking or serialization), two processes can read the same value, each modify it independently, and one update overwrites the other - leaving the data in an incorrect, inconsistent state. This is the classic "lost update" problem.

Availability (B) is wrong because the data is still accessible - the problem isn't that users can't reach it, but that what they see is inaccurate. Confidentiality (D) is wrong because no unauthorized disclosure of information occurs; both transactions are legitimate. Accountability (A) is wrong because the issue isn't about tracing actions to individuals - audit trails may still function correctly even when concurrent updates corrupt data.

Memory tip: Think of Integrity = correctness of data. Any time a question describes a scenario where data ends up with the wrong value (race conditions, lost updates, dirty reads), integrity is the answer. Confidentiality = who sees it, Availability = can you get to it, Accountability = who did it.

No community discussion yet for this question.