Transactions are used to... (Choose 2)

Question

Options

• Aguarantee high performance
• Bsecure data consistency
• Csecure access to the database
• Dreduce the database server overhead
• Ereduce code size in PHP

• B
  78% (14)
• C
  6% (1)
• D
  11% (2)
• E
  6% (1)

Explanation

Transactions enforce the ACID properties (Atomicity, Consistency, Isolation, Durability), which together secure data consistency - ensuring that a database moves from one valid state to another even if errors, crashes, or concurrent operations occur mid-process. Note: the question says "choose 2," but only B is marked correct here, so focus on understanding B deeply.

Why the distractors are wrong:

• A - Transactions add overhead (locking, logging, rollback tracking); they can actually reduce performance in high-throughput scenarios.
• C - Access control is handled by authentication and authorization (users, roles, privileges), not transactions.
• D - Transactions increase server overhead due to write-ahead logs, locks, and rollback buffers.
• E - Transactions are a database concept and have no effect on PHP code length.

Memory tip: Think of a bank transfer - money leaves one account and enters another. A transaction guarantees both steps happen together or neither does, keeping the data consistent. If you see any answer that sounds like "transactions make things faster or smaller," eliminate it immediately - consistency and reliability are what transactions buy you, not speed or brevity.

No community discussion yet for this question.