CCAO-F domain - 12% of the exam

Configuration and Knowledge Management

Configuration and Knowledge Management is 12% of the CCAO-F exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

29
Practice questions
4
Objectives
7
Easy
22
Medium

Where people go wrong

  • Mixing up project instructions and project knowledge

    The wrong answers put material in the wrong place. A 30-page style guide is pasted into the instructions, a standing format rule is filed as knowledge, or a role description is expected to supply fee figures Claude was never given. Instructions set how Claude behaves in every chat: audience, tone, format, boundaries. Knowledge holds long reference documents and the facts Claude draws on. A rule about structure goes in the instructions, and a policy document goes in the knowledge.

    See it in a sample question
  • Giving Claude more access than the task needs

    The wrong answers keep more within Claude's reach than the task needs: connecting Gmail and the calendar because the administrator enabled them, renaming files with client codes so two competing clients can share one Project, or sharing a Project that still holds named absence records with fewer managers. Each leaves the extra data available to every chat. The correct answers set the scope in the setup: connect only Google Drive, give each client a separate Project, and remove the records before sharing.

    See it in a sample question
  • Patching the symptom while the outdated source stays

    When answers quote an old mileage rate, an old entitlement or a formal tone, the wrong options leave the outdated file or instruction in place and work around it: tell Claude which version to prefer, ask Claude to forget the old figure, correct the tone in each chat, or ask staff to check. Two contradicting versions in knowledge give Claude two sources, and an outdated instruction applies again in every new chat. The correct answer removes or replaces the source itself.

    See it in a sample question
  • Choosing a stronger model to fix weak instructions

    A more capable model is offered when drafts break a boundary, come back generic, or swing in tone. The cause is in the instructions. They set a goal with no limit on refunds, describe an aspiration instead of the reader, or describe a tone in adjectives open to many readings, and a stronger model still has to guess what was meant. The correct answers rewrite the instructions: add a boundary and who handles exceptions, name the audience and format, or add agreed replies as tone examples.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleConfiguration and Knowledge Managementeasy

A communications officer at a local council maintains the Project the team uses to draft public notices. Its instructions say to write in a formal tone. The council has now adopted a 30-page plain-English style guide and a rule that every notice must give a contact phone line, but drafts still come out formal and without the contact line. What should the officer change? Select TWO.

  • APaste the full style guide into the project instructions so Claude reads every rule before each draft.
  • BKeep the instructions as they are and correct the tone in each chat, expecting Claude to learn from it.
  • CRewrite the tone line in the project instructions to ask for plain English and to include the contact line. Correct
  • DAsk each team member to type the new tone and contact rules at the start of every drafting request.
  • EAdd the style guide document to the project knowledge so Claude can draw on it as reference material. Correct
Update project instructions when required behaviour changes, and put long reference material such as a style guide in project knowledge. Project instructions set how Claude behaves in every chat, so an outdated tone rule there keeps producing outdated drafts until it is rewritten. A lengthy style guide is reference material, so it belongs in the knowledge, where Claude can draw on it without crowding the instructions.

Why A is wrong: This is tempting because it puts the new rules where Claude will see them. It is wrong because a long reference document belongs in the project knowledge; pasting 30 pages into the instructions buries the core behaviour rules and makes them hard to maintain.

Why B is wrong: This appeals because each correction does improve that one draft. It is wrong because the instructions still ask for a formal tone, so every new chat starts from the outdated rule again.

Why C is correct: This is correct because the instructions still ask for the old formal tone and say nothing about the contact line. Updating them changes how Claude behaves in every chat in the Project, for everyone on the team.

Why D is wrong: This seems workable because the rules would reach Claude. It is wrong because it leaves the outdated instruction in place and depends on every person remembering, which is the repetition a Project exists to remove.

Why E is correct: This is correct because the style guide is a long reference document. Holding it in the project knowledge lets Claude consult its detailed rules while the instructions stay short and focused on behaviour.

Free sampleConfiguration and Knowledge Managementmedium

A consultant at a management consultancy writes weekly status reports for two competing retail clients. The firm's confidentiality rules say one client's material must not inform work for another client. She currently uses a single Project called "Retail engagements" that holds both clients' files and one set of instructions. What should she do?

  • AKeep the shared Project and add an instruction to use a client's files only when that client is named.
  • BCreate a separate Project for each client, each holding that client's files and its own instructions. Correct
  • CTake the files out of the Project and upload the relevant client's documents into each chat instead.
  • DRename the files with client codes so Claude can tell the two clients' material apart in the shared Project.
When work for different clients must stay separate, give each client its own Project rather than relying on instructions or labels in a shared one. Everything in a Project's knowledge is available to every chat in that Project. Separating clients into their own Projects puts the boundary in how the work is set up rather than in an instruction, while each Project still supplies the stable context that recurring reports need.

Why A is wrong: An instruction feels like a safeguard, but it is not a control. Both clients' material stays available in the same Project, which is what the confidentiality rule forbids.

Why B is correct: Separate Projects keep each client's material apart, so one client's files are not available when drafting for the other. Each Project still gives her weekly reports the persistent context that recurring work needs.

Why C is wrong: This keeps the clients apart in each chat, which is why it appeals. It gives up the persistent setup a weekly task benefits from and means re-uploading the same files each week.

Why D is wrong: Clear labels help a reader, but both clients' files remain in one Project, so the separation the firm requires still depends on Claude choosing correctly each time.

Free sampleConfiguration and Knowledge Managementmedium

A customer service team lead at an online retailer set up a Project for drafting replies to complaints. Its instructions say only: 'Be friendly and solve the customer's problem.' Several drafts have offered refunds outside the returns window, which only the team lead may approve. She wants the Project setup itself to prevent this rather than relying on each agent to spot it. What should she change?

  • APaste the full returns policy into the instructions so Claude has every rule in front of it when drafting
  • BChange the instruction to 'Be very careful and accurate' so that Claude takes more care before offering anything
  • CAdd a boundary to the instructions: do not offer refunds outside the returns window or other exceptions, and flag those requests for the team lead Correct
  • DSwitch to the most capable model for these chats so that it reasons better about whether a refund is allowed
Project instructions should state clear boundaries on what Claude must not commit to, and what to do instead, when a decision belongs to a person. Instructions that state only a goal invite Claude to pursue it by any means, including offers the business does not allow. A boundary names the action that is off limits and the alternative behaviour, such as flagging the request for a named role. Putting this in the standing instructions makes every draft in the Project follow it without each agent having to remember.

Why A is wrong: Giving Claude the policy seems like the obvious fix. Long reference documents belong in project knowledge rather than instructions, and the policy alone does not tell Claude that approving exceptions is outside its role or what to do with such requests.

Why B is wrong: Asking for care sounds responsible. It is too vague to change behaviour, because it never says which commitments are off limits or who should handle them, so drafts can still offer refunds in a careful tone.

Why C is correct: The drafts go wrong because the instructions set a goal with no limit on what Claude may promise. An explicit boundary that names the off-limits commitment, plus what to do instead, tells Claude to hold back on out-of-window refunds and route those cases to the person who can approve them, while ordinary in-window refunds are still handled.

Why D is wrong: A stronger model can feel like a safer choice. The problem is a missing boundary, not weak reasoning, and the decision on exceptions belongs to the team lead whichever model drafts the reply.

Other domains in this exam

See also the CCAO-F cert hub, the study guide, and the cheat sheet.

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