Data Access · interview question

If you wrote a test around basic sqlite queries, what should the test prove first?

Multiple choiceEasychapter-11-curatedpremiumdata-accessbasic-sqlite-queries

python

import sqlite3

connection = sqlite3.connect("orders.db")
rows = connection.execute("SELECT id, subtotal_cents FROM orders").fetchall()

Delay clarity until production traffic reveals the edge case and then patch it under pressure.That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.Keep basic sqlite queries 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 basic sqlite queries.

Answer and explanation

Correct answer

B. 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 basic sqlite queries, what should the test prove first?

Correct answer

Why

More Data Access questions