Your enterprise has a contract with AWS that requires Claude API calls to flow through Amazon Bedrock rather than the direct Anthropic API. Your team is building a new Claude application and is unfamiliar with this constraint.
How would you build the application?

• A. Build two parallel implementations of every call, one for the direct Anthropic API and one for Bedrock, and pick the faster one at runtime.
• B. Build the application against the direct Anthropic API and ignore the contractual requirement to route Claude calls through Amazon Bedrock.
• C. Build the application against the direct Anthropic API now and migrate to Bedrock in a follow-up release once the team has more experience with the Bedrock API.
• D. Configure the application to invoke Claude through the Bedrock-compatible API path while keeping the application's logic provider-agnostic.

Your Claude agent has access to a tool that retrieves customer records. A teammate has noticed that the agent occasionally calls the tool with arguments the schema does not declare, and the tool's downstream service returns an error each time. The teammate proposes loosening the schema so the tool accepts whatever arguments the model produces.
How would you respond?

• A. Loosen the schema as the teammate proposed so the downstream service receives every call the agent makes during normal operation.
• B. Keep the schema strict, validate arguments before dispatching, and return a structured error so the agent can retry.
• C. Add a system prompt instruction telling the model to produce schema-conforming arguments, treating the prompt instruction as the primary mechanism for keeping the agent's tool calls valid.
• D. Remove the schema entirely and rely on the downstream service to reject invalid calls, treating the downstream service as the team's primary enforcement layer.

You are choosing between using STDIO-based communication and HTTP-based communication for an MCP server. The server will be invoked by a Claude Code session running locally.
Which communication pattern would you use?

• A. HTTP polling against the MCP server, treating HTTP as a substitute for the standard MCP communication patterns.
• B. HTTP on the grounds that HTTP is preferable to STDIO in any context the application might encounter during normal operation.
• C. STDIO and HTTP simultaneously for redundancy, with the team running two communication patterns at the same time across Claude Code sessions.
• D. STDIO because STDIO is well-suited to local process communication and avoids unnecessary network setup.

You are designing a Claude application that will require structured JSON output for downstream processing.
The output schema is well-defined, and downstream systems will reject malformed JSON.

• A. Define a clear schema and structure the prompt to request output in that schema, with downstream systems handling any validation needed.
• B. Define a clear schema, structure the prompt to request output in that schema, and validate Claude's output against the schema before passing it downstream.
• C. Structure the prompt to request output in a schema that is described in plain English, with downstream systems parsing whatever shape Claude produces.
• D. Avoid structured output and use free-form text everywhere instead, on the grounds that free-form text is more flexible and handles edge cases better than structured schemas.

A new agent your team built handles customer support tickets, but it routinely gets confused when a single ticket spans billing, shipping, and product issues. The agent often loses track of which sub-issue it has already addressed and revisits the same one. The team is considering architectural changes.
What architectural change would you recommend?

• A. Add detailed prompting that instructs the agent to track which sub-issues have been resolved and which remain.
• B. Increase the size of the agent's context window so it can hold the full ticket history at once.
• C. Introduce an orchestrator agent that delegates billing, shipping, and product sub-issues to dedicated subagents.
• D. Switch to a deterministic workflow that handles billing, shipping, and product issues in a fixed sequence.