最新のCCDV-F問題集で試験を準備する

Your Claude application has multi-step workflows where each step's output is needed only briefly before the agent moves on. The cumulative tool output is filling the context window with content that is no longer relevant.
How would you handle the accumulating tool output?

• A. Switch to a smaller Claude model that processes context more efficiently and treat any quality loss as a tradeoff for the cost reduction.
• B. Keep every tool output in the context indefinitely so the agent has the full record of every step it has executed during the workflow.
• C. Apply tool output pruning to remove tool outputs that are no longer needed by later steps in the workflow.
• D. Apply prompt caching to the accumulated tool outputs so the application does not re-pay for the older content on each subsequent step.

Your team is debating how to manage the prompts used in your Claude application. Some prompts are checked into the code repository, some live in a separate configuration file, and some are constructed inline at runtime. The result is inconsistent, and a recent prompt change went out without code review.
What steps would you take?

• A. Establish a single source of truth for prompts, version-control them alongside code, and require code review for prompt changes.
• B. Move all prompts out of version control to a separate spreadsheet that team members can edit freely as the application evolves over time.
• C. Move all prompts to inline runtime construction so the team can update them quickly through a streamlined process outside the standard code review workflow.
• D. Establish a single source of truth for prompts but keep change review optional, allowing developers to update prompts directly when changes are urgent.

You are setting up a CI/CD pipeline for a new Claude application. The pipeline needs to run automated checks on every pull request before code can be merged.
The CI/CD checks would include...

• A. Automated linting and security scanning, with Claude integration testing handled manually during pre- release verification by a designated reviewer.
• B. A full end-to-end production deployment on every pull request to catch all possible issues before any code is merged into the main branch.
• C. Automated tests of the Claude integration only, with linting handled separately during local development on each developer's machine.
• D. Automated tests of the Claude integration, linting, and any other standard quality gates the team applies to its other services.

Your team is choosing how to add a capability to a Claude application. You want to apply the appropriate option, whether built-in tool, custom tool, Skill, or MCP server, based on the use case.
You would choose the option that...

• A. Is the newest available option among built-in tools, custom tools, Skills, and MCP servers.
• B. Matches the use case's scope, reuse needs, and integration context.
• C. Is the easiest to build given the team's current development tools and workflows.
• D. Is the most familiar to the team based on prior experience with similar capabilities.

A Claude application that worked well in testing is now occasionally returning outputs that mention information not present in the input. The development team initially assumed the model was hallucinating, so they asked you to troubleshoot.
What would you do first?

• A. Examine production traces to identify whether the issue is hallucination by the model, context loss, prompt injection, or another failure mode before recommending a fix.
• B. Replace the current model with a larger one to reduce the chance of hallucination, on the grounds that larger models tend to hallucinate less in typical applications.
• C. Add a system prompt instruction telling the model not to invent information, on the grounds that prompt-level instructions are the fastest fix for hallucination concerns.
• D. Apply a retrieval-augmented generation pattern to ground the responses in source content before any further investigation of the production traces.