Option C applies the appropriate context-management technique. The issue is not simply whether the older conversation can physically fit into the context window; it is that stale details remain prominent enough to interfere with the model's current task. Effective context engineering optimizes signal quality, not merely maximum token retention.
Anthropic's context-editing documentation describes compaction as summarizing accumulated history and replacing the full history with a structured summary when context becomes large. This preserves important task state while substantially reducing low-value detail that can distract later reasoning.
A retains precisely the stale material producing the problem and therefore does not address context drift. B destroys all useful continuity between turns, including valid goals, decisions, and intermediate state. D is similarly excessive because limiting Claude to only the latest turn discards information that may still be required.
Compaction provides the correct middle ground: retain durable conclusions, current objectives, unresolved issues, and other high-signal state while compressing obsolete conversational detail. Relevant Study Guide topics: context engineering, compaction, conversation history, long-running agents, stale context, context drift, and high-signal state preservation.

Option C follows the governing constraint in the scenario: data residency is an enterprise requirement, whereas minimizing infrastructure management is a preference. A deployment architecture cannot knowingly violate a mandatory compliance boundary merely to accelerate delivery. The question should therefore be interpreted under its stated assumption that the described BYOC environment satisfies the enterprise residency policy.
Anthropic's current Managed Agents documentation distinguishes Anthropic-managed cloud environments from self-hosted sandboxes running on infrastructure controlled by the customer. Self-hosting keeps tool execution, files, and network egress within customer infrastructure, although Anthropic documents that model- facing tool inputs and outputs can still pass through its control plane; therefore, actual regulatory approval must be based on the organization's precise data-flow requirements.
B and D explicitly defer or violate the existing policy. A unnecessarily introduces a planned migration away from the residency-compliant architecture without establishing that such a migration would be permissible.
Accordingly, C is the intended certification answer. Relevant Study Guide topics: deployment topology, data residency, self-hosting, compliance constraints, infrastructure ownership, security boundaries, and architecture tradeoffs.

The question presents a trust-boundary failure: model-generated tool arguments are being accepted without sufficient validation before an external operation executes. A tool call should therefore be treated like input arriving at any typed application interface-the application must ensure that the tool name and arguments satisfy the declared contract before dispatch.
Anthropic describes tool use as a contract in which the application defines the tool's schema and Claude returns structured tool_use input. Current Claude functionality also supports strict: true, which guarantees schema-compliant tool inputs through constrained generation and specifically addresses invented parameters, incompatible types, and missing required fields. For applications not using strict tool use, explicit application- side validation and a controlled error path remain essential.
B knowingly executes invalid input. C relies on uncontrolled repetition rather than deterministic validation and bounded recovery. D eliminates a useful capability instead of correcting its execution boundary.
Therefore, A provides the correct defensive design. Relevant Study Guide topics: tool calling, tool_use, input_schema, strict tool use, schema validation, defensive execution, error handling, and secure tool dispatch.

D is directly aligned with Claude Code's configuration model. The supplied exam source marks D . Anthropic documents settings.json as the official mechanism for configuring Claude Code through hierarchical scopes.
Shared project configuration is stored in .claude/settings.json , which is intended to be checked into source control and shared with the team.
Project settings provide consistent repository-level behavior while still participating in Claude Code's configuration precedence. They can configure permissions, environment variables, tool behavior, and other supported project policies. Claude Code additionally distinguishes shared project settings from .claude
/settings.local.json, which is intentionally excluded from source control and is suitable for developer-specific experimentation or machine-local overrides.
A spreadsheet provides documentation but no executable configuration enforcement. B allows every developer's configuration to diverge and is appropriate only for values that genuinely belong to the local environment. C requires manual repetition and cannot reliably establish repository-wide policy.
Therefore, shared project settings.json is the appropriate configuration-as-code mechanism.
Relevant Claude Developer topics: Confia Management, Claude Code configuration, settings scopes, project settings, permissions, environment configuration, team consistency, and source-controlled configuration .

Option A treats a Claude application as production software subject to the same disciplined engineering controls as other services while adding tests for its model integration. CI should provide repeatable feedback before merge, including deterministic unit/integration tests, linting, type or static checks where applicable, security checks, and organization-specific quality gates.
Claude-specific behavior should also be tested systematically rather than reserved for manual release verification. Anthropic's evaluation guidance recommends task-specific test cases reflecting realistic inputs and edge cases, measurable success criteria, and automation whenever practical. Claude Code documentation also explicitly identifies CI automation, including GitHub Actions and GitLab CI/CD, as supported development workflows.
B is excessive because every pull request should not directly deploy to production merely to obtain end-to-end coverage; testing environments and staged deployment exist for that purpose. C makes linting dependent on individual developer discipline rather than a shared merge gate. D delays Claude integration verification until pre-release and makes a repeatable automated check manual.
Therefore, A provides comprehensive and consistent pull-request validation. Relevant Study Guide topics: CI
/CD, automated testing, integration testing, linting, evaluations, regression prevention, and quality gates.