CCAR-F Claude Certified Architect Foundations

Option A matches the standard coordinator-managed subagent model. The coordinator invokes the web-search agent, receives its final result, selects the useful URLs or source records, and then supplies them explicitly when invoking the document-analysis agent. This keeps task ownership, provenance, and execution order visible to the coordinator.

The Claude Agent SDK subagent documentation states that a subagent begins with a fresh context window and does not inherit the parent’s conversation history or previous tool results. The information passed through the Agent tool’s prompt is the primary parent-to-subagent context channel. Consequently, the analysis prompt must include the source URLs, documents, retrieval notes, and any questions the analyzer must answer.

Option B requires nested delegation that is neither stated nor necessary and reduces centralized observability. Options C and D describe valid custom architectures only if the application has deliberately implemented a queue or shared memory system; neither is automatic Agent SDK behavior. Coordinator-mediated handoff is therefore the expected approach. For reliability, the handoff should use structured source records rather than an informal prose statement, ensuring that the analyzer receives identifiers, provenance, relevant excerpts, and analysis objectives.

Option C matches the distinction between reasoning about delegation and executing it. Defining subagents makes their descriptions available for selection, but the coordinator must still invoke the SDK’s subagent-spawning tool. Current Claude Agent SDK documentation calls this the Agent tool; Task was its earlier name and remains relevant to older SDK configurations. Anthropic’s Subagents in the SDK documentation instructs developers to include Agent in allowedTools so subagent invocations are approved automatically. Without that permission, an invocation can fall through to a permission callback or be denied under a non-interactive permission mode. Option A is unlikely because the configured subagent descriptions already tell Claude when each agent should be selected, although explicit prompting can improve invocation reliability. Option B misstates context isolation: context must be included in the spawning prompt, but that issue occurs after an invocation is attempted and does not explain the absence of all subagent executions. Option D would normally produce truncation evidence or incomplete output rather than consistent verbal promises with no tool call. The configuration should therefore permit Agent, explicitly request delegation where necessary, and log subagent invocation events.