Q22 of 60 — CCA Practice Exam

Claude Code for Continuous Integration

Your CI pipeline uses Claude Code to automatically triage test failures: for each failing test, an agent calls a set of diagnostic tools to inspect logs, read source files, and propose a fix. Overnight, a batch of 47 test failures is processed. The next morning, engineers find that 12 of those failures have no fix proposal and no error in the pipeline logs — instead, the agent silently moved on to the next failure. Examining the raw API responses, you find that all 12 share stop_reason: "max_tokens" and contain incomplete tool use blocks. What is the most likely root cause, and what structural change would resolve it?

A. The agent's tool descriptions are too long, consuming input tokens that should be reserved for output; shorten the tool descriptions so the model has more room to generate complete responses and tool use blocks are no longer truncated mid-execution.

B. The agent loop does not inspect stop_reason before treating a response as complete; when output is truncated mid-tool-use-block, the agent must detect stop_reason: "max_tokens" and treat that invocation as a hard failure requiring retry or escalation — not silently advance to the next item.

C. The pipeline is processing too many failures concurrently, causing resource contention that limits how many tokens each individual response can use; reducing batch size and serializing requests will give each invocation its full token budget and prevent truncation.

D. The diagnostic tools are returning excessively verbose output that fills the context window before Claude can emit a complete tool use block; summarizing tool outputs before passing them back to the agent will free up space for Claude to finish generating its response.