Anthropic CCA-F Exam Actual Questions
Claude Certified Architect - Foundations (Page 2 )

Updated On: 1-Aug-2026

After the web search agent and document analysis agent complete their tasks, the coordinator invokes the synthesis agent. However, the synthesis agent responds that it cannot complete the task because no research findings were provided.
What is the most likely cause of this issue?

  1. The synthesis agent needs tools that can fetch results directly from the other agents' conversation histories.
  2. The synthesis agent's context window is not large enough to hold the combined outputs from both previous agents.
  3. The subagents need to share a single API connection to enable automatic context sharing between invocations.
  4. The coordinator did not include the outputs from the previous agents in the synthesis agent's prompt.

Answer(s): D

Explanation:

A: The synthesis agent needs tools that can fetch results directly from the other agents' conversation histories. Incorrect.
Agents do not require direct access to each other’s histories. Proper orchestration passes outputs explicitly via prompts.
B: The synthesis agent's context window is not large enough to hold the combined outputs from both previous agents. Incorrect.
If this were the issue, the agent would receive truncated data, not no data at all. The error indicates missing inputs entirely.
C: The subagents need to share a single API connection to enable automatic context sharing between invocations. Incorrect.
Agent communication does not depend on shared API connections. Context must be explicitly passed by the coordinator.
D: The coordinator did not include the outputs from the previous agents in the synthesis agent's prompt. Correct.
The synthesis agent can only act on the information provided in its prompt. If prior outputs are not passed, it will report missing research findings.



When researching "renewable energy adoption," the web search agent returns recent statistics (2024: 35% adoption) while the document analysis agent extracts data from internal reports (2022: 18% adoption). The synthesis agent incorrectly flags these as contradictory sources rather than recognizing the data shows growth over time.
What change would best enable the synthesis agent to correctly interpret such temporal differences?

  1. Require subagents to include publication or data collection dates in their structured outputs.
  2. Instruct the synthesis agent to always treat the most recent data as authoritative and place older findings in a separate historical appendix.
  3. Add a conflict resolution agent that automatically discards older data when newer data exists for the same metric.
  4. Configure the web search agent to only return results from the past 6 months

Answer(s): A

Explanation:

A: Require subagents to include publication or data collection dates in their structured outputs. Correct.
Providing timestamps allows the synthesis agent to understand that the figures refer to different points in time, enabling it to interpret the data as a trend (growth) rather than a contradiction.
B: Instruct the synthesis agent to always treat the most recent data as authoritative and place older findings in a separate historical appendix. Incorrect.
This approach hides useful context and does not help the agent understand relationships between data points over time.
C: Add a conflict resolution agent that automatically discards older data when newer data exists for the same metric. Incorrect.
Discarding older data removes valuable historical insight and prevents trend analysis.
D: Configure the web search agent to only return results from the past 6 months. Incorrect.
Limiting recency reduces context and does not address the core issue of interpreting time-based differences.



Users report that final reports sometimes lack depth on specific subtopics. Investigation shows that the document analysis agent frequently identifies gaps—for instance, noting "the retrieved sources discuss API authentication but lack details on token refresh patterns"—but under the current strict pipeline, this insight isn't actionable since search has already completed.
What is the most effective architectural change?

  1. Have the analysis agent report specific gaps to the coordinator, which triggers targeted searches and re-invokes analysis until sufficient.
  2. Add a research planning agent before the search phase that decomposes topics into specific sub-questions.
  3. Have the synthesis agent attach confidence scores to each section and flag areas with insufficient coverage for manual review.
  4. Have the coordinator review analysis output for gap indicators and re-invoke search with gap-informed queries when gaps are detected.

Answer(s): A

Explanation:

A: Have the analysis agent report specific gaps to the coordinator, which triggers targeted searches and re-invokes analysis until sufficient.
This introduces a dynamic, agentic loop (or reflection pattern) into the workflow. Instead of a rigid, linear pipeline where steps cannot be retraced, the system can now adapt based on what it discovers.
The Analysis Agent is the Expert: The document analysis agent is the one actively reading the text and identifying exactly what is missing (e.g., "missing token refresh patterns").
The Coordinator Manages the Flow: By reporting these specific gaps back to the coordinator, the coordinator can intelligently route the workflow back to the search agent with a highly targeted query, then pass the new findings back to the analysis agent to close the loop.



