Practice Exams:

Microsoft AI-103 Dumps

EXAM: Developing AI Apps and Agents on Azure
Verified By Experts
Premium Bundle
$49.99

AI-103 Premium ETE File


  • Premium File 187 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-103 Practice Test 48

Question 470

During a reliability exercise, a security engineer must accept a change for search tool integration. The issue to be addressed is: An agent needs current internal documentation to answer product questions. Which concrete verification action demonstrates that the relevant behavior works?

  1. Attach an authorized file-search knowledge tool and return supported citations
  2. Run scenarios covering success refusal escalation and tool error states
  3. Ask a recently updated product question and confirm citations from the index
  4. Assume the model remembers documents uploaded after its last training date

Explanation

Correct Answer

C:

To verify this change, the customer support center should ask a recently updated product question and confirm citations from the index. Operators still need the implementation to attach an authorized file-search knowledge tool and return supported citations and the preventive requirement to scope search permissions to the user and validate citation coverage.

Incorrect Answers

A:

The action to attach an authorized file-search knowledge tool and return supported citations can contribute to search tool integration as a implementation step; here, an agent needs current internal documentation to answer product questions. In the customer support center acceptance review, trying to attach an authorized file-search knowledge tool and return supported citations does not test the exact search tool integration condition where an agent needs current internal documentation to answer product questions; the relevant test is to ask a recently updated product question and confirm citations from the index.

B:

For agent evaluation data, it can be sensible to run scenarios covering success refusal escalation and tool error states if an agent seems helpful but its actions frequently violate workflow constraints. Without the actual change to ask a recently updated product question and confirm citations from the index, the answer lacks the correct operational scope even if the alternate action is technically valid elsewhere.

D:

In the customer support center acceptance review, trying to assume the model remembers documents uploaded after its last training date does not test the exact search tool integration condition where an agent needs current internal documentation to answer product questions; the relevant test is to ask a recently updated product question and confirm citations from the index. Acceptance should instead demonstrate that the service can ask a recently updated product question and confirm citations from the index, using the described failure as the test criterion.

Question 471

At a pharmaceutical research group, the agent designer is preparing a service audit. The concrete requirement is: An agent must access a customer API using delegated user permissions. Which design action BEST addresses the stated need?

  1. Use a supported delegated OAuth flow with consent and scoped tokens
  2. Call a permitted endpoint and verify denied operations outside the grant
  3. Embed a tenant-wide administrative API key into the agent prompt
  4. Produce schema-validated output including status evidence and failure reason

Explanation

Correct Answer

A:

The proposed implementation is to use a supported delegated OAuth flow with consent and scoped tokens; this matches the operational requirement that an agent must access a customer API using delegated user permissions. The team can call a permitted endpoint and verify denied operations outside the grant. The team should also validate audience expiry and least privilege on tokens.

Incorrect Answers

B:

The action to call a permitted endpoint and verify denied operations outside the grant can contribute to external api auth for agent as a targeted acceptance check step; here, an agent must access a customer API using delegated user permissions. Choosing to call a permitted endpoint and verify denied operations outside the grant cannot directly replace the specified action to use a supported delegated OAuth flow with consent and scoped tokens when an agent must access a customer API using delegated user permissions.

C:

Choosing to embed a tenant-wide administrative API key into the agent prompt cannot directly replace the specified action to use a supported delegated OAuth flow with consent and scoped tokens when an agent must access a customer API using delegated user permissions. The actual implementation must use a supported delegated OAuth flow with consent and scoped tokens, because the stated service condition is that an agent must access a customer API using delegated user permissions.

D:

Choosing to produce schema-validated output including status evidence and failure reason cannot directly replace the specified action to use a supported delegated OAuth flow with consent and scoped tokens when an agent must access a customer API using delegated user permissions. The relevant corrective or preventive action here remains to use a supported delegated OAuth flow with consent and scoped tokens, with its own validation criteria.

Question 472

After a security tabletop exercise at a travel support provider, the team observes this failure: An agent must access a customer API using delegated user permissions. Which flawed assumption or implementation choice would MOST DIRECTLY explain why the intended outcome was not achieved?

  1. Use a supported delegated OAuth flow with consent and scoped tokens
  2. Call a permitted endpoint and verify denied operations outside the grant
  3. Send an unstructured free-text plan and assume the executor knows permissions
  4. Embed a tenant-wide administrative API key into the agent prompt

Explanation

Correct Answer

