Q32 of 60 — CCA Practice Exam

Multi-Agent Research System

Your multi-agent research system uses PreToolUse hooks to validate each subagent's external API calls before execution. During a large overnight research run, logs show that roughly 12% of hook callbacks are timing out — specifically on callbacks that perform a secondary compliance check against an internal policy API. When these timeouts occur, the affected subagent stalls and the overall research pipeline halts. A junior engineer proposes removing the compliance check from the hook entirely and running it as a post-processing step after results are collected. What is the most effective architectural fix that preserves the blocking guarantee of the pre-execution check?

A. Increase the timeout value in the HookMatcher configuration to give the compliance API call sufficient time to complete before the hook is considered failed.

B. Remove the compliance check from the PreToolUse hook and implement it as a PostToolUse hook that flags non-compliant results for human review after execution.

C. Add a stronger instruction in the subagent's system prompt telling it to pause and retry API calls if a compliance error is detected, reducing the frequency of non-compliant tool calls reaching the hook.

D. Replace the synchronous compliance API call inside the hook callback with a cached local policy check, reserving the full remote compliance call for a periodic background refresh of the cache.