A bank transfer takes money from one account but the system crashes before adding it to the other. Which property prevents loss?
- Either both steps happen or neither does.
- The partial change is rolled back.
- Atomicity.
Answer Atomicity
A-level Computer Science revision · Exchanging data
A transaction is a single logical operation. ACID properties keep databases reliable: Atomicity (all or nothing), Consistency (rules are kept), Isolation (concurrent transactions do not interfere) and Durability (committed changes survive failures). Record locking prevents two users updating the same record at once. Redundancy (copies on separate systems) protects against failure.
Watch out Atomicity means a transaction cannot be half-completed; it is fully done or fully rolled back.
A bank transfer takes money from one account but the system crashes before adding it to the other. Which property prevents loss?
Answer Atomicity
Which ACID property ensures committed changes survive a power cut?
What problem does record locking prevent?
Explain deadlock in databases.
Answer Two transactions each lock a record the other needs, so both wait forever; the DBMS must detect this and roll one back.
A-level Computer Science Pro, OCR H446
£119 once
Price rises to £199 on 1 January. Save £80 by joining before then.
At least 12 months of access
No VAT is charged.