D:

This design mistake is to embed a tenant-wide administrative API key into the agent prompt; it conflicts with the actual external api auth for agent behavior needed when an agent must access a customer API using delegated user permissions. The travel support provider should instead use a supported delegated OAuth flow with consent and scoped tokens, followed by a check to call a permitted endpoint and verify denied operations outside the grant.

Incorrect Answers

A:

The alternative to use a supported delegated OAuth flow with consent and scoped tokens is a implementation step rather than the faulty assumption being diagnosed. This travel support provider failure-analysis alternative of use a supported delegated OAuth flow with consent and scoped tokens does not diagnose the particular external api auth for agent defect where an agent must access a customer API using delegated user permissions; the keyed mistake is embed a tenant-wide administrative API key into the agent prompt.

B:

The alternative to call a permitted endpoint and verify denied operations outside the grant is a targeted acceptance check step rather than the faulty assumption being diagnosed. This travel support provider failure-analysis alternative of call a permitted endpoint and verify denied operations outside the grant does not diagnose the particular external api auth for agent defect where an agent must access a customer API using delegated user permissions; the keyed mistake is embed a tenant-wide administrative API key into the agent prompt.

C:

The option to send an unstructured free-text plan and assume the executor knows permissions would normally serve a different multi-agent handoff schema requirement, where a planner agent passes incomplete instructions to an executor agent. The alternative may be useful in its own context, but it does not directly supply embed a tenant-wide administrative API key into the agent prompt for the stated decision.

Question 473

The scientific publisher is responding to a support escalation. A solution architect discovers this issue: An agent must access a customer API using delegated user permissions. What corrective step should the team take to restore the intended functionality most directly?

  1. Reroute the request to the correct domain specialist and review outputs
  2. Call a permitted endpoint and verify denied operations outside the grant
  3. Replace shared credentials with delegated scoped authorization
  4. Validate audience expiry and least privilege on tokens
  5. Embed a tenant-wide administrative API key into the agent prompt

Explanation

Correct Answer

C:

The direct repair is to replace shared credentials with delegated scoped authorization. Once the condition is corrected, the scientific publisher should call a permitted endpoint and verify denied operations outside the grant. To reduce recurrence, it should also validate audience expiry and least privilege on tokens; those steps provide different recovery and prevention functions.

Incorrect Answers

A:

The action to reroute the request to the correct domain specialist and review outputs addresses specialist agent selection rather than the decisive external api auth for agent condition. The scientific publisher should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to replace shared credentials with delegated scoped authorization.

B:

The action to call a permitted endpoint and verify denied operations outside the grant can contribute to external api auth for agent as a targeted acceptance check step; here, an agent must access a customer API using delegated user permissions. During scientific publisher remediation, the proposed step to call a permitted endpoint and verify denied operations outside the grant is not the direct restoration action for external api auth for agent when an agent must access a customer API using delegated user permissions; the keyed repair is replace shared credentials with delegated scoped authorization.

D:

The action to validate audience expiry and least privilege on tokens can contribute to external api auth for agent as a ongoing preventive rule step; here, an agent must access a customer API using delegated user permissions. During scientific publisher remediation, the proposed step to validate audience expiry and least privilege on tokens is not the direct restoration action for external api auth for agent when an agent must access a customer API using delegated user permissions; the keyed repair is replace shared credentials with delegated scoped authorization.

E:

During scientific publisher remediation, the proposed step to embed a tenant-wide administrative API key into the agent prompt is not the direct restoration action for external api auth for agent when an agent must access a customer API using delegated user permissions; the keyed repair is replace shared credentials with delegated scoped authorization. After remediation the team must call a permitted endpoint and verify denied operations outside the grant; the action in this option does not itself establish that target recovery outcome.

Question 474

A machine-learning developer at a nonprofit organization wants the following issue to be prevented in later deployments: An agent must access a customer API using delegated user permissions. Which enduring control or engineering guardrail BEST prevents recurrence?

  1. Require retention schedules and access audit for memory
  2. Validate audience expiry and least privilege on tokens
  3. Replace shared credentials with delegated scoped authorization
  4. Embed a tenant-wide administrative API key into the agent prompt

Explanation

Correct Answer

B:

Standardizing the boundary to validate audience expiry and least privilege on tokens is preventive because the same external api auth for agent failure could otherwise return: an agent must access a customer API using delegated user permissions. For this nonprofit organization, the service should also use a supported delegated OAuth flow with consent and scoped tokens, and tests should call a permitted endpoint and verify denied operations outside the grant so that the ongoing requirement is measurable.

