CCAO-F practice questions: Configuration and knowledge management.

Your team runs the same weekly task with the same standing instructions and reference files. What setup avoids re-explaining every time?

• A saved prompt template that each person pastes as the first message every week
• A Project with the standing instructions and reference files attached
• A single long-running conversation that the whole team continues week after week
• A shared document of past outputs that Claude is asked to imitate each week

What belongs in a Project's instructions?

• Every document the team has produced on the topic, so Claude has the fullest possible picture
• A log of past conversations that went well, so Claude can reproduce the pattern
• Standing context: who the audience is, tone, formats, and rules that apply to every conversation
• The specific request for this week, updated each time the task changes

Your Project's knowledge files are out of date and answers reflect old policy. Fix?

• Add a line to the instructions telling Claude to prefer the most recent file when they conflict
• Replace the outdated files and tell the team that the source of truth has changed
• Add the new policy document alongside the old ones so Claude can see both versions
• Start a new Project from scratch and move the team over once it is set up

What is a good way to keep a team's prompts consistent?

• A weekly review where the team compares the prompts each person wrote that week
• A rule that everyone uses the same model so the outputs come out in a similar style
• Shared templates or skills with the agreed structure, stored where the team can find them
• One designated person who writes every prompt and sends it to the rest of the team

Which is a reason to split work into several Projects?

• The knowledge files are large and splitting them spreads the storage across Projects
• Projects perform better when each one holds fewer than ten conversations
• Each team member should own a Project so their conversations stay private
• Different audiences, tones, or confidentiality levels that should not mix

How much should a knowledge file contain?

• A single summary page, since longer files make answers slower and less focused
• What conversations in that Project regularly need, kept current
• Only finalized documents; drafts and working notes should stay out of the Project
• Everything the team has written on the topic, so nothing relevant is left out

What should you record when a prompt template works well?

• The name of the person who wrote it, so colleagues know who to ask about it
• The number of times it has been used, so the team can see which templates matter
• The template, the inputs it expects, and an example output, so others can reuse it
• The model version and the date, so the team knows when it may need to be re-tested