exam-a · Q5

The coordinator provides detailed step-by-step instructions to the web search subagent, specifying exact search queries, source priorities, and date filters. Production monitoring reveals three issues: (1) the subagent reports “insufficient results” rather than trying alternative approaches when pre-specified searches fail, (2) research quality drops for emerging topics that don’t match expected patterns, and (3) the subagent rarely surfaces valuable tangential sources. What’s the most effective way to improve subagent adaptability?

1. AImplement a topic classification step where the coordinator categorizes requests as “well-defined” or “exploratory” and uses different instruction styles for each category.
2. BAdd explicit fallback directives to the detailed instructions: “If specified searches yield fewer than N results, attempt alternative query formulations before reporting failure.”
3. CRemove procedural details entirely, delegating with simple goals like “research X thoroughly” and relying on the subagent’s general capabilities.
4. DSpecify research goals and quality criteria (coverage breadth, source diversity, recency) rather than procedural steps, letting the subagent determine its search strategy.

nobody has checked this keyWhy

exam-a · Q12

After the web search and document analysis subagents complete their tasks, the coordinator needs to spawn the synthesis subagent to synthesize the findings. What is the correct approach for providing the synthesis subagent with the information it needs?

1. ASpawn the subagent with only a brief task description, relying on automatic context inheritance from the coordinator
2. BProvide the subagent with tool definitions that allow it to request outputs from other subagents via callbacks
3. CPass reference identifiers and configure the subagent with read access to a shared memory store where other subagents deposited their results
4. DInclude the complete findings from both subagents directly in the synthesis subagent’s prompt

community agreesWhy

exam-a · Q17

Your order management system requires tools for three distinct operations: issuing refunds (requires amount and reason), canceling orders (requires reason), and requesting reshipments (requires shipping address). Each operation shares an order_id parameter but has different additional requirements. You notice during testing that with your current unified tool design, the agent frequently omits required parameters or includes irrelevant ones. What design change will most effectively improve parameter accuracy?

1. AKeep one unified tool with a nested operation_details object parameter whose internal structure varies by operation type, documented in the tool description.
2. BKeep one unified tool but add JSON Schema if-then-else conditionals to enforce that parameters like amount are required only when the operation type is “refund”.
3. CSplit into three separate tools (issue_refund, cancel_order, request_reshipment), each defining only the parameters required for that specific operation.
4. DKeep one unified tool with all parameters marked optional, but add detailed few-shot examples in the system prompt showing correct parameter combinations for each operation type.

nobody has checked this keyWhy

exam-a · Q18

Your post_content tool requires user confirmation before publishing. The current workflow displays “Ready to post to social media. Confirm?” and analytics show users approve 98% of requests within 2 seconds. Post-mortems reveal incidents where posts went to wrong accounts, were scheduled for wrong times, or contained errors – all confirmed by users without catching the mistakes. How should you redesign the confirmation workflow?

1. AAuto-approve routine posts and only require explicit confirmation for unusual patterns like posting to new accounts or large audiences
2. BRequire users to type a confirmation phrase instead of clicking a button
3. CAdd a mandatory waiting period before the confirm option becomes available
4. DInclude the complete post text, target account, scheduled time, and platform in the confirmation request

nobody has checked this keyWhy

exam-a · Q19

Your agent uses three tools: get_property_details(property_id) returns data including street address, get_price_history(property_id) returns historical pricing, and get_neighborhood_info(address) returns area statistics. You observe that get_neighborhood_info always requires get_property_details first just to extract the address, even when users specify the property by ID. This creates unnecessary latency and failure coupling – if the first call fails, the neighborhood request also fails. What tool design change best addresses this?

1. ACreate a lookup_address(property_id) helper tool for retrieving addresses.
2. BAdd retry logic and timeout handling to get_property_details.
3. CChange get_neighborhood_info to accept property_id, resolving the address internally.
4. DConsolidate into a single get_property_with_neighborhood(property_id) tool returning both datasets.

nobody has checked this keyWhy

exam-a · Q20

Your update_user_profile tool accepts a user_id (required) and an optional fields_to_update object. In testing, Claude frequently omits user_id or passes incorrectly structured data. What is most critical for helping Claude understand what parameter values to provide?

1. AStrict JSON Schema type constraints marking user_id as required and defining fields_to_update as an object type
2. BVerbose parameter names encoding format hints, such as user_id_string_uuid_format
3. CDetailed error responses explaining why invalid parameter values were rejected
4. DClear parameter descriptions explaining expected format, such as “user_id: UUID of the user to update (required)”

community agreesWhy

exam-a · Q21