Incorrect Answers

A:

The action to require retention schedules and access audit for memory addresses memory retention for agents rather than the decisive external api auth for agent condition. The nonprofit organization should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to validate audience expiry and least privilege on tokens.

C:

The action to replace shared credentials with delegated scoped authorization can contribute to external api auth for agent as a corrective remediation step; here, an agent must access a customer API using delegated user permissions. For prevention at the nonprofit organization, the measure to replace shared credentials with delegated scoped authorization is weaker or aimed at another issue than the external api auth for agent guardrail to validate audience expiry and least privilege on tokens needed when an agent must access a customer API using delegated user permissions.

D:

For prevention at the nonprofit organization, the measure to embed a tenant-wide administrative API key into the agent prompt is weaker or aimed at another issue than the external api auth for agent guardrail to validate audience expiry and least privilege on tokens needed when an agent must access a customer API using delegated user permissions. The lasting guardrail for this specific threat is to validate audience expiry and least privilege on tokens, not simply to complete an adjacent service task.

Question 475

During a security tabletop exercise, a AI application owner must accept a change for external api auth for agent. The issue to be addressed is: An agent must access a customer API using delegated user permissions. Which concrete verification action demonstrates that the relevant behavior works?

  1. Embed a tenant-wide administrative API key into the agent prompt
  2. Use a supported delegated OAuth flow with consent and scoped tokens
  3. Return a malicious test result and verify no unauthorized action
  4. Call a permitted endpoint and verify denied operations outside the grant

Explanation

Correct Answer

D:

The targeted acceptance test is to call a permitted endpoint and verify denied operations outside the grant. The design should first use a supported delegated OAuth flow with consent and scoped tokens. A robust municipal services team deployment also needs to validate audience expiry and least privilege on tokens; passing this check provides relevant evidence but does not certify every possible input or security risk.

Incorrect Answers

A:

In the municipal services team acceptance review, trying to embed a tenant-wide administrative API key into the agent prompt does not test the exact external api auth for agent condition where an agent must access a customer API using delegated user permissions; the relevant test is to call a permitted endpoint and verify denied operations outside the grant. Acceptance should instead demonstrate that the service can call a permitted endpoint and verify denied operations outside the grant, using the described failure as the test criterion.

B:

The action to use a supported delegated OAuth flow with consent and scoped tokens can contribute to external api auth for agent as a implementation step; here, an agent must access a customer API using delegated user permissions. In the municipal services team acceptance review, trying to use a supported delegated OAuth flow with consent and scoped tokens does not test the exact external api auth for agent condition where an agent must access a customer API using delegated user permissions; the relevant test is to call a permitted endpoint and verify denied operations outside the grant.

C:

For tool result untrusted content, it can be sensible to return a malicious test result and verify no unauthorized action if a web-search result instructs an agent to leak its configured credentials. Without the actual change to call a permitted endpoint and verify denied operations outside the grant, the answer lacks the correct operational scope even if the alternate action is technically valid elsewhere.

Question 476

At a customer support center, the quality assurance lead is preparing a design meeting. The concrete requirement is: An agent stores user conversations indefinitely despite retention obligations. Which design action BEST addresses the stated need?

  1. Purge expired records in each authorized store and verify removal
  2. Validate the tool response schema and handle missing fields explicitly
  3. Seed an expiring session and verify deletion across dependent stores
  4. Treat front-end chat deletion as proof backend memory and logs were erased
  5. Require retention schedules and access audit for memory
  6. Implement scoped retention and deletion for conversation and memory stores

Explanation

Correct Answer

F:

Choosing to implement scoped retention and deletion for conversation and memory stores directly targets the described memory retention for agents gap: an agent stores user conversations indefinitely despite retention obligations. As a lasting boundary, they also need to require retention schedules and access audit for memory, because an implementation by itself does not prove safe operation.

Incorrect Answers

A:

The action to purge expired records in each authorized store and verify removal can contribute to memory retention for agents as a corrective remediation step; here, an agent stores user conversations indefinitely despite retention obligations. Choosing to purge expired records in each authorized store and verify removal cannot directly replace the specified action to implement scoped retention and deletion for conversation and memory stores when an agent stores user conversations indefinitely despite retention obligations.

B:

