Your Claude application receives untrusted input from external sources. The team is establishing how the application should treat this untrusted input.
Untrusted input would be...

• A. Routed through a separate Claude application with more lax security controls so the original application does not handle the untrusted input directly.
• B. Validated and sanitized before being incorporated into prompts, and treated as data the model should not interpret as instructions.
• C. Treated identically to trusted input from internal sources, on the grounds that all input the application receives can be handled the same way.
• D. Blocked entirely so the application accepts only trusted input, with no path for legitimate external input the application might process.

You are designing an agent that handles a multi-step research task. You want the agent to break the task into smaller pieces, hand each piece to a focused subagent, and consolidate the results.
The agent pattern you would apply is...

• A. A context-window pruning pattern that drops each subtask's content after the agent moves on.
• B. A memory pattern that stores the entire research history in advance, before any subtask begins execution.
• C. A single tool-use loop that includes every tool the agent might need across all subtasks.
• D. An orchestrator and subagent pattern with specialized subagents assigned to each subtask.

You are setting up the configuration management approach for a new Claude Code project. Your team will use CLAUDE.md files and settings.json files to control behavior, and you want to make sure changes are tracked and reviewable.
The configuration management approach would...

• A. Version-control CLAUDE.md and settings.json files alongside the project's source code, with changes reviewed through standard pull request workflows the team applies.
• B. Version-control CLAUDE.md and settings.json files in a separate repository from the project's source code, so configuration evolves independently from the application code over time.
• C. Duplicate CLAUDE.md and settings.json files in multiple repositories to provide redundancy, on the grounds that a single source of truth is risky for project configuration.
• D. Version-control CLAUDE.md alongside the project's source code and settings.json files in a separate repository from the project's source code.

You are configuring Claude Code for a new project. The team needs to set permissions, default model selections, and environment-specific behavior at the project level so the configuration is consistent across all developers working on the repository.
The Claude Code mechanism you would use is...

• A. Environment variables that each developer sets on their own machine when working with Claude Code on the project.
• B. A system prompt embedded in every Claude Code conversation by each developer at the start of every session in the project.
• C. The settings.json file, scoped at the project level so the configuration applies consistently across developers and persists with the repository.
• D. A shared spreadsheet that lists configuration values for team members to reference and update by hand as the project evolves.

You are designing an agent that processes vendor invoices. The work involves a small number of well- understood steps, but occasionally an invoice arrives in an unexpected format that requires the system to decide between rerouting, requesting clarification, or flagging for human review.
The most appropriate architecture for this system is...

• A. A workflow for the standard path with an agent invoked at the decision point for unexpected formats.
• B. A single large prompt that processes every incoming invoice, both standard and unexpected, in one model call.
• C. A manager agent that delegates each step of standard invoice processing to a dedicated subagent, with a separate subagent handling each unexpected format.
• D. A fully autonomous agent that handles every invoice from start to finish across all formats.