Data Buddy

Step 1 of 3

Read the evidence

Separate confirmed facts from assumptions before you propose a repair.

The evidence files load with the scenario.

Step 2 of 3

Write your fix

Revise the SQL, count what the delivery records show, and write down what you assumed.

Your task

The starter appends every delivery attempt. Inspect the supplied rows, explain what another run would write, and revise it to preserve the . The dictionary defines the input and proposed destination.

Failure summary

Bounded SQL candidatePractice rows only

INSERT INTO order_events (
  event_id, order_id, line_no, sku, quantity, unit_price
)
SELECT event_id, order_id, line_no, sku, quantity, unit_price
FROM delivery_attempts;

Result on the practice rows

What this candidate would write

Run your SQL on the practice rows to see what it writes to order_events. Nothing else is reachable.

5 linesThe checks run your SQL twice: the delivery, then the retry.

Step 3 of 3

Review what your evidence supports

Four kinds of result come back: passed, needs a person, not simulated, did not pass.

Deterministic checks

Run on the supplied synthetic records only

No checks have run on this draft.

Run the bounded checks from step 2. Any edit after a run clears the old result.