Level 2 — Ask For the Right Thing

10 questions, drawn from a bank of 20 across 18 topics. Pass at 80%. Every wrong option carries a note explaining why it is tempting — those notes are the point of the quiz, so read them whether you pass or not.

attempt 1

1 / 10 · Choose one
Besides the file itself, what else does an @ file reference bring into context?
Besides the file itself, what else does an @ file reference bring into context?
Every module the file imports, resolved recursively, so the reference arrives as a complete dependency pictureThe file’s recent git history, so you can ask why its API ended up this way without running a command firstNothing else — a reference expands to exactly one file’s contents, and any conventions around it have to be loaded separatelyThe CLAUDE.md from that file’s directory and from each of its parent directories
2 / 10 · Choose one
Which rewrite of this prompt supplies scope, rather than merely more words?
terminal
```
add tests for foo.py
```
Which rewrite of this prompt supplies scope, rather than merely more words?
write a test for foo.py covering the edge case where the user is logged out. avoid mocks.when you have a moment, could you please add some tests for foo.py? no rushYou are a senior test engineer with 15 years of experience. Please write excellent, comprehensive, production-quality tests for foo.py.add tests for foo.py covering every function, every branch and every error path, and make sure coverage is 100%
3 / 10 · Choose all that apply
You have a screenshot of a broken layout. Which of these are documented ways to get it into a session? Select all that apply.
You have a screenshot of a broken layout. Which of these are documented ways to get it into a session? Select all that apply.
Drag and drop the image into the promptDescribe the layout problem in words instead — images are not supportedCopy the image and paste it with Ctrl+V — Alt+V on Windows and WSLEncode it as base64 and paste the string into the promptGive the file path and ask Claude to look at it
4 / 10 · Choose one
You have four pages of conventions for the payments module — relevant when anyone touches billing, irrelevant the other ninety percent of the time. Where do they belong?
You have four pages of conventions for the payments module — relevant when anyone touches billing, irrelevant the other ninety percent of the time. Where do they belong?
Comments in the payments source files, where the code that needs them livesA hook, so the payments conventions are enforced by a script, not suggestedCLAUDE.md, so all four pages are guaranteed to be in context on the sessions that touch billingA skill, which Claude loads when it is relevant instead of on every conversation
5 / 10 · Choose one
You open a session with "investigate how our authentication works" and no further constraint. What does the documentation call this, and what is the fix?
You open a session with "investigate how our authentication works" and no further constraint. What does the documentation call this, and what is the fix?
The trust-then-verify gap — a plausible implementation that does not handle the edge cases. Always provide verification, and do not ship what you cannot verifyThe infinite exploration — Claude reads hundreds of files, filling the context. Scope the investigation narrowly, or hand it to subagentsThe kitchen sink session — one window carrying several unrelated tasks. The fix is /clear between themNot a documented failure — asking a codebase the questions you would ask a colleague is how people learn an unfamiliar codebase
6 / 10 · Choose one
Which statement about this command is true?
terminal
```
git diff main | claude -p "report any typos in this diff"
```
Which statement about this command is true?
Claude still needs Bash permission, because reading from a pipe is a shell operation the permission system gatesClaude never needs Bash permission to obtain the diff — the data arrives as input rather than as the result of a tool callIt opens an interactive session with the diff already loaded, ready for follow-up questions about the same diffThe piped data is ignored unless an input-format flag is passed as well, so as written -p answers from the prompt alone
7 / 10 · Put these in order
Put the documented workflow for a large, under-specified feature into order.
1. 1Answer the questions until the coverage is complete, including the ones about edge cases and tradeoffs you had not considered
2. 2Send a minimal prompt describing the feature and ask to be interviewed with the AskUserQuestion tool
3. 3Start a fresh session and execute the spec there
4. 4Have Claude write the whole conversation out as a complete, self-contained spec in SPEC.md
8 / 10 · Choose one
The same documentation page says to describe the symptom, and also to address the root cause rather than the symptom. How do both hold at once?
The same documentation page says to describe the symptom, and also to address the root cause rather than the symptom. How do both hold at once?
They do conflict, and the second supersedes the first — lead with your best theory of the cause so the search starts where it mattersThe first applies to small bugs where the cause is obvious and the second to serious ones where it is notThe first is advice for whoever reports the bug and the second for whoever fixes it, so in any one session only one of them is addressed to youThey govern different directions: report symptoms rather than your diagnosis going in, and require causes rather than suppression coming back
9 / 10 · Choose all that apply
The documented rewrite of "fix the login bug" supplies three things. Which of these are among them? Select all that apply.
The documented rewrite of "fix the login bug" supplies three things. Which of these are among them? Select all that apply.
The urgency and who reported it, so the work can be prioritisedYour conclusion about the root cause, stated up front so the search can start thereWhat "fixed" means — write a failing test that reproduces the issue, then fix itThe observable symptom — login fails after session timeoutA likely location, offered as a hint — check the auth flow, especially token refresh
10 / 10 · Choose one
You try to pipe a 40MB production log into claude -p. What happens, and what is the documented alternative?
You try to pipe a 40MB production log into claude -p. What happens, and what is the documented alternative?
The input is silently truncated at the 10MB mark and the run proceeds on the first part, so the answer describes the head of the log and says so nowhereClaude Code splits oversized stdin into chunks and works through them over several turns, then reports a single answer covering the whole 40MB fileThere is no separate cap — piped input is bounded only by the context window, and compaction absorbs whatever does not fitPiped stdin is capped at 10MB, so the run exits with a clear error and a non-zero status. Write the log to a file and name that path in the prompt

9 questions still to answer