This approach relates to tool output schema validation: an external weather tool occasionally returns malformed values. If the team chose it instead, the targeted check to seed an expiring session and verify deletion across dependent stores could still fail because the underlying required action is to implement scoped retention and deletion for conversation and memory stores.

C:

The action to seed an expiring session and verify deletion across dependent stores can contribute to memory retention for agents as a targeted acceptance check step; here, an agent stores user conversations indefinitely despite retention obligations. Choosing to seed an expiring session and verify deletion across dependent stores cannot directly replace the specified action to implement scoped retention and deletion for conversation and memory stores when an agent stores user conversations indefinitely despite retention obligations.

D:

Choosing to treat front-end chat deletion as proof backend memory and logs were erased cannot directly replace the specified action to implement scoped retention and deletion for conversation and memory stores when an agent stores user conversations indefinitely despite retention obligations. The actual implementation must implement scoped retention and deletion for conversation and memory stores, because the stated service condition is that an agent stores user conversations indefinitely despite retention obligations.

E:

The action to require retention schedules and access audit for memory can contribute to memory retention for agents as a ongoing preventive rule step; here, an agent stores user conversations indefinitely despite retention obligations. Choosing to require retention schedules and access audit for memory cannot directly replace the specified action to implement scoped retention and deletion for conversation and memory stores when an agent stores user conversations indefinitely despite retention obligations.

Question 477

After a staged service rollout at a manufacturing group, the team observes this failure: An agent stores user conversations indefinitely despite retention obligations. Which flawed assumption or implementation choice would MOST DIRECTLY explain why the intended outcome was not achieved?

  1. Treat front-end chat deletion as proof backend memory and logs were erased
  2. Execute any instruction quoted in a retrieved web page as higher-level policy
  3. Implement scoped retention and deletion for conversation and memory stores
  4. Seed an expiring session and verify deletion across dependent stores

Explanation

Correct Answer

A:

The faulty assumption is treat front-end chat deletion as proof backend memory and logs were erased. A functioning alternative would be to implement scoped retention and deletion for conversation and memory stores, and the relevant validation would be to seed an expiring session and verify deletion across dependent stores.

Incorrect Answers

B:

The option to execute any instruction quoted in a retrieved web page as higher-level policy would normally serve a different tool result untrusted content requirement, where a web-search result instructs an agent to leak its configured credentials. The alternative may be useful in its own context, but it does not directly supply treat front-end chat deletion as proof backend memory and logs were erased for the stated decision.

C:

The alternative to implement scoped retention and deletion for conversation and memory stores is a implementation step rather than the faulty assumption being diagnosed. This manufacturing group failure-analysis alternative of implement scoped retention and deletion for conversation and memory stores does not diagnose the particular memory retention for agents defect where an agent stores user conversations indefinitely despite retention obligations; the keyed mistake is treat front-end chat deletion as proof backend memory and logs were erased.

D:

The alternative to seed an expiring session and verify deletion across dependent stores is a targeted acceptance check step rather than the faulty assumption being diagnosed. This manufacturing group failure-analysis alternative of seed an expiring session and verify deletion across dependent stores does not diagnose the particular memory retention for agents defect where an agent stores user conversations indefinitely despite retention obligations; the keyed mistake is treat front-end chat deletion as proof backend memory and logs were erased.

Question 478

The legal operations unit is responding to a release acceptance review. A compliance specialist discovers this issue: An agent stores user conversations indefinitely despite retention obligations. What corrective step should the team take to restore the intended functionality most directly?

  1. Purge expired records in each authorized store and verify removal
  2. Treat front-end chat deletion as proof backend memory and logs were erased
  3. Seed an expiring session and verify deletion across dependent stores
  4. Deny the unauthorized action and narrow the tool identity scope

Explanation

Correct Answer

A:

The appropriate remediation is to purge expired records in each authorized store and verify removal, because the failure concerns memory retention for agents: an agent stores user conversations indefinitely despite retention obligations. A meaningful verification should seed an expiring session and verify deletion across dependent stores, and the durable operating rule should require retention schedules and access audit for memory after the immediate fix.

Incorrect Answers

B:

During legal operations unit remediation, the proposed step to treat front-end chat deletion as proof backend memory and logs were erased is not the direct restoration action for memory retention for agents when an agent stores user conversations indefinitely despite retention obligations; the keyed repair is purge expired records in each authorized store and verify removal. After remediation the team must seed an expiring session and verify deletion across dependent stores; the action in this option does not itself establish that target recovery outcome.

