Question 230
Before approving the proposed action to use a content-extraction tool for uploaded forms, which measurable acceptance check should be required?
- Test out-of-scope requests for proper refusal or delegated escalation
- Trace agent runs for actual knowledge-tool invocation and check support for each source-grounded answer
- Compare computed totals against independently verified reference calculations
- Measure field-level extraction accuracy on labeled scans and low-quality images
Explanation
Correct Answer
D:The accepted change is to use a content-extraction tool for uploaded forms; this evaluation checks whether it can enable an agent to read key fields from photographed or scanned paperwork, since document extraction tools convert visual text and layout into structured data suitable for subsequent agent reasoning.
Incorrect Answers
A:This test concerns the ability to keep a support agent focused on diagnosing product issues rather than taking unrelated administrative action, for which a clear role and allowed-goal scope guide planning; enforceable permissions remain necessary at tool boundaries; it does not establish whether the change to use a content-extraction tool for uploaded forms works for the current release.
B:This test concerns the ability to invoke governed document search as a tool at the point the agent needs evidence for an answer, for which an agent run needs explicit retrieval calls and returned context before composing a grounded response; model parameters alone do not fetch current documentation; it does not establish whether the change to use a content-extraction tool for uploaded forms works for the current release.
C:This test concerns the ability to let an agent aggregate a supplied numeric CSV where exact computation is important, for which a sandboxed execution tool performs calculations deterministically; executable code needs strict isolation and resource limits; it does not establish whether the change to use a content-extraction tool for uploaded forms works for the current release.
Question 231
The team plans to require approval before irreversible business actions. Which test provides the clearest evidence that this change works?
- Inspect tool-call schema adherence and argument-validation failure rate
- Simulate unapproved requests and verify that no closure is committed
- Inspect inter-agent messages for unauthorized fields and verify output correctness
- Force timeouts and confirm the payment ledger records one transaction
- Inject mid-workflow failures and audit the final reconciled business state
Explanation
Correct Answer
B:The accepted change is to require approval before irreversible business actions; this evaluation checks whether it can prevent an autonomous agent from executing account closure without explicit review, since a human approval checkpoint separates proposed actions from committed side effects and provides an auditable decision.
Incorrect Answers
A:This test concerns the ability to make the parameters of an account-lookup function explicit to the model and executor, for which a typed tool contract constrains argument names and shapes and simplifies validation; authorization still occurs on execution; it does not establish whether the change to require approval before irreversible business actions works for the current release.
C:This test concerns the ability to stop one agent from receiving private data that another agent needed only for its subtask, for which scoped messages and redacted handoff contracts minimize sensitive context propagation across multiple agents; it does not establish whether the change to require approval before irreversible business actions works for the current release.
D:This test concerns the ability to prevent double charging when an agent retries after a network timeout, for which an idempotency key ties a logical transaction to one effect even if the same request is retried; it does not establish whether the change to require approval before irreversible business actions works for the current release.
E:This test concerns the ability to recover from a partially completed workflow when a later operation fails, for which a compensating action undoes or offsets previously committed steps where a transaction cannot be atomic across services; it does not establish whether the change to require approval before irreversible business actions works for the current release.
Question 232
A release reviewer is assessing a feature intended to orchestrate agent knowledge lookup during a conversation. Which test is most meaningful?
- Red-team embedded document instructions and inspect unauthorized tool-call attempts
- Measure field-level extraction accuracy on labeled scans and low-quality images
- Trace agent runs for actual knowledge-tool invocation and check support for each source-grounded answer
- Compare computed totals against independently verified reference calculations
Explanation
Correct Answer
C:The accepted change is to orchestrate agent knowledge lookup during a conversation; this evaluation checks whether it can invoke governed document search as a tool at the point the agent needs evidence for an answer, since an agent run needs explicit retrieval calls and returned context before composing a grounded response; model parameters alone do not fetch current documentation.
Incorrect Answers
A:This test concerns the ability to keep untrusted customer-uploaded text from redefining the agent's permissions, for which trusted control instructions must have higher precedence than external content; retrieved pages are data, not agent policy; it does not establish whether the change to orchestrate agent knowledge lookup during a conversation works for the current release.
B:This test concerns the ability to enable an agent to read key fields from photographed or scanned paperwork, for which document extraction tools convert visual text and layout into structured data suitable for subsequent agent reasoning; it does not establish whether the change to orchestrate agent knowledge lookup during a conversation works for the current release.
D:This test concerns the ability to let an agent aggregate a supplied numeric CSV where exact computation is important, for which a sandboxed execution tool performs calculations deterministically; executable code needs strict isolation and resource limits; it does not establish whether the change to orchestrate agent knowledge lookup during a conversation works for the current release.
Question 233
A cloud engineering team needs its AI workflow to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed. What technical approach most directly enables that?
- Expire temporary secrets and tool results
- Limit information passed between specialist agents
- Preserve short-term dialogue references
- Summarize old dialogue for context-window management
Explanation
Correct Answer
A:For the stated requirement to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed, short-lived state and purpose-based retention protect secrets and sensitive data; summarization is not a substitute for removal; this is the mechanism that the system must implement.
Incorrect Answers
B:For a system whose objective is to stop one agent from receiving private data that another agent needed only for its subtask, scoped messages and redacted handoff contracts minimize sensitive context propagation across multiple agents; this does not directly meet the required outcome to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed.
C:For a system whose objective is to resolve 'those two records' by retaining the preceding selection context, conversation tracking gives referential continuity across turns, but the context should be bounded to the correct user session; this does not directly meet the required outcome to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed.
D:For a system whose objective is to retain key decisions after a long conversation becomes too large to replay verbatim, a validated rolling summary compresses history while preserving commitments and identifiers; careless compression can discard safety constraints; this does not directly meet the required outcome to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed.
Question 234
The support ticket describes this behavior: The agent receives a scanned application as bytes but cannot access its checked boxes or line items. Which engineering change should come first?
- Invoke an authorized OCR-and-layout extraction tool before applying business rules
- Use an approved shared tool integration with centralized access policy and secret handling
- Use a permitted status lookup tool with the customer's authorization context
- Route approved computation to an isolated code tool with validated file inputs
Explanation
Correct Answer
A:The fault signal is that the agent receives a scanned application as bytes but cannot access its checked boxes or line items; the targeted fix works because document extraction tools convert visual text and layout into structured data suitable for subsequent agent reasoning, restoring the ability to enable an agent to read key fields from photographed or scanned paperwork.
Incorrect Answers
B:If the failing function were to avoid giving every agent separate uncontrolled credentials for the same external service, this change could be relevant because centralized governed tool access can standardize authentication and logging while each agent remains least privileged; the actual symptom is that the agent receives a scanned application as bytes but cannot access its checked boxes or line items, which calls for a different repair.
C:If the failing function were to let an agent check a shipment's present location without permission to modify the order, this change could be relevant because a scoped API tool obtains current transactional facts while maintaining least-privilege read access; the actual symptom is that the agent receives a scanned application as bytes but cannot access its checked boxes or line items, which calls for a different repair.
D:If the failing function were to let an agent aggregate a supplied numeric CSV where exact computation is important, this change could be relevant because a sandboxed execution tool performs calculations deterministically; executable code needs strict isolation and resource limits; the actual symptom is that the agent receives a scanned application as bytes but cannot access its checked boxes or line items, which calls for a different repair.
Question 235
During a regression test, the following unexpected result occurs: A release shows more failed tasks but the team lacks evidence about which subsystem regressed. What should the engineer do?
- Categorize traces by root-cause stage and track regressions by version
- Evaluate external side effects and final artifacts against labeled target states
- Provide a precise function description and schema with required parameters
- Enable correlated tracing across decision and tool spans with appropriate redaction
Explanation
Correct Answer
A:The fault signal is that a release shows more failed tasks but the team lacks evidence about which subsystem regressed; the targeted fix works because failure classification links observed symptoms to the component that can be improved; a single aggregate error rate obscures causes, restoring the ability to prioritize corrections across retrieval misses, malformed tools, policy blocks, and model planning errors.
Incorrect Answers
B:If the failing function were to determine whether the agent actually achieved a multi-step business goal, this change could be relevant because task-success tests compare final system state with expected outcomes; prose fluency does not prove work was completed; the actual symptom is that a release shows more failed tasks but the team lacks evidence about which subsystem regressed, which calls for a different repair.
C:If the failing function were to make the parameters of an account-lookup function explicit to the model and executor, this change could be relevant because a typed tool contract constrains argument names and shapes and simplifies validation; authorization still occurs on execution; the actual symptom is that a release shows more failed tasks but the team lacks evidence about which subsystem regressed, which calls for a different repair.
D:If the failing function were to find where a lengthy agent plan diverges from intended workflow, this change could be relevant because per-step tracing captures model requests, tool parameters, statuses and transitions; a final response log hides the path taken; the actual symptom is that a release shows more failed tasks but the team lacks evidence about which subsystem regressed, which calls for a different repair.
Question 236
A solution architect is deciding how to make the parameters of an account-lookup function explicit to the model and executor. Which Azure AI pattern addresses that task?
- Design a typed tool schema for actions
- Define an agent's bounded role and objective
- Retrieve consented durable preferences when required
- Separate developer rules from retrieved instructions
Explanation
Correct Answer
A:For the stated requirement to make the parameters of an account-lookup function explicit to the model and executor, a typed tool contract constrains argument names and shapes and simplifies validation; authorization still occurs on execution; this is the mechanism that the system must implement.
Incorrect Answers
B:For a system whose objective is to keep a support agent focused on diagnosing product issues rather than taking unrelated administrative action, a clear role and allowed-goal scope guide planning; enforceable permissions remain necessary at tool boundaries; this does not directly meet the required outcome to make the parameters of an account-lookup function explicit to the model and executor.
C:For a system whose objective is to remember a customer's explicit notification preference across separate sessions, persistent preference storage is distinct from a single chat transcript and requires consent, access control, and deletion workflows; this does not directly meet the required outcome to make the parameters of an account-lookup function explicit to the model and executor.
D:For a system whose objective is to keep untrusted customer-uploaded text from redefining the agent's permissions, trusted control instructions must have higher precedence than external content; retrieved pages are data, not agent policy; this does not directly meet the required outcome to make the parameters of an account-lookup function explicit to the model and executor.
Question 237
A design review proposes to scope shared tool access centrally. Which measurable check would establish success on real inputs?
- Attempt cross-user requests and confirm access denials in both retrieval and tools
- Verify contract compatibility and rollback on representative client calls
- Inspect memory contents and verify secrets are absent after session termination
- Audit per-agent tool entitlements and cross-service invocation traces
Explanation
Correct Answer
D:The accepted change is to scope shared tool access centrally; this evaluation checks whether it can avoid giving every agent separate uncontrolled credentials for the same external service, since centralized governed tool access can standardize authentication and logging while each agent remains least privileged.
Incorrect Answers
A:This test concerns the ability to enforce what both the service and the delegated user are authorized to do, for which a workload identity authenticates the agent service, while user-aware authorization limits operations on behalf of a caller; it does not establish whether the change to scope shared tool access centrally works for the current release.
B:This test concerns the ability to let several applications consume an agent while its implementation changes under controlled release, for which versioned published endpoints decouple client contracts from internals and support staged promotion when the platform supports it; it does not establish whether the change to scope shared tool access centrally works for the current release.
C:This test concerns the ability to avoid retaining authentication tokens or temporary PII inside agent memory longer than needed, for which short-lived state and purpose-based retention protect secrets and sensitive data; summarization is not a substitute for removal; it does not establish whether the change to scope shared tool access centrally works for the current release.
Question 238
After deployment, the team observes: An agent searches repeatedly for a document that does not exist and never terminates. Which remediation addresses the likely cause?
- Use an approved shared tool integration with centralized access policy and secret handling
- Define and test compensating operations for successfully completed steps when later steps fail
- Set tool-call ceilings and route exhausted searches to a controlled no-result response
- Use stable operation identifiers and enforce idempotent processing server-side
Explanation
Correct Answer
C:The fault signal is that an agent searches repeatedly for a document that does not exist and never terminates; the targeted fix works because step, time, and spending limits create enforceable failure boundaries regardless of the prompt plan, restoring the ability to stop self-triggering tool loops from consuming unlimited tokens or external calls.
Incorrect Answers
A:If the failing function were to avoid giving every agent separate uncontrolled credentials for the same external service, this change could be relevant because centralized governed tool access can standardize authentication and logging while each agent remains least privileged; the actual symptom is that an agent searches repeatedly for a document that does not exist and never terminates, which calls for a different repair.
B:If the failing function were to recover from a partially completed workflow when a later operation fails, this change could be relevant because a compensating action undoes or offsets previously committed steps where a transaction cannot be atomic across services; the actual symptom is that an agent searches repeatedly for a document that does not exist and never terminates, which calls for a different repair.
D:If the failing function were to prevent double charging when an agent retries after a network timeout, this change could be relevant because an idempotency key ties a logical transaction to one effect even if the same request is retried; the actual symptom is that an agent searches repeatedly for a document that does not exist and never terminates, which calls for a different repair.
Question 239
An engineering team has a requirement to determine whether the agent actually achieved a multi-step business goal. Which capability should be in the initial design?
- Evaluate whether an agent chooses appropriate tools
- Run task-completion evaluations with ground truth
- Use a supervisor to coordinate parallel worker agents
- Analyze agent errors by failure class
Explanation
Correct Answer
B:For the stated requirement to determine whether the agent actually achieved a multi-step business goal, task-success tests compare final system state with expected outcomes; prose fluency does not prove work was completed; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to detect unnecessary or dangerous tool calls even when its final prose looks plausible, tool-selection evaluation examines intermediate actions and authorization fit, not only the final natural-language answer; this does not directly meet the required outcome to determine whether the agent actually achieved a multi-step business goal.
C:For a system whose objective is to combine independent research subtasks into a coherent final response with oversight, a supervisor can assign independent tasks, collect outputs, and apply cross-checks before presenting an answer; this does not directly meet the required outcome to determine whether the agent actually achieved a multi-step business goal.
D:For a system whose objective is to prioritize corrections across retrieval misses, malformed tools, policy blocks, and model planning errors, failure classification links observed symptoms to the component that can be improved; a single aggregate error rate obscures causes; this does not directly meet the required outcome to determine whether the agent actually achieved a multi-step business goal.
Question 240
After implementing a workflow to publish a versioned agent endpoint for stable clients, the team needs a robust release gate. Which check should it choose?
- Verify contract compatibility and rollback on representative client calls
- Monitor calls to the retired version and test that the old tool endpoint is inaccessible
- Attempt cross-user requests and confirm access denials in both retrieval and tools
- Measure field-level extraction accuracy on labeled scans and low-quality images
Explanation
Correct Answer
A:The accepted change is to publish a versioned agent endpoint for stable clients; this evaluation checks whether it can let several applications consume an agent while its implementation changes under controlled release, since versioned published endpoints decouple client contracts from internals and support staged promotion when the platform supports it.
Incorrect Answers
B:This test concerns the ability to remove old versions that retain deprecated tools without disrupting active clients, for which a controlled retirement checks clients, revokes unused credentials, and archives relevant audit records before deletion; it does not establish whether the change to publish a versioned agent endpoint for stable clients works for the current release.
C:This test concerns the ability to enforce what both the service and the delegated user are authorized to do, for which a workload identity authenticates the agent service, while user-aware authorization limits operations on behalf of a caller; it does not establish whether the change to publish a versioned agent endpoint for stable clients works for the current release.
D:This test concerns the ability to enable an agent to read key fields from photographed or scanned paperwork, for which document extraction tools convert visual text and layout into structured data suitable for subsequent agent reasoning; it does not establish whether the change to publish a versioned agent endpoint for stable clients works for the current release.