Q26 of 60 — CCA Practice Exam

Claude Code for Continuous Integration

Your team has built a CI pipeline that invokes claude -p as a subprocess to auto-generate test scaffolding for pull requests. In roughly 15% of runs, Claude calls AskUserQuestion mid-session to resolve an ambiguity about the test framework. Because the pipeline runs headlessly, these calls hang indefinitely — the CI job times out after 10 minutes with no output. A teammate suggests returning permissionDecision: "defer" from a PreToolUse hook so the calling process can surface the question and resume later. Examining the pipeline logs, you notice that in the failing runs, Claude is making two or three parallel tool calls in the same turn — AskUserQuestion alongside Read calls. What is the most likely reason the defer approach will not solve the timeout in these cases?

A. The defer mechanism requires Claude Code v2.1.89 or later, and CI environments typically pin to an older version to ensure reproducibility, so the hook result is silently ignored and the tool proceeds through the normal permission flow.

B. When Claude makes multiple tool calls in a single turn, defer is ignored with a warning and the tool proceeds through the normal permission flow, leaving AskUserQuestion undeferred and the headless session hanging as before.

C. The defer mechanism only works in interactive terminal sessions; in non-interactive -p mode the hook result is silently discarded, so the AskUserQuestion call executes immediately and the pipeline hangs waiting for terminal input.

D. The cleanupPeriodDays retention sweep will delete the session before the CI pipeline can resume it, because the default 30-day window does not protect sessions that have been idle for more than a few hours between CI stages.