Pass exam with CCAR-F Top Exam Collection for sure one-shot

You are building developer productivity tools using the Claude Agent SDK. The agent helps engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate code, and automate repetitive tasks. It uses the built-in tools (Read, Write, Bash, Grep, Glob) and integrates with Model Context Protocol (MCP) servers.
Your agent has spent 25 minutes exploring a game engine's rendering subsystem -reading shader code, buffer management, and frame synchronization logic. An engineer now asks it to understand how the physics engine integrates with rendering for collision debug overlays. You notice recent responses reference "typical rendering patterns" rather than the specific VulkanPipeline and FrameGraph classes it discovered earlier.
What's the most effective approach?

• A. Continue in the current context with more targeted prompts referencing the specific classes by name.
• B. Use /clear to reset context completely, then start fresh with physics exploration using file paths from the project's CLAUDE.md.
• C. Summarize key rendering findings, then spawn a sub-agent for physics exploration with that summary in its initial context.
• D. Spawn a sub-agent to explore physics independently, then manually synthesize its findings with the rendering knowledge accumulated in the main conversation.

Your automated reviewer uses a single prompt covering security issues, API design, and business-logic correctness. Your evaluation suite shows strong recall for API-design findings at
82% but poor recall for business-logic edge cases in quiz scoring at 34%. When you add few-shot examples of logic bugs to the prompt, logic recall improves to 41%, but API-design recall drops to
68%. How should you address this trade-off to improve detection across both categories?

• A. Upgrade to a more capable model tier because its stronger reasoning will handle both concern types in a single prompt and eliminate the recall trade-off.
• B. Split the review into separate focused prompts--one for security and API design and another for business logic--each with dedicated examples, and then consolidate the findings before posting.
• C. Provide the full repository as context instead of only the changed files and surrounding code, giving the model deeper visibility into business-logic patterns.
• D. Replace the few-shot examples with a detailed checklist of specific logic edge cases to verify, such as division by zero in score calculations and boundary conditions in grading thresholds.

An organization wants predictable outputs for automated invoice classification. Which API parameter should generally be LOWER?

• A. Max tokens
• B. Context window
• C. Prompt length
• D. Temperature

Your pipeline reviews approximately 200 database-migration scripts daily using the Message Batches API. Each request includes a shared 8,000-token system prompt containing migration- review guidelines and schema documentation, followed by an individual migration script. You added cache_control breakpoints to the shared system prompt in every request, but monitoring shows cache-hit rates of only 32%, with misses concentrated among requests processed later in the batch window. Which change addresses the root cause without adding sequential-processing latency?

• A. Configure the cache breakpoints to use the extended one-hour TTL instead of the default five- minute TTL.
• B. Add cache-prewarming requests with max_tokens: 0 at the beginning of every batch.
• C. Split the 200 requests into ten sequential batches of 20, submitting each batch only after the previous batch completes.
• D. Move the cache_control breakpoint from the shared system prompt to each migration script so similar code patterns can be reused.

You are building a structured data extraction system using Claude. The system extracts information from unstructured documents, validates the output using JavaScript Object Notation (JSON) schemas, and maintains high accuracy. It must handle edge cases gracefully and integrate with downstream systems.
Your system has been running for 3 weeks and human reviewers have corrected 847 extractions.
Analysis reveals a recurring pattern: when recipes use informal measurements like "a handful" or
"a splash," the model either invents specific amounts or leaves fields empty--accounting for 23% of all corrections.
How should you use this feedback to improve extraction accuracy?

• A. Fine-tune the model on the 847 corrected extractions.
• B. Implement a post-processing layer that uses pattern matching to detect informal measurement phrases in source text and automatically populate values when the extraction is empty.
• C. Update your JSON schema to add a "measurement_type" enum field (precise/informal).
• D. Add few-shot examples to your prompt demonstrating correct handling of informal measurements--extracting them verbatim rather than converting or omitting them.