Q01 - Question
A procurement agent initiates purchase orders that exceed a financial threshold. The solution must pause the agent action and wait for a manager's approval before the order is placed. The approval may take hours. Which workflow characteristic is most important for this scenario?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Synchronous in-memory polling that blocks the agent thread until the manager responds.
- B. A durable asynchronous approval workflow that persists state until the approver responds.
- C. An automatic timeout that approves the order if no response is received within five minutes.
- D. A retry loop that resends the order without approval after three failed notification attempts.
B is correct.
Explanation: The evidence supports using durable asynchronous approvals for agent-initiated actions. This ensures the approval state is preserved even when the response takes hours.
A is incorrect: Blocking the agent thread synchronously wastes resources and does not scale when approvals take hours.
C is incorrect: Automatically approving on timeout defeats the purpose of requiring human oversight for high-impact financial actions.
D is incorrect: Retrying and then proceeding without approval bypasses the required human intervention.
Q02 - Question
An agent in your multi-agent solution produced an unexpected output during a production transaction. The issue does not recur when you rerun the same input in a staging environment. You need to reproduce the exact failure conditions. What should you use?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Increased logging verbosity in the staging environment
- B. Deterministic agent replay
- C. A duplicate agent instance in production
- D. Manual reconstruction of the agent's prompt and context
B is correct.
Explanation: The evidence supports B because agent replay enables deterministic reproduction of production execution paths, which is essential when failures cannot be reproduced in staging environments.
A is incorrect: Increasing logging verbosity does not guarantee reproduction of the original failure.
C is incorrect: Deploying a duplicate instance does not reproduce the exact conditions of the original failure because nondeterministic factors may differ.
D is incorrect: Manual reconstruction from memory is unreliable and does not provide deterministic replay.
Q03 - Question
A team updates its multi-agent solution frequently. The team is concerned that agent behavior can drift and reduce quality. The team wants to detect drift before each change reaches production. What should the team do?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Review customer feedback after each release and investigate quality problems then.
- B. Run the evaluation once at initial launch and reuse the results for later releases.
- C. Add regression testing as a gate in the CI/CD pipeline so that evaluation runs before deployment.
- D. Test only the individual agents that changed and skip end-to-end evaluation.
C is correct.
Explanation: The evidence states that building regression testing pipelines and using CI/CD regression gates evaluates multi-agent quality and catches agent drift before deployment.
A is incorrect: Reviewing feedback after release detects problems after deployment, failing the requirement to detect drift before production.
B is incorrect: A single launch evaluation does not reflect later changes and cannot detect drift introduced by subsequent updates.
D is incorrect: Testing only individual agents omits end-to-end system metrics, which are required to evaluate multi-agent quality.
Q04 - Question
You are configuring telemetry aggregation and alerts for a multi-agent solution in Azure Monitor. You need to configure an alert that accurately detects latency degradation without being skewed by outliers. Which metric should you use?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Average end-to-end latency.
- B. P95 latency degradation.
- C. Total output tokens by agent.
- D. Escalation rates.
B is correct.
Explanation: The evidence recommends configuring dynamic alerts for P95 latency degradation and emphasizes using percentiles rather than averages to track latency.
A is incorrect: The evidence explicitly states to use percentiles rather than averages for latency tracking.
C is incorrect: Total output tokens track usage and cost, not latency degradation.
D is incorrect: Escalation rates track how often agents escalate to human operators, not system latency.
Q05 - Question
A customer interaction passes through several agents in a multi-agent system. You want a single correlated view of each interaction in Azure Monitor. Which design should you use?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Configure each agent to generate its own trace ID and join the records by timestamp.
- B. Record session context in the first agent and omit identifiers in downstream agents.
- C. Use OpenTelemetry to propagate a shared trace ID across every agent in the interaction.
- D. Send each agent's telemetry to Azure Monitor separately and review the records in isolation.
C is correct.
Explanation: OpenTelemetry distributed tracing primitives propagate a shared trace ID across every agent. This gives you one correlated view of each customer interaction in Azure Monitor.
A is incorrect: Separate trace IDs produce disconnected traces. Joining them by timestamp relies on guesswork instead of a shared identifier.
B is incorrect: Downstream agents without identifiers cannot be linked to the interaction. The trace ID must propagate across all agents.
D is incorrect: Reviewing each agent's records in isolation does not produce a unified view of the complete customer journey.
Q06 - Question
A company deploys a multi-agent solution that handles both routine customer inquiries and high-impact contract amendments. The team wants to add human oversight without significantly reducing automation throughput. Which design principle best aligns with the goal of human-in-the-loop workflows?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Require manual approval for every agent action to maximize safety.
- B. Apply targeted oversight to uncertain, high-impact, and regulated decisions while keeping routine actions automated.
- C. Remove human oversight entirely and rely on post-hoc auditing to detect errors.
- D. Limit human oversight to only those actions that have previously caused failures.
B is correct.
Explanation: The evidence states that human-in-the-loop workflows provide targeted oversight for uncertain, high-impact, and regulated multi-agent decisions without making every action manual. This balances automation velocity with human oversight.
A is incorrect: Requiring manual approval for every action eliminates the automation benefit and contradicts the principle of targeted oversight.
C is incorrect: Removing human oversight entirely does not satisfy the requirement for consequential oversight of high-impact and regulated decisions.
D is incorrect: Limiting oversight only to previously failed actions misses uncertain or novel high-impact decisions that have not yet produced a failure.
Q07 - Question
A company is deploying a production multi-agent system and needs to reduce operational costs while preserving customer experience. Which combination of techniques should the team prioritize to optimize cost without sacrificing quality?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Complexity-aware model routing, multi-level caching, and token and context management
- B. Uniform model routing, single-level caching, and maximizing token limits
- C. Routing all tasks to the most capable model and disabling context management
- D. Applying uniform token budgets and routing all requests to a single model
A is correct.
Explanation: The evidence supports A because production multi-agent cost optimization uses complexity-aware model routing, multi-level caching, token and context management, and quality-cost-latency tradeoffs without sacrificing customer experience.
B is incorrect: Uniform model routing and maximizing token limits raise costs and do not optimize the system.
C is incorrect: Routing all tasks to the most capable model ignores complexity-aware routing and increases unnecessary cost for simpler tasks.
D is incorrect: Applying uniform token budgets and routing all requests to a single model fails to optimize for cost and complexity.
Q08 - Question
A team observes that token consumption in their multi-agent system is growing rapidly as conversations lengthen. Which optimization area should the team focus on to control this growth?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Model routing configuration
- B. Semantic-cache thresholds
- C. Token usage and context management
- D. Customer-segment SLA definitions
C is correct.
Explanation: The evidence supports C because optimizing token usage and context management directly addresses controlling how much context is passed to models as conversations grow, reducing unnecessary token consumption.
A is incorrect: Model routing selects which model handles a task but does not directly manage growing context size within a conversation.
B is incorrect: Semantic-cache thresholds help with repeated queries but do not address the problem of expanding context in ongoing conversations.
D is incorrect: SLA definitions set quality and latency targets per customer segment but do not directly manage token consumption in long conversations.
Q09 - Question
An insurance claims agent produces a confidence score for each claim decision. The architect must design an escalation strategy that routes low-confidence decisions to a human reviewer. Which approach should the architect use?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Route all decisions to a human reviewer regardless of confidence score.
- B. Use a calibrated confidence threshold so that decisions below the threshold escalate to a human reviewer.
- C. Discard low-confidence decisions and ask the customer to resubmit.
- D. Log low-confidence decisions for a weekly batch review without pausing the action.
B is correct.
Explanation: The evidence supports using calibrated escalation to determine which agent decisions require human intervention. This ensures that uncertain outcomes receive review while high-confidence decisions proceed automatically.
A is incorrect: Routing all decisions to a human reviewer negates the benefit of confidence scoring and reduces automation velocity.
C is incorrect: Discarding low-confidence decisions does not provide human oversight and creates a poor customer experience.
D is incorrect: Allowing the action to proceed without pausing removes the opportunity for a human to intervene before a potentially incorrect decision takes effect.
Q10 - Question
A multi-agent system receives many repeated queries throughout the day. The operations team wants to reduce both latency and token costs. Which strategy directly addresses both goals?
Domain: Evaluate, optimize, and monitor multi-agent solutions (20–25%) Type: Single choice
- A. Increase the token budget for each agent
- B. Implement multi-level caching strategies
- C. Disable context management for repeated queries
- D. Configure quality-floor model escalation
B is correct.
Explanation: The evidence supports B because multi-level caching strategies allow repeated queries to be served from cache, reducing both the token cost of redundant model calls and the latency of generating new responses.
A is incorrect: Increasing the token budget does not reduce latency or cost for repeated queries; it increases token consumption.
C is incorrect: Disabling context management does not address caching of repeated queries and may degrade response quality.
D is incorrect: Quality-floor model escalation is used for routing, not for caching repeated queries.