Data Access · interview question

If you wrote a test around transactions, what should the test prove first?

Multiple choiceMediumchapter-11-curatedpremiumdata-accesstransactions

python

with connection:
    connection.execute("INSERT INTO orders(id, subtotal_cents) VALUES (?, ?)", ("ORD-1", 8800))
    connection.execute("INSERT INTO order_events(order_id, event_type) VALUES (?, ?)", ("ORD-1", "CREATED"))

Keep transactions implicit so the script stays short and hope the next engineer infers the rule.Solve the symptom with comments only and avoid changing the code shape around transactions.That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.Delay clarity until production traffic reveals the edge case and then patch it under pressure.

Answer and explanation

Correct answer

C. That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.

Why

Good tests make the design safer to change because they lock in the meaningful behavior rather than surface-level implementation details.

Test yourself on Data Access

A free test with instant, explained results. No account needed.

Start free test

All Data Access questions →

If you wrote a test around transactions, what should the test prove first?

Correct answer

Why

More Data Access questions