Your document extraction tool uses ML models to extract invoice fields (vendor, amount, date). The models return confidence scores (0.0-1.0) for each extracted field. In production, you observe: (1) the agent proceeds with low-confidence extractions that are incorrect 23% of the time, and (2) the agent requests unnecessary human review for 31% of extractions that were actually correct. How should you restructure the tool’s output?

1. AReturn fields with their raw confidence scores and add detailed few-shot examples to your system prompt demonstrating how to interpret different confidence ranges and when to request human review.
2. BReturn fields with confidence scores, plus a request_review boolean computed using your tested confidence thresholds, along with a review_reasons array explaining which fields triggered review.
3. CCompute an aggregate extraction_quality score across all fields and return it alongside the extracted values. Include a text summary describing the overall extraction reliability.
4. DReturn fields organized into verified and needs_verification objects based on confidence thresholds.

nobody has checked this keyWhy

exam-a · Q22

Your product search tool queries an external catalog API and returns matching items. In production, you observe the agent frequently retries searches immediately after receiving zero results, treating “no matches found” as a failure requiring retry. The external API returns HTTP 200 with an empty results array – a valid response. How should you restructure the tool’s result to help the agent correctly interpret empty result sets?

1. AAdd a suggestions field containing alternative search strategies when results are empty, helping guide the agent toward more productive follow-up queries.
2. BReturn a natural language string describing the outcome, allowing the agent to interpret the result contextually based on the message content.
3. CReturn a result object with isError: true and a message explaining no products matched.
4. DReturn a structured result with a success boolean and results array, reserving isError: true for actual execution failures only.

nobody has checked this keyWhy

exam-a · Q23

Your MCP server includes archive_file(file_id) and delete_file(file_id) tools. Production logs show the agent calls delete_file when users ask to “remove old backups,” but company policy requires archiving backup files. Both tools currently have minimal descriptions: “Archives a file” and “Deletes a file.” Which change most directly improves tool selection for this scenario?

1. AExpand tool descriptions to clarify use cases, adding guidance like “Do not use for backup files” to delete_file.
2. BAdd a confirmation step that requires users to type “CONFIRM DELETE” before delete_file executes.
3. CImplement server-side validation that rejects delete_file calls for files tagged as backups, returning an error message suggesting archive_file.
4. DAdd few-shot examples to the system prompt demonstrating that requests involving “backup” or “old” should use archive_file.

community says CWhy

exam-a · Q24

Your track_shipment(tracking_id) tool queries an external logistics API that sometimes fails – the API may be temporarily unavailable, the tracking ID may be malformed, or the shipment may not exist. Currently, your tool raises a Python exception when errors occur. Users report the agent gives unhelpful responses like “I’m having trouble with that request” instead of suggesting alternatives such as verifying the tracking number format or checking by order number. How should you handle errors in tool results?

1. AReturn a generic error response (e.g., {"success": false, "error": "lookup_failed"}) for all failure cases to maintain a consistent schema and avoid exposing internal error details.
2. BReturn structured error information as normal tool output including error type, recoverability status, and actionable context for the user.
3. CCreate dedicated error-recovery tools (retry_tracking_lookup, search_by_order_number) that the model can invoke after the primary tracking tool returns a failure indicator.
4. DImplement retry logic with exponential backoff inside the tool implementation so transient errors are automatically handled and only return a result after all retry attempts are exhausted.

nobody has checked this keyWhy

exam-a · Q25

Your MCP server implements a check_availability tool that queries an external calendar API. During testing, you encounter three error conditions: (1) the tool is called with a malformed request missing the required user_email parameter, (2) the calendar API returns a 404 because the specified user doesn’t exist in the calendar system, and (3) the calendar API returns a 503 because the service is temporarily unavailable. How should each error be reported according to MCP’s error handling design?

1. AReport all three as tool results with isError: true.
2. BReport errors 1 and 2 as JSON-RPC protocol errors; report error 3 as a tool result with isError: true.
3. CReport error 1 as a JSON-RPC protocol error; report errors 2 and 3 as tool results with isError: true.
4. DReport all three as JSON-RPC protocol errors.

nobody has checked this keyWhy

exam-a · Q26

Your send_notification tool calls third-party messaging APIs. When these services time out during delivery, you cannot determine whether the message was actually sent. Currently, the tool returns is_error: true with a generic “Notification failed” message for all timeouts. Production monitoring reveals agents automatically retry these failures, frequently causing users to receive duplicate notifications. How should you modify the error response?

1. AReturn is_error: true with a structured field retry_safe: true for timeouts, distinguishing them from permanent failures that should not be retried.
2. BReturn is_error: true with a message communicating uncertainty: “Timeout – status unknown. Message may have been sent. Avoid retry.”
3. CReturn is_error: true with a message encouraging retry: “Delivery service temporarily unavailable. Please retry the notification.”
4. DReturn is_error: true with the original message content echoed back.