Your multi-agent research pipeline crashed after processing 12 of 28 documents. The web search agent had identified relevant sources, the document analyzer had partially complete and the synthesizer had begun pattern identification. You need to resume processing without repeating work or losing fidelity of prior findings.
What state management approach be Information fidelity with context efficiency when restoring agent state?

  1. Have each agent persist a structured export to a known location. On resume, the coordinator loads the manifest and injects relevant state into agent prompts.
  2. Persist the coordinator's conversation log containing all task delegations and responses, providing this to agents when resuming.
  3. Have each agent maintain its own persistent state file and reload it independently at the start of each session.
  4. Index all agent outputs in a shared vector store.
    When resuming each agent queries the store using semantic search to retrieve relevant prior findings.

Answer(s): A

Explanation:

A: Have each agent persist a structured export to a known location. On resume, the coordinator loads the manifest and injects relevant state into agent prompts. Correct.
This provides high information fidelity (structured, complete outputs) while maintaining context efficiency (only relevant pieces are re-injected into prompts). The coordinator remains in control of what each agent needs, avoiding unnecessary bloat and duplication.
B: Persist the coordinator's conversation log containing all task delegations and responses, providing this to agents when resuming. Incorrect.
Conversation logs are often verbose and unstructured, leading to context overload and inefficient prompt usage without guaranteed clarity.
C: Have each agent maintain its own persistent state file and reload it independently at the start of each session. Incorrect.
This decentralizes control and can lead to inconsistencies and coordination issues , especially when agents need shared or aligned context.
D: Index all agent outputs in a shared vector store.
When resuming each agent queries the store using semantic search to retrieve relevant prior findings. Incorrect.
Vector stores are useful for retrieval, but they introduce probabilistic recall and may miss or distort critical structured state, reducing fidelity during recovery.



The synthesis agent completes its initial pass but flags that three key research questions remain unanswered because the web search and document analysis agents didn't find relevant information on those specific subtopics. The coordinator currently proceeds directly to report generation, producing reports with incomplete coverage.
What change would most effectively improve research completeness?

  1. Have the coordinator evaluate synthesis output for gaps, then re-delegate to web search and document analysis with targeted queries before Invoking synthesis again.
  2. Increase the initial breadth of queries sent to web search and document analysis to reduce the probability of missing relevant information.
  3. Have the report generation agent note which research questions couldn't be answered, so users understand the limitations of the final output.
  4. Give the synthesis agent direct access to web search tools so it can autonomously fill knowledge gaps without returning control to the coordinator.

Answer(s): A

Explanation:

A: Have the coordinator evaluate synthesis output for gaps, then re-delegate to web search and document analysis with targeted queries before invoking synthesis again. Correct.
This introduces an iterative feedback loop , where identified gaps are actively addressed. The coordinator maintains control and ensures completeness before final report generation.
B: Increase the initial breadth of queries sent to web search and document analysis to reduce the probability of missing relevant information. Incorrect.
Broader queries may help coverage but are inefficient and still won’t guarantee that specific gaps discovered later are filled.
C: Have the report generation agent note which research questions couldn't be answered, so users understand the limitations of the final output. Incorrect.
This improves transparency but does not solve the completeness problem .
D: Give the synthesis agent direct access to web search tools so it can autonomously fill knowledge gaps without returning control to the coordinator. Incorrect.
This breaks separation of concerns and reduces system control. The coordinator should manage task delegation, not the synthesis agent.



When analyzing complex legal cases that cite multiple precedents, the document analysis subagent processes each sequentially. A landmark case citing 12 precedents takes over 3 minutes to analyze completely.
What's the most effective way to reduce this latency while preserving the coordinator's ability to monitor and debug the system?

  1. Enable the document analysis subagent to spawn its own specialized subagents dynamically when it encounters cases with many citations
  2. Implement a message queue where precedent analysis tasks are processed asynchronously by a pool of worker agents
  3. Create a recursive agent hierarchy where analysis agents subdivide work among child agents until reading single-precedent granularity
  4. Have the coordinator spawn parallel document analysis subagents, each handling a subset of precedents, then aggregate results before synthesis

Answer(s): D

Explanation:

A: Enable the document analysis subagent to spawn its own specialized subagents dynamically when it encounters cases with many citations. Incorrect.
This decentralizes orchestration and makes the system harder to monitor and debug. The coordinator loses visibility into dynamically spawned agents.
B: Implement a message queue where precedent analysis tasks are processed asynchronously by a pool of worker agents. Incorrect.
While this improves scalability, it introduces infrastructure complexity and reduces transparency for debugging at the coordinator level.
C: Create a recursive agent hierarchy where analysis agents subdivide work among child agents until reaching single-precedent granularity. Incorrect.
This further complicates the architecture and makes tracing execution paths difficult, reducing observability and control.
D: Have the coordinator spawn parallel document analysis subagents, each handling a subset of precedents, then aggregate results before synthesis. Correct.
This enables parallel processing to reduce latency while keeping orchestration centralized. The coordinator retains full visibility, making monitoring and debugging easier.



