CCAO-F - Troubleshooting and Optimization (10% of the exam) - Section 7.2

Adjust approach based on feedback and results.

Using feedback from reviewers, recipients and results to change the approach, such as revising instructions, adding examples or changing the feature used, rather than repeating what did not work.

reviewer feedbackrevising instructionslearning from results

Practice question for this objective

Free sampleTroubleshooting and Optimizationeasy

A consultant at a management consultancy writes a summary after each weekly client workshop. Over the past month the engagement partner returned every summary with the same corrections: decisions first, an owner and date for each action, and no more than one page. Last week's summary was approved first time. Workshops continue weekly for three more months. What should the consultant do to keep this standard?

  • AStart each week's summary in a new chat with the original prompt and repeat the corrections as needed
  • BSet up a Project with the partner's requirements as instructions and the approved summary as an example Correct
  • CKeep drafting every future summary in last week's chat so Claude can see all the earlier corrections
  • DPaste the whole month of drafts and the partner's comments into each new week's chat before starting
Once feedback has produced an approved approach for recurring work, capture it in a Project's instructions and examples so later work starts from it. Feedback is only useful if the lesson is kept. For recurring work, a Project holds persistent instructions and reference material that apply to every new chat, so the partner's requirements and an approved example shape each summary. This avoids repeating failed rounds, overlong chats and repeated pasting of mixed old material.

Why A is wrong: This feels like a clean start, but it throws away what the month of feedback established and repeats the approach that kept failing review, costing extra rounds every week.

Why B is correct: The work recurs weekly, so capturing what the feedback taught in Project instructions, with the approved summary as a model, means every new chat starts from the agreed standard instead of relearning it.

Why C is wrong: Staying in one chat keeps the history visible, but over three months the conversation grows very long and earlier detail can blur, so the agreed requirements are likely to drift.

Why D is wrong: Pasting background each week preserves the feedback, but it mixes rejected drafts with the final requirements and must be repeated every time, which a Project handles once and cleanly.

See more CCAO-F practice questions, answers explained.

Exam traps in Troubleshooting and Optimization

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.

  • Ask Claude to make the bulletin more engaging while keeping the current order and length of items

    Why it is wrong: More engaging writing sounds like an improvement, but it keeps the valued item at the end, where most readers never reach it. The results point to a structural change, not a stylistic one.

  • Ask Claude to confirm that each new advert is free of bias before the officer posts it

    Why it is wrong: A bias check sounds responsible, which makes this tempting. But Claude's own confirmation is not independent evidence, and the same drafting that produced the flagged phrases is now being asked to judge them.

  • Set up a Project holding the categorisation rules so each evening's chat starts with them ready

    Why it is wrong: A Project is the right tool for recurring work, so this is tempting. It would save setup time, but the analyst would still copy and paste every night, which does not meet the need to run unattended between two systems.

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