C addresses the failures at the correct architectural layer: orchestration and supervision . The supplied exam item identifies C as correct. The primary agent is responsible not merely for forwarding subordinate output but for governing delegation, resource usage, stage boundaries, and result quality.
Anthropic's current guidance recommends explicit control over subagent use because excessive delegation multiplies latency and cost. Its documentation specifically supports deterministic limits on subagent spawning and SDK budget controls such as max_budget_usd. Tool contracts can also use defined input schemas and strict validation so malformed data cannot silently propagate between processing stages.
Explicit handoff contracts are equally important. Retrieval should provide an agreed structure to analysis; analysis should provide validated findings to report generation; and the manager should reject, retry, reconcile, or escalate outputs that violate those contracts.
A improves observability but mainly detects problems after they occur. B destroys context isolation and can create additional coupling. D abandons useful specialization instead of correcting deficient supervision.
Relevant Claude Developer topics: Agent Patterns, orchestrator/subagent architecture, delegation, budgets, handoff contracts, schema validation, output reconciliation, and multi-agent governance .

The supplied Claude Certified Developer Foundations source marks C . Model selection is a multidimensional engineering decision. There is no universally correct Claude model independent of workload requirements; the application must satisfy the required capability or quality while remaining within acceptable latency and cost envelopes.
Anthropic's official model-selection guidance explicitly identifies capabilities, speed, and cost as core considerations and recommends testing models against workload-specific benchmarks rather than selecting them from a single metric. The guidance further recommends evaluating actual prompts and data, comparing response accuracy, quality, and edge-case behavior, and then weighing the resulting performance and cost tradeoffs.
Options A, B, and D each establish one or two dimensions as primary and effectively defer the remainder.
That can lead to a technically unsuitable model-for example, a cheap model that fails the quality threshold or a high-quality model whose latency makes the user experience unacceptable.
The correct method is to define minimum acceptable thresholds across all relevant dimensions and benchmark candidate models against the actual workload.
Relevant Claude Developer topics: Claude App Design, model selection, capability, quality, latency, cost, benchmarking, workload evaluation, tradeoff analysis, and production optimization .

Option D reflects the correct architecture-selection principle: extension mechanisms should be selected according to what the capability must accomplish rather than familiarity, novelty, or implementation convenience. Anthropic explicitly distinguishes Claude extension mechanisms by purpose. Built-in tools cover common capabilities already supported by the platform. Custom tools expose application-specific callable operations through defined schemas. Skills package reusable knowledge, instructions, and workflows.
MCP connects Claude to external systems, APIs, databases, and services through a standardized protocol.
The decision therefore depends on scope and integration boundaries. A reusable procedural workflow may belong in a Skill; access to an external enterprise system may warrant MCP; a narrowly application-specific operation can be a custom tool; and a built-in tool should generally be preferred when it already satisfies the requirement.
A makes prior team experience the architectural criterion rather than requirements. B assumes newer technology is inherently better. C optimizes implementation convenience without considering maintainability, interoperability, or reuse.
Therefore, D is the appropriate selection rule. Relevant Study Guide topics: built-in tools, custom tools, Skills, MCP, extension architecture, reuse boundaries, and capability selection.

Option C provides the required configuration-management discipline. Development, staging, and production may legitimately use different models, prompts, plugins, permissions, or service endpoints, but those differences must be explicit, reproducible, and auditable rather than scattered across undocumented mechanisms.
Claude Code documentation follows the same configuration-as-code principle. Project-level configuration can live in source-controlled files such as .claude/settings.json, while project instructions are maintained in repository-level CLAUDE.md. Anthropic specifically distinguishes shared project settings from local developer configuration.
A introduces uncontrolled model changes and regression risk. B hides configuration in application logic and makes environment differences harder to review. D ignores the fact that environments often require deliberate differences-for example, production credentials or pinned release versions.
The correct strategy is therefore to define configuration centrally, pin compatibility-sensitive dependencies, record environment-specific overrides, review modifications through source control, and retain rollback history. Relevant Study Guide topics: configuration management, environment isolation, model versioning, prompt versioning, dependency management, reproducibility, and controlled deployment.

The architecture is a manager/supervisor-or orchestrator/subagent-pattern with isolated subagent context.
The defining characteristics are a coordinating top-level agent, specialized subordinate agents, delegated responsibilities, and distinct tool/context boundaries. The supervisor determines which specialist should act, sequences work where necessary, and integrates the specialists' outputs into the final result.
Anthropic's published multi-agent research architecture uses this same structural principle. Its Research system employs an orchestrator-worker pattern in which a lead agent analyzes the task, creates specialized subagents, delegates separate research responsibilities, and consolidates their findings. Anthropic emphasizes that good delegation requires each subagent to receive a specific objective, task boundaries, expected output, and appropriate tools.
The question additionally specifies that each travel specialist has its own conversation history and tool list.
That eliminates B because context is explicitly not shared globally. C would involve fixed sequential processing rather than supervisor-directed specialization. D describes retrieval augmentation, not autonomous subordinate agents.
Therefore, A precisely matches both the hierarchy and context-isolation characteristics described.
The supplied examination set also marks A as the intended answer. Relevant topics: Agent Patterns, manager
/supervisor architecture, orchestrator-worker systems, subagents, delegation, specialized tools, and context isolation.