Introduction monitoring shows the research phase takes longer than expected. Analysis reveals the coordinator invokes the web search subagent, waits for its response, then invokes the document analysis subagent and waits again. These tasks are independent - neither requires the other's output. How should you modify the system to run these subagents concurrently?

  1. Switch both subagents to use a Haiku tier model instead of to reduce their individual execution time.
  2. Create an async orchestration layer outside the agent that spawns parallel threads, each running a separate coordinator subagent pair, then aggregates results.
  3. Add detailed instructions to the coordinator's system prompt explaining the performance benefits of parallel execution and requesting it invoke both subagents at the same
  4. Structure the coordinator to emit both Task tool calls (for web search and document analysis) in a single response message rather than across separate conversation turns.

Answer(s): D

Explanation:

A: Switch both subagents to use a Haiku tier model instead to reduce their individual execution time. Incorrect.
This may reduce latency per task, but it does not address the core issue of sequential execution vs. parallelism.
B: Create an async orchestration layer outside the agent that spawns parallel threads, each running a separate coordinator subagent pair, then aggregates results. Incorrect.
This overcomplicates the architecture and duplicates coordinators unnecessarily instead of fixing concurrency within the existing flow.
C: Add detailed instructions to the coordinator's system prompt explaining the performance benefits of parallel execution and requesting it invoke both subagents at the same time. Incorrect.
Instructions alone are not reliable for enforcing concurrency. Execution behavior depends on how tool calls are structured, not just prompt wording.
D: Structure the coordinator to emit both Task tool calls (for web search and document analysis) in a single response message rather than across separate conversation turns. Correct.
Issuing both tool calls in one response enables true parallel execution , since the system can run them concurrently instead of waiting for one to finish before starting the other.



Production reviews reveal inconsistent handling of uncertainty in final reports. Sometimes conflicting subagent findings are synthesized into a single confident statement (losing other times reports over hedge with excessive qualifications (becoming unhelpful).
When the web search agent returns "Industry analysts estimate $50B market size (methodolo the document analysis agent returns "peer-reviewed study estimates $358 (1578, 95% CI)," the coordinator either picks one arbitrarily or produces vague statements like "the ma 6358-6508 depending on factors." What systematic approach best addresses this?

  1. Configure subagents to only report findings meeting a high confidence threshold, filtering uncertain information before it reaches the coordinator.
  2. Add a verification subagent that cross-references findings across sources, only passing claims to synthesis that are corroborated by at least two independent sources.
  3. Instruct the synthesis agent to structure reports with explicit sections distinguishing well-established findings from contested ones, preserving original source characterization and methodological context.
  4. Implement a confidence calibration layer that normalizes subagent uncertainty expressions to standardized probability scores (0.0-1.0), then weight-average findings by their calculated reliability scores to produce a statistically grounded synthesis.

Answer(s): C

Explanation:

A: Configure subagents to only report findings meeting a high confidence threshold, filtering uncertain information before it reaches the coordinator. Incorrect.
This suppresses potentially valuable but uncertain insights and introduces bias by hiding ambiguity rather than managing it.
B: Add a verification subagent that cross-references findings across sources, only passing claims to synthesis that are corroborated by at least two independent sources. Incorrect.
While useful for validation, this approach still filters out uncertainty instead of representing it, and may discard novel or emerging insights.
C: Instruct the synthesis agent to structure reports with explicit sections distinguishing well-established findings from contested ones, preserving original source characterization and methodological context. Correct.
This directly addresses inconsistent handling of uncertainty by making it explicit and structured , allowing users to understand both consensus and disagreement without losing context.
D: Implement a confidence calibration layer that normalizes subagent uncertainty expressions to standardized probability scores (0.0–1.0), then weight-average findings by their calculated reliability scores to produce a statistically grounded synthesis. Incorrect.
This introduces artificial precision and may oversimplify complex, qualitative uncertainty, potentially misleading users.



Viewing page 2 of 20
Viewing questions 9 - 16 out of 149 questions


Post your Comments and Discuss Anthropic CCA-F exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!