Data Access · interview question

Which naming or modeling choice is strongest for transactions?

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"))

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep transactions implicit so the script stays short and hope the next engineer infers the rule.Use names and structures that describe the business fact directly instead of temporary implementation noise.Solve the symptom with comments only and avoid changing the code shape around transactions.

Answer and explanation

Correct answer

C. Use names and structures that describe the business fact directly instead of temporary implementation noise.

Why

Clear naming and modeling shorten debugging, review, and onboarding time.

Test yourself on Data Access

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

Start free test

All Data Access questions →

Which naming or modeling choice is strongest for transactions?

Correct answer

Why

More Data Access questions