Mode disclosure
All modes use one coherent workspace; only disclosure and guidance change. Review mode hides concept labels until submission, keeps a due counter visible, and lets you Skip for Later without losing work.
Scalar and Set Subqueries / predict result
RE-A01 - Use a scalar subquery with the correct comparison population
RE-A01 - Use a scalar subquery with the correct comparison population. Use nested queries when scalar or one-column set shape is clearest.
- Result grain
- one row per scan
- Exact columns
- scan_id; package_id; scan_type; ingest_delay_minutes
SQL editor shortcuts: Ctrl or Command Enter runs the query, Ctrl or Command Shift Enter checks it, Alt H opens the next hint, Ctrl or Command slash toggles a line comment, Ctrl or Command Shift F formats the SQL, and Escape closes transient UI.
Cursor at line 1, column 1.
Scenario
Retrieve the skill without relying on the lesson label.
Review mode / concept labels hidden until submission
One-sentence task
RE-A01 - Use a scalar subquery with the correct comparison population. Use nested queries when scalar or one-column set shape is clearest.
Review mode disclosure
Concept labels hidden until submission. Use the due counter and Skip for Later without losing the draft.
Structured output contract
- Result grain
- one row per scan
- Exact columns
- scan_id; package_id; scan_type; ingest_delay_minutes
- Source population
- Use the prompt setup plus FROM, JOIN, WHERE, and subquery predicates as the source population. Visible rows are only examples.
- Grouping
- Do not collapse rows unless the contract explicitly asks for aggregation, distinct tuples, or set semantics.
- Ordering
- No display order requirement unless Check reports one.
- Validation
- select-only; hidden deterministic variants.
Relevant tables
Time and difficulty
- Estimated time
- 6 minutes
- Difficulty
- 5/5
Objective and concepts
Concept labels are hidden until submission so retrieval stays honest.
Assumptions, dialect notes, and common traps
- Duplicate policy
- Preserve duplicate facts unless the prompt explicitly asks for distinct tuples or set semantics.
- Null policy
- Preserve NULL, empty string, zero, and false as distinct values unless the contract says to display a fallback.
- Tie-breakers
- Use every ordering rule in the contract and end tied business metrics with deterministic secondary keys when needed.
- Zero-related entities
- Do not invent zero rows unless the contract asks for preserved parents, missing entities, or complete periods.
- Numeric tolerance
- Round only at the requested final stage; hidden checks use the contract precision rather than visible formatting luck.
Opened hints
Hints are disabled during active review or challenge assessment and become available after submission or outside assessment mode.