CCAR-F Agentic Architecture and Orchestration Practice Question
An agent is designed to summarize long documents by first splitting them into chunks and then calling a 'summarize_chunk' tool for each part. What is the most efficient orchestration strategy to minimize the total time taken for this task?
⚠ Common exam trap
Candidates frequently choose sequential processing because it seems safer or easier to debug, failing to recognize that independent tool calls should always be parallelized to optimize latency and throughput.
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
✓
Asynchronous parallel tool calls managed by the orchestrator for all chunks simultaneously.
In workflows where tasks are independent, such as summarizing different parts of a document, sequential execution is unnecessarily slow. Orchestrating these calls in parallel allows the system to utilize the full throughput of the API, significantly reducing the 'wall-clock' time required to complete the overall job.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Sequential execution where each chunk is processed only after the previous one finishes.
Why it's wrong here
Sequential execution is the least efficient method for independent tasks. It forces the orchestrator to wait for a full round-trip to the API and the tool for every single chunk, leading to a total processing time that scales linearly with the number of chunks, which is suboptimal for large documents.
- ✗
Instructing Claude to summarize all chunks in a single, very long 'text' block without tools.
Why it's wrong here
While this might seem faster, it often leads to lower quality summaries and 'lost in the middle' issues where Claude ignores information from the center of a very long prompt. Using tools for chunked processing provides better control and higher quality results than attempting to process everything in one go.
- ✓
Asynchronous parallel tool calls managed by the orchestrator for all chunks simultaneously.
Why this is correct
By triggering all 'summarize_chunk' calls at once, the orchestrator can process them in parallel. This leverages the concurrency capabilities of the environment and the API, ensuring that the total time is limited by the single longest-running chunk rather than the sum of all chunks.
- ✗
Recursive orchestration where the agent calls itself to summarize each new chunk.
Why it's wrong here
Recursive agentic loops add significant overhead and complexity without providing a clear performance benefit for this specific task. It would increase the number of tokens used and the risk of the agent losing its place in the overall workflow compared to a simple parallel orchestration pattern.
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.