C:

The action to seed an expiring session and verify deletion across dependent stores can contribute to memory retention for agents as a targeted acceptance check step; here, an agent stores user conversations indefinitely despite retention obligations. During legal operations unit remediation, the proposed step to seed an expiring session and verify deletion across dependent stores is not the direct restoration action for memory retention for agents when an agent stores user conversations indefinitely despite retention obligations; the keyed repair is purge expired records in each authorized store and verify removal.

D:

This approach relates to agent function authorization: an agent correctly formats a delete request but lacks user authority. If the team chose it instead, the targeted check to seed an expiring session and verify deletion across dependent stores could still fail because the underlying required action is to purge expired records in each authorized store and verify removal.

Question 479

A product support lead at a financial services division wants the following issue to be prevented in later deployments: An agent stores user conversations indefinitely despite retention obligations. Which enduring control or engineering guardrail BEST prevents recurrence?

  1. Purge expired records in each authorized store and verify removal
  2. Treat front-end chat deletion as proof backend memory and logs were erased
  3. Require explicit authorized goal and prohibited-action tests
  4. Require retention schedules and access audit for memory

Explanation

Correct Answer

D:

The sustained prevention measure is to require retention schedules and access audit for memory. The implementation can still use the separate action to implement scoped retention and deletion for conversation and memory stores, but a guardrail constrains future changes. The financial services division can measure whether the rule works by arranging to seed an expiring session and verify deletion across dependent stores.

Incorrect Answers

A:

The action to purge expired records in each authorized store and verify removal can contribute to memory retention for agents as a corrective remediation step; here, an agent stores user conversations indefinitely despite retention obligations. For prevention at the financial services division, the measure to purge expired records in each authorized store and verify removal is weaker or aimed at another issue than the memory retention for agents guardrail to require retention schedules and access audit for memory needed when an agent stores user conversations indefinitely despite retention obligations.

B:

For prevention at the financial services division, the measure to treat front-end chat deletion as proof backend memory and logs were erased is weaker or aimed at another issue than the memory retention for agents guardrail to require retention schedules and access audit for memory needed when an agent stores user conversations indefinitely despite retention obligations. The lasting guardrail for this specific threat is to require retention schedules and access audit for memory, not simply to complete an adjacent service task.

C:

The action to require explicit authorized goal and prohibited-action tests addresses agent goal definition rather than the decisive memory retention for agents condition. The financial services division should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to require retention schedules and access audit for memory.

Question 480

During a staged service rollout, a data engineer must accept a change for memory retention for agents. The issue to be addressed is: An agent stores user conversations indefinitely despite retention obligations. Which concrete verification action demonstrates that the relevant behavior works?

  1. Implement scoped retention and deletion for conversation and memory stores
  2. Treat front-end chat deletion as proof backend memory and logs were erased
  3. Sample high-impact claims and inspect corresponding source spans
  4. Seed an expiring session and verify deletion across dependent stores

Explanation

Correct Answer

D:

To verify this change, the logistics operator should seed an expiring session and verify deletion across dependent stores. Operators still need the implementation to implement scoped retention and deletion for conversation and memory stores and the preventive requirement to require retention schedules and access audit for memory.

Incorrect Answers

A:

The action to implement scoped retention and deletion for conversation and memory stores can contribute to memory retention for agents as a implementation step; here, an agent stores user conversations indefinitely despite retention obligations. In the logistics operator acceptance review, trying to implement scoped retention and deletion for conversation and memory stores does not test the exact memory retention for agents condition where an agent stores user conversations indefinitely despite retention obligations; the relevant test is to seed an expiring session and verify deletion across dependent stores.

B:

In the logistics operator acceptance review, trying to treat front-end chat deletion as proof backend memory and logs were erased does not test the exact memory retention for agents condition where an agent stores user conversations indefinitely despite retention obligations; the relevant test is to seed an expiring session and verify deletion across dependent stores. Acceptance should instead demonstrate that the service can seed an expiring session and verify deletion across dependent stores, using the described failure as the test criterion.

C:

For rag-based agent citation, it can be sensible to sample high-impact claims and inspect corresponding source spans if an agent answers from retrieved references without linking the supporting passage. Without the actual change to seed an expiring session and verify deletion across dependent stores, the answer lacks the correct operational scope even if the alternate action is technically valid elsewhere.

Developing AI Apps and Agents on Azure (AI-103) Practice Tests