A bank needs to ensure that a transaction involving debiting funds from a source account and crediting the same funds to a destination account must complete both actions. If either action falls to…

Consistency ensures data moves from one valid state to another according to defined rules and constraints, but does not govern whether both operations must succeed or fail together.

Durability ensures committed data persists after system failures, addressing post-commit persistence rather than all-or-nothing execution.

Atomicity guarantees that a transaction is treated as a single atomic unit of work - either all operations within the transaction commit successfully, or none of them do. In this banking scenario, the debit from the source account and the credit to the destination account are wrapped in one atomic transaction, so a failure in either operation causes the entire transaction to roll back, preventing partial updates.

Isolation controls how concurrent transactions interact with each other's intermediate states, not whether the operations within a single transaction all succeed or fail together.