Anthropic Claude Certified Developer CCDV-F New Questions

The supplied question selects D . If a downstream component requires an exact machine-readable structure, the expected structure must be communicated explicitly rather than left to Claude's discretion. The prompt should define required fields, types, nesting, permissible values where relevant, and instruct Claude not to emit surrounding prose.

Anthropic's consistency guidance states that developers should precisely specify the desired output format when format consistency matters. More importantly, current Claude APIs provide Structured Outputs for cases requiring guaranteed JSON Schema conformance; Anthropic explicitly recommends Structured Outputs instead of prompt-only techniques when valid schema-compliant JSON is mandatory.

Therefore, D is the strongest prompt choice among the listed alternatives. In a contemporary production implementation, the design can be strengthened further by supplying the schema through Claude's structured-output configuration and performing downstream semantic validation where business rules exceed JSON Schema.

A permits arbitrary formatting. B intentionally creates inconsistent representations. C assumes post-processing can reliably reconstruct missing or ambiguously formatted information, which is significantly less robust than specifying the contract up front.

Relevant Claude Developer topics: system prompts, JSON formatting, structured outputs, schema constraints, output contracts, validation, and downstream integration reliability .

===============

Option A is correct because sensitive-data protection must occur before prohibited information crosses the application's trust boundary. If account numbers, passwords, or other secrets must not be sent to Claude, asking Claude to “ignore” those values after transmission does not satisfy the requirement. The application must determine which data is permitted to leave its controlled environment and transform or reject prohibited content before constructing the Claude request.

This principle is consistent with Anthropic's defense-in-depth guidance. Anthropic recommends input screening, limiting Claude's access to sensitive information, and applying least privilege so the model receives only information necessary for the task.

B is fundamentally too late: the sensitive information has already been transmitted to the model context before the system instruction can influence behavior. C is worse because logging can create an additional store containing the sensitive information and only detects exposure after it occurs. D implements some boundary filtering but deliberately leaves coverage incomplete until production incidents reveal additional patterns.

Therefore, A requires the boundary and its permitted data flows to be defined first, then enforced comprehensively through filtering, redaction, tokenization, or rejection. Relevant Study Guide topics: application boundaries, data minimization, sensitive-data handling, filtering, redaction, least privilege, and privacy-preserving design.

===============

A is correct because the workflow is state-dependent, non-linear, and iterative . The source explicitly identifies the graph-based pattern as the intended architecture for this scenario. Each stage—fact extraction, eligibility evaluation, and decision-making—has its own completion criteria, and the process may need to move backward from eligibility evaluation to fact extraction when information is incomplete. A graph representation naturally models these conditional transitions and loops.

Anthropic's current orchestration guidance supports workflows containing branching, loops, filtering, staged execution, and state-dependent control flow , rather than forcing every task through one fixed sequence. Dynamic workflow orchestration can use explicit control logic so the next processing stage depends on current state and previous results.

B concerns progressive output delivery, not workflow-state transitions. C provides a generic agentic tool loop but does not explicitly model distinct states or transition criteria. D is unsuitable because it prohibits the required return path between extraction and eligibility evaluation.

Therefore, a graph-based architecture provides the necessary conditional routing, iteration, and stage-specific validation.

Relevant Claude Developer topics: Agent Patterns, graph workflows, state transitions, conditional branching, loops, stage-specific success criteria, and agent orchestration .

===============

Option B is the correct automation pattern. A CI pipeline must operate non-interactively, so Claude Code should be invoked in its programmatic/headless execution mode and given only the permissions required for the predefined workflow. Output can then be captured by the pipeline and supplied to subsequent build, testing, reporting, or deployment stages.

Claude Code's configuration system supports explicit permission rules in JSON settings. Anthropic documents that settings.json controls, among other behavior, what Claude Code can execute without asking. For example, permissions.allow can authorize specific commands while permissions.deny prevents sensitive operations. Project-level .claude/settings.json can be version-controlled so CI behavior is reproducible across runners.

This is substantially safer than C, which disables confirmation behavior globally and expands the blast radius beyond the CI workload. D defeats automation because a human must remain present. A is unnecessary because Claude Code is explicitly configurable for automation scenarios.

The principle is least-privilege non-interactive configuration: authorize only the commands and resources required by the pipeline and capture machine-readable output for downstream processing. Relevant Claude Developer topics are Claude Code automation, configuration management, permissions, CI/CD integration, headless execution, and reproducible project settings.