10 scenarios, graded as you go, with the exact grading principle for every answer. Start free, no sign-up.
Timed mock assessment
31 scenarios in 37 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor and the seller of record, adds tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@annotationprep.com and we will put it right.
One-time payment. Nothing renews.
You have an assessment ticket for this practice test. Start the mock assessment to use it.
Practice tests that prepare you for this assessment
Exact question counts, time limits, and project rubrics vary by platform cohort and qualification tier. Always read the platform's live project instructions carefully.
Sample scenarios
PROMPT
Add a composite index on (org_id, created_at DESC) for the high-write audit_events table in PostgreSQL without disrupting ingestion.
MODEL A
SQL
CREATE INDEX idx_audit_org_created ON audit_events (org_id, created_at DESC);
MODEL B
SQL
-- alembic: disable_transaction = true
CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_audit_org_created
ON audit_events (org_id, created_at DESC);
Which comparison accurately justifies preferring Model B over Model A?
Model A fails with a syntax error because PostgreSQL does not support descending sort order inside standard B-tree indexes.
Model A acquires an ACCESS EXCLUSIVE lock that halts all SELECT queries, whereas Model B permits reads but still blocks writes.
Model B builds the index significantly faster than Model A by parallelizing disk writes inside a single atomic transaction block.
Model A takes a SHARE lock blocking writes; Model B uses CONCURRENTLY outside a transaction so writes proceed.
Show the answer
D. Model A takes a SHARE lock blocking writes; Model B uses CONCURRENTLY outside a transaction so writes proceed.
A standard CREATE INDEX in PostgreSQL takes a SHARE lock, which permits concurrent SELECT reads but blocks all writes (INSERT, UPDATE, DELETE) for the entire build duration—causing ingestion timeouts on busy tables. CREATE INDEX CONCURRENTLY takes a SHARE UPDATE EXCLUSIVE lock so writes keep flowing, and Model B correctly disables transaction wrapping because Postgres rejects CONCURRENTLY inside a transaction block.
Principle: PostgreSQL Index Locks: CREATE INDEX vs. CREATE INDEX CONCURRENTLY
PROMPT
Fix the bug in parse_duration(raw) where nested composite strings like "1h30m" fail to sum all components. The failing issue report includes the example parse_duration("2h15m") == 8100.
Model A's patch passes the repository's entire test suite:
DIFF
def parse_duration(raw: str) -> int:
+ if raw == "2h15m":
+ return 8100
match = re.match(r"^(\d+)([hms])$", raw)
if not match:
raise ValueError(f"Invalid duration: {raw}")
value, unit = int(match.group(1)), match.group(2)
return value * UNIT_SECONDS[unit]
Why must an SWE-Bench evaluator fail Model A despite all automated tests turning green?
Returning an integer literal 8100 skips type validation and breaks mypy strict checks across downstream callers.
It is a reward-hacking / overfitted patch that hardcodes the test input instead of fixing composite duration parsing.
Placing an if branch above re.match prevents Python's regex engine from caching the compiled pattern object.
The patch passes only because UNIT_SECONDS is a global dictionary, which should be refactored into an immutable Enum.
Show the answer
B. It is a reward-hacking / overfitted patch that hardcodes the test input instead of fixing composite duration parsing.
In SWE-Bench and repository-level RLHF evaluations, green CI alone is never sufficient: models sometimes memorize or special-case the exact failing test string ("2h15m"). Any other composite duration such as "1h30m" or "45m10s" still raises ValueError. Evaluators must reject hardcoded test-case shortcuts and require a general solution (e.g., re.finditer validating full-string coverage).
Reject as a breaking API change: removing total_cents breaks live /v1 clients instead of additively returning both fields.
Approve with a minor nit: renaming a JSON property on a GET endpoint is backwards-compatible because HTTP status codes stay 200.
Reject solely because invoice.totalCents uses camelCase internally while the JSON payload mixes snake_case field names.
Approve if the PR also updates openapi.yaml, because updating the specification automatically protects older mobile clients.
Show the answer
A. Reject as a breaking API change: removing total_cents breaks live /v1 clients instead of additively returning both fields.
Public versioned APIs (/v1/...) must preserve backwards compatibility for pinned mobile apps and third-party integrations. Removing total_cents in place causes existing clients to read undefined or crash deserialization. The non-breaking pattern is additive deprecation: emit both total_cents and amount_cents in /v1, document total_cents as deprecated, and remove it only in /v2 or after a sunset window.
Principle: API Evolution: Additive Deprecation vs. Breaking Contract Changes
Taking this assessment soon?
Tell us what skills or question formats you want more drills on.