CCAR-F practice › Context Management & Reliability · Question 94 of 105
Context Management & Reliability
A compliance-research subagent queries a regulatory filings database. When the database times out, the subagent catches the error and returns an empty results list with a success status. Final reports state "no relevant filings found" for companies whose filings were never retrieved. What is the root cause?
Show answer and explanation
Answer: B — The subagent reports an access failure the same way as a valid empty result
Returning an empty success for a timeout suppresses the error, so the coordinator can't tell "we couldn't look" from "we looked and found nothing." Access failures and valid empty results must be reported distinctly. (A) matters downstream, but the information was already lost. (C) may reduce timeouts but leaves the reporting flaw. (D) is the opposite anti-pattern, terminating on a single failure.
Keep going
More Context Management & Reliability questions
- You are defining how a web-search subagent handles failures so the coordinator can make…
- A research coordinator continues with partial results when two of seven sources remain…
- Two hours into a Claude Code session spent reading files in a large codebase, Claude now…
- An agent must assess the impact of changing refund logic in a large monorepo. Running…
- A multi-agent exploration of a monorepo crashes about 70% of the way through. Restarting…