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

Your Claude application validates structured output but has been treating validation failures as terminal errors. Each validation failure causes the entire user request to fail. The team wants to handle validation failures more gracefully.
How would you handle the validation failures?

• A. Pass validation failures directly to downstream systems and let each downstream system decide how to handle the malformed output.
• B. Tell users that validation failures are unavoidable and instruct them to perform manual accuracy checks before relying on outputs.
• C. Treat validation failures as a recognized error path that triggers retry, repair, or fallback logic before failing the user request.
• D. Disable output validation until the underlying cause of validation failures has been identified and addressed in a future release.

Your Claude application is deployed to development, staging, and production environments. Each environment uses a different model version, different prompt versions, and different plugin dependencies, but the configuration is currently scattered across environment variables, hardcoded values, and undocumented setup scripts.
How would you manage the configuration?

• A. Use the latest available model version everywhere and stop pinning model versions, on the grounds that pinning adds maintenance overhead the team should aim to reduce.
• B. Move all configuration into hardcoded application code to reduce reliance on external configuration sources that are difficult to track over time.
• C. Consolidate the configuration into a version-controlled system documenting model version pinning, prompt versioning, and plugin dependencies for each environment.
• D. Standardize all environments to use the same configuration values to eliminate the differences between development, staging, and production.

A teammate has asked you to explain why your Claude agent's tools include detailed descriptions in the tool definition, even when the tool name is already descriptive. The teammate suggests removing the descriptions to simplify the tool definitions.
How would you respond?

• A. Suggest moving the descriptions out of the tool definition and into a separate documentation file the team maintains so the tool definitions stay short and the descriptions remain available.
• B. Explain that the model uses the tool description to decide when to call the tool, and descriptions disambiguate cases where the tool name is not enough.
• C. Agree with the teammate because tool names are sufficient for the model to choose the right tool on every request the agent handles.
• D. Suggest replacing the descriptions with example calls embedded in the tool definition, treating example calls as a complete substitute for the prose description.