CCAO-F - Configuration and Knowledge Management (12% of the exam) - Section 5.3

Create effective system-level instructions.

Writing standing instructions, such as Project instructions, that set role, tone, audience, format and boundaries once, so individual prompts can stay short. Candidates should distinguish what belongs in standing instructions from what belongs in a single request.

standing instructionsrole and toneboundariesinstructions versus one-off requests

Practice question for this objective

Free sampleConfiguration and Knowledge Managementmedium

The head of geography at a secondary school uses a Project to build lesson resources. At the start of each chat she types the same paragraph: pitch it for Year 9, use a starter, main activity and plenary structure, and include one idea for pupils who need extra support. Two colleagues are about to start using the same shared Project and should get resources in that format without being told. What should she change?

APut the paragraph into the project instructions so it shapes each chat in the Project for whoever uses it. Correct
BUpload the paragraph to the project knowledge as a short document titled "House style".
CSave the paragraph to her Memory so Claude applies it whenever she builds lesson resources.
DKeep the paragraph in a shared department document for each teacher to paste in at the start.

Standing directions about audience, structure and format belong in project instructions, which apply to every chat in a shared Project. Project instructions are the Project's standing brief: they apply to each chat started inside it, whoever starts it. Memory follows an individual user and knowledge holds reference documents, so neither guarantees that colleagues in a shared Project get the same format without being told.

Why A is correct: Project instructions set how Claude behaves in every chat in the Project, including audience and structure. Because they belong to the shared Project, her colleagues get the same format without typing anything.

Why B is wrong: Putting it in the Project is the right instinct, but knowledge is reference material Claude draws on when relevant. A standing rule about audience and structure belongs in the instructions, which shape each chat.

Why C is wrong: Memory can carry her preferences between her own chats, which makes this tempting. It is tied to her account, so her two colleagues would not get the format.

Why D is wrong: This shares the wording, but it keeps the paste-every-time routine that a Project exists to remove, and relies on each colleague remembering to do it.

See more CCAO-F practice questions, answers explained.

Exam traps in Configuration and Knowledge Management

Answers that look right on this material and are not. Each one is a distractor from a different question in the CCAO-F bank for this domain.

Rewrite the Project instructions for the appeal format, then change them back once the appeal email has gone out
Why it is wrong: This does get the appeal format applied, which makes it feel thorough. It edits standing guidance for a single piece of work and risks the change being forgotten or reversed incorrectly, affecting next month's newsletter.
Strengthen the existing wording with capitals, such as 'BE EXTREMELY THOROUGH', so Claude treats it more seriously
Why it is wrong: Emphasis can feel like a way to make instructions stick. Asking for even more thoroughness pushes drafts to be longer, which is the opposite of the one-page brief the finance directors want, and it still says nothing about audience or format.
Add more tone words to the instructions, such as courteous, approachable, measured and reassuring.
Why it is wrong: More description feels like more guidance, so this is a natural first move. Each extra adjective is open to the same range of readings as 'warm' and 'professional', so the drafts would keep drifting between interpretations.

Examworthy is not affiliated with or endorsed by Anthropic. Original, blueprint-aligned practice material only.