A. A long-lived stateful session protocol for a stateless single-call interaction.

B. An agent-to-agent handoff that introduces another Claude-based agent in front of the pricing service.

C. A bespoke streaming protocol layered over an unrelated asynchronous message bus.

D. A direct API call to the existing endpoint with the appropriate scoped credentials.

A. The outbound HTTP tool returns a 200 response when the assistant calls an allow-listed domain to fulfil a user-initiated data-lookup request.

B. The user submits a routine question and receives a routine answer.

C. Adversarial content in a retrieved document instructs the model to call the outbound HTTP tool and send sensitive content to an attacker-controlled URL.

D. The internal-document retrieval tool returns a document that the user is authorized to view.

A. A verbal walkthrough conducted on the day of handoff with no written architecture overview, ADRs, component contracts, evaluation framework, runbooks, playbook, or known limitations.

B. The most recent set of design presentation slides without component-level diagrams, interface contracts, an evaluation framework with a reference set, runbooks, or a known-limitations register.

C. Source code alone with no integrating architecture overview, ADRs, component contracts, evaluation framework, runbooks, on-call playbook, or known-limitations register to support the delivery team.

D. Architecture overview, ADRs, component contracts, evaluation framework with reference set, runbooks, on-call playbook, and known limitations.

A. The team has no recurring specialized tasks and uses Claude Code only for isolated general-purpose work that does not justify a dedicated system prompt or tool scope.

B. The team has a recurring specialized task, such as database schema review, that requires a focused system prompt, narrow tool permissions, and a specific model selection across many sessions.

C. The team wants every Claude Code interaction to use the same generic system prompt with no task- specific specialization, narrow tool permissions, or dedicated model selection.

D. The team has a one-time ad hoc question that will not recur and does not require a focused system prompt, narrow tool permissions, or dedicated model selection.

A. Propose a fixed scope that you commit to by default based on your own assumptions.

B. Begin prototyping a generic assistant against the broad request before the next deadline.

C. Recommend that the sponsor revise the request and resubmit it later for evaluation.

D. Facilitate a structured discovery to define the failing decision and the target metric.

A. Decision rationale, business outcomes, and high-level risk summary for executive review.

B. Feature delivery schedule, roadmap dependencies, and scope boundaries for the product manager.

C. Implementation timeline, component interfaces, and deployment sequence for the engineering team.

D. Threat model, control mappings, residual-risk acceptance criteria, and audit traceability.

A. Select Architecture Y based solely on the 50% cost reduction, since solution cost is the most important value pillar in healthcare budget-constrained environments.

B. Eliminate Architecture X on SLA grounds, then evaluate Architecture Y against the efficiency and solution cost pillars by calculating annual cost difference and assessing whether the quality delta materially impacts clinical workflow productivity.

C. Recommend a hybrid approach using Architecture X for complex cases and Architecture Y for routine cases, without additional analysis, since this preserves quality where it matters most.

D. Select Architecture X because the higher quality scores justify the cost premium, and any SLA gap can be addressed through infrastructure optimization after deployment.

A. Inspect the active permission rules across all scopes-managed, command-line, local, project, and user-to identify which rule is denying the action and confirm whether it should be amended or remain denied.

B. Grant the engineer unrestricted Bash access to bypass the specific rule causing the denial, removing all tool-pattern constraints rather than amending only the rule in question.

C. Disable the permission system entirely across all scopes to remove the denial, eliminating all tool- pattern and deny-rule controls rather than identifying and amending the specific rule.

D. Tell the engineer to retry the denied action verbatim repeatedly until the denial stops appearing, without inspecting the active permission rules to determine whether the denial is intentional.

A. List the configured Model Context Protocol (MCP) servers and inspect server status to identify connection failures.

B. File a support ticket with vendor support before any local reproduction or evidence collection.

C. Increase the model sampling temperature so that intermittent issues surface more frequently for analysis.

D. Reproduce the issue with a minimal reproduction case that isolates one variable at a time.

E. Roll back to the previous Claude Code version immediately to confirm whether the issue is version specific.