Review six database control claims

Objectives

The clinic's release lead calls all six claims audit-ready because each came from a successful deployment. Review the actual mechanisms and test evidence, not that label.

Accept supported claims. Reject each unsupported claim with its single root-cause code: relationship-gap for missing reference enforcement, excessive-privilege for unnecessary authority, unproven-recovery for absent restoration evidence, or audit-gap for a trail the monitored account can erase. Leave accepted reasons empty.

Verdicts are accept or reject. Every rejection needs one reason code from: relationship-gap | excessive-privilege | unproven-recovery | audit-gap.

DBA-1 | appointments.patient_id is required and has an enforced foreign key to patients.patient_id; an orphan insert test fails as intended.
DBA-2 | A non-unique index on appointments.patient_id is the only relationship mechanism; the lead says it prevents orphan records.
DBA-3 | The reporting runtime needs SELECT on a restricted view but also receives database-wide write and schema-change permissions for convenience.
DBA-4 | Daily backup jobs succeed; no restoration has ever been attempted. The lead claims the 60-minute restoration objective is proven.
DBA-5 | Authentication, privilege changes and sensitive reads are audited, but the runtime account can delete the only stored event copies.
DBA-6 | An isolated drill restored a base backup and replayed the complete archived log chain to before a deletion; integrity checks passed, measured loss was 2 minutes and recovery took 38 minutes against 5-minute and 60-minute targets.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

1. Step 1

   Read the request before the artefact

   Treat each ledger line as one claim. Compare its mechanism or test to the property it purports to prove.

2. Step 2

   Judge every line, including the boring ones

   Visit every identifier once and give it a verdict. Leave the reason field empty for claims you accept.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Separate lookup performance from relationship enforcement, convenience from necessary authority, copy creation from demonstrated restoration, and event capture from protected retention. Compare drill measurements with their corresponding objectives.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Choose the code for the control that actually fails. A problem with what a runtime identity may do differs from a problem with how its actions are retained.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  40 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 10 XP).

• Reveal solution

  Scores 0 XP and unlocks only after 3 check runs.

• Attempt cap

  60 check runs per learner. The runner warns you in the last 10.

• Drafts

  Your editor content is saved in this browser, so a reload will not lose work.

• Walkthrough

  Always free and never penalised: use it before spending a hint.