Acid Proporties

The canonical record provides only the phrase "Acid Proporties" and no statement, inputs, examples, or constraints. Do not invent a coding problem. Start by asking whether the interviewer means the database ACID properties. If so, explain atomicity as all-or-nothing transaction effects, consistency as preserving declared invariants, isolation as behavior equivalent to an allowed serial order, and durability as committed data surviving a crash. Use a transfer example: atomicity prevents one-sided debits, consistency prevents invalid balances, isolation prevents conflicting observations, and durability requires a recoverable commit record. Then ask whether they want trade-offs between isolation levels, implementation mechanisms such as write-ahead logging and locks, or a system-design example. Complexity notation is not meaningful until a concrete operation and data model are supplied; say that explicitly rather than fabricating Big-O claims.

Complexity: Once the measurement rule is fixed, validating n samples in one pass is O(n) time and O(1) auxiliary space.