CCAR-F Context and Reliability Practice Question
A multi-agent system has a coordinator that delegates research subtasks to worker agents. Workers often return verbose, partially relevant summaries, and the coordinator loses track of which findings map to which subtask. Which change best improves the coordinator's ability to assemble a coherent final answer?
⚠ Common exam trap
The trap here is adding more context or output space to the coordinator when the actual defect is the absence of structure and identifiers in worker outputs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Define a strict output schema for workers, such as a JSON object with fields for subtask identifier, findings, and confidence, and validate it before the coordinator consumes it.
The coordinator's difficulty is traceability: verbose worker summaries carry no explicit link to the subtask that produced them. Imposing a schema with subtask identifiers, findings, and confidence makes each worker's contribution self-describing and validates it before synthesis, so the coordinator can assemble and reconcile results deterministically rather than inferring associations from prose.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Have each worker call the other workers directly to reconcile their findings before returning to the coordinator.
Why it's wrong here
Peer-to-peer reconciliation creates a mesh of dependencies that is hard to observe, debug, and bound in cost, and it undermines the coordinator's role as the single point of synthesis. Workers may also lack the global view needed to resolve conflicts. The problem is output structure, not missing cross-talk between workers.
- ✗
Instruct the coordinator to re-read the entire conversation history before composing the final answer.
Why it's wrong here
Re-reading history does not make the worker outputs any more structured; the coordinator still faces verbose, unattributed summaries. The mapping problem persists because the association between findings and subtasks was never encoded. This adds tokens and latency without adding the information the coordinator actually lacks.
- ✗
Increase the coordinator's max_tokens so it has more room to write the final answer.
Why it's wrong here
A larger output budget lets the coordinator produce a longer response but does nothing to clarify which findings came from which subtask. Verbose, unattributed inputs remain ambiguous regardless of output length. The bottleneck is input structure and traceability, not the coordinator's writing capacity.
- ✓
Define a strict output schema for workers, such as a JSON object with fields for subtask identifier, findings, and confidence, and validate it before the coordinator consumes it.
Why this is correct
A strict schema forces each worker to declare which subtask its findings belong to and how confident it is, giving the coordinator structured, machine-checkable inputs to assemble. Validation catches malformed or missing fields before they corrupt the final synthesis. This directly addresses the mapping and verbosity problems described.
About these practice questions
This CCAR-F question is part of Courseiva's 271-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-F exam.