nobody has checked this keyWhy

exam-a · Q27

Your control_device tool manages smart home devices through external APIs. When a device doesn’t respond within the timeout period, the tool returns an error. Production logs show that the agent simply tells users “the device is not responding” without offering helpful next steps. Which error response structure would best enable the agent to provide useful follow-up?

1. ASet is_error: true with a structured technical error containing the device ID, timeout duration, and raw API response code for debugging purposes.
2. BSet is_error: true with a brief “Device offline” message and provide a separate tool the agent can call to retrieve context-specific troubleshooting suggestions.
3. CSet is_error: false with an optimistic message indicating the command was dispatched successfully but device acknowledgment is still pending.
4. DSet is_error: true with a message explaining the likely cause and suggesting troubleshooting steps the agent can offer the user.

nobody has checked this keyWhy

exam-a · Q28

Your expense reimbursement agent processes employee requests using a process_reimbursement tool. Company policy requires that reimbursements above $500 must be approved by a manager before funds are disbursed. The agent handles hundreds of requests daily, and you need the threshold enforcement to be tamper-proof regardless of how the agent is prompted. Which design ensures the $500 approval threshold cannot be bypassed?

1. AThe process_reimbursement tool accepts amount and details, and internally enforces the threshold: amounts <$500 are auto-disbursed and the tool returns a success confirmation; amounts >$500 cause the tool to create a pending approval request and return a status indicating manager review is pending.
2. BThe process_reimbursement tool accepts an approved_by_manager: boolean parameter. The system prompt instructs the agent to only set this to true after confirming that a manager has approved the request. A nightly audit script reviews all reimbursements where approved_by_manager was set to true.
3. CProvide two tools: auto_reimburse (hard-coded limit of $500) and request_manager_approval. Include detailed system prompt instructions telling the agent to check the amount and call the appropriate tool. Add a PostToolUse hook that logs which tool was called for auditing.
4. DImplement the threshold check in a PreToolUse hook that inspects the amount parameter before process_reimbursement executes. If the amount exceeds $500, the hook modifies the tool call to add a requires_approval: true flag, which the tool checks before disbursing.

nobody has checked this keyWhy

exam-a · Q29

Your content curation agent discovers articles, analyzes each for relevance, then adds selected articles to themed collections. With separate discover_articles(topic), analyze_article(id), and add_to_collection(article_id, collection_id) tools, you observe 18+ sequential tool calls per request, causing latency issues. The agent must make editorial judgments about which articles fit a collection’s theme – this requires seeing all candidates with their analysis scores simultaneously to select a cohesive set. What tool composition best addresses efficiency while preserving editorial judgment?

1. AKeep all tools separate but implement response caching for analyze_article calls.
2. BCreate a curate_collection(topic, collection_id) tool that handles discovery, analysis, and selection internally using configurable quality thresholds.
3. CCreate a discover_and_analyze(topic) composite tool that returns all candidates with their analysis scores, keeping add_to_collection separate for selective calls.
4. DAdd a preview_curation(topic, collection_id) tool that shows what would be added based on predefined rules, with an approve_curation() tool to confirm.

nobody has checked this keyWhy

exam-a · Q31

Compliance requires that refunds exceeding $500 must automatically escalate to a human agent – this rule cannot be left to model discretion. Despite clear system prompt instructions, production logs show the agent occasionally processes high-value refunds directly (3% failure rate). How should you achieve guaranteed compliance?

1. AModify the refund tool to return an error with message “Amount exceeds policy limit – please escalate” when threshold is exceeded.
2. BAdd few-shot examples to the prompt showing correct escalation behavior at various refund amounts ($400, $500, $600).
3. CImplement a hook to intercept tool calls; when the refund process amount exceeds $500, block it and invoke human escalation.
4. DStrengthen the system prompt with emphatic language: “CRITICAL POLICY: Refunds over $500 MUST trigger human escalation. NEVER process these directly.”

nobody has checked this keyWhy

exam-a · Q35

Your get_portfolio_value tool returns the total value of a user’s investment portfolio. You’re deciding between returning a structured JSON object with explicit fields versus returning the information as a formatted text string. What is the primary advantage of using structured output with defined fields?

1. AJSON schemas automatically validate that the underlying API returned correct data before the agent processes it.
2. BStructured JSON consumes significantly fewer tokens than natural language, substantially reducing API costs.
3. CStructured JSON is processed deterministically by the model, significantly improving accuracy when extracting values.
4. DThe agent can reliably extract specific values without parsing free-form text, reducing errors in subsequent operations.

nobody has checked this keyWhy

exam-a · Q37

Your conversational assistant frequently generates multiple clarifying questions when users make ambiguous requests. When a user asks “Can you help me with the report?”, the assistant responds: “I’d be happy to help! Could you tell me: 1) Which report? 2) What kind of help – drafting, reviewing, or formatting? 3) What’s your deadline?” User analytics show a 40% conversation abandonment rate after these multi-question responses. What’s the most effective way to reduce friction while appropriately handling ambiguity?

1. ALimit the assistant to one clarifying question per turn, using conversation history to accumulate answers over multiple exchanges rather than requesting everything upfront.
2. BAdd a preprocessing step using a smaller model to classify request ambiguity on a 1-5 scale, routing high-ambiguity requests to a clarification dialog and low-ambiguity requests directly to the assistant.
3. CModify the system prompt to instruct the assistant to make reasonable assumptions from available context, state those assumptions explicitly, and offer to adjust if the interpretation is wrong.
4. DCreate a lookup table of common request patterns with predefined default interpretations, having the assistant respond with those defaults without stating the assumptions made.

nobody has checked this keyWhy

exam-a · Q38

After 30+ turns, your conversational assistant shows noticeably slower responses and occasionally produces less coherent outputs. Investigation reveals: (1) average conversations reach 50,000 tokens by turn 35, (2) production logs show 94% of user messages only reference the previous 3- 5 exchanges, (3) the 6% of queries referencing earlier context typically ask about information the user could easily re-state. Your goal is to improve response speed and quality while maintaining good user experience. What’s the most effective approach?

1. AEnable prompt caching and continue sending the complete conversation history, using cached prefixes to reduce per-request costs while preserving all context.
2. BBuild a retrieval system that stores all conversation turns and uses semantic search to pull in relevant historical context only when the current query appears to reference past information.
3. CImplement a summarization layer that progressively compresses older conversation turns into a running summary while keeping the most recent 5-6 turns verbatim, maintaining full historical context in condensed form.
4. DImplement a sliding window keeping only the system prompt and last 8-10 turns. When users reference earlier context, acknowledge the limitation and ask them to re-state the relevant information.

community says DWhy

exam-a · Q39

Production monitoring shows that follow-up queries like “summarize what we learned about market trends” consistently take 40+ seconds. Investigation reveals the coordinator spawns the synthesis subagent for each summarization request, passing 80K+ tokens of accumulated findings. The coordinator already has these findings in its context from orchestrating the research. What’s the most effective way to improve response time for these follow-up summaries?

1. AEnable prompt caching on the synthesis subagent to reduce the overhead of repeatedly transferring the same research findings.
2. BHave the coordinator handle straightforward summarization requests directly using its existing context, reserving subagent spawning for complex analysis.
3. CPre-generate and cache summaries at multiple granularities whenever new findings accumulate.
4. DSpawn the synthesis subagent with reduced context and have it request specific findings from the coordinator on-demand.

nobody has checked this keyWhy

exam-a · Q40

A customer raises three separate issues during one session: a refund inquiry (turns 1-15), a subscription question (turns 16-30), and a payment method update (turns 31-45). At turn 48, the customer asks “What happened with my refund?” The conversation is approaching context limits. What strategy best maintains the agent’s ability to address all issues throughout the session?

1. AExtract and persist structured issue data (order IDs, amounts, statuses) into a separate context layer.
2. BSummarize earlier turns into a narrative description, preserving full message history only for the active issue.
3. CRely on MCP tools to re-fetch relevant information on demand when the customer references earlier issues.
4. DImplement sliding window context that retains the most recent 30 turns.

nobody has checked this keyWhy

exam-a · Q44

A customer sends: “This is frustrating. I’ve explained my issue twice and nothing is being resolved. I want to talk to a real person NOW.” The agent has not yet called any tools to investigate their account. What should the agent do?

1. AImmediately call escalate_to_human with the conversation history.
2. BBriefly explain what the agent can help with and offer to resolve the issue quickly, escalating only if the customer repeats their request.
3. CFirst call get_customer and lookup_order to gather account context, then escalate to a human agent.
4. DAcknowledge the frustration and ask one targeted question to understand the specific issue before escalating.

community says CWhy

exam-a · Q46

The agent verifies customer identity through a multi-step process before resetting passwords. During testing, you notice that after the customer answers the third verification question, the agent asks them to provide their name again, as if the earlier exchange never happened. What’s the most likely cause of this behavior?

1. AThe verification tool is clearing the agent’s internal state after each successful validation step.
2. BClaude’s memory retention is limited to two conversational turns by default, requiring explicit configuration to extend it.
3. CThe conversation history isn’t being passed in subsequent API requests.
4. DThe prompt lacks instructions telling Claude to remember information across multiple exchanges.

nobody has checked this keyWhy