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 19

Question 180

During a staged service rollout, a machine-learning developer must accept a change for search index health. The issue to be addressed is: A knowledge assistant gives old policy answers after nightly ingestion. Which concrete verification action demonstrates that the relevant behavior works?

  1. Assume an available search endpoint guarantees current indexed data
  2. Modify a test source and verify its latest passage becomes retrievable
  3. Submit a known sensitive test string and inspect who can retrieve telemetry
  4. Inspect indexer status document freshness and failed ingestion counts

Explanation

Correct Answer

B:

To verify this change, the large online retailer should modify a test source and verify its latest passage becomes retrievable. Operators still need the implementation to inspect indexer status document freshness and failed ingestion counts and the preventive requirement to alert on ingestion lag and reject stale high-risk policy evidence.

Incorrect Answers

A:

In the large online retailer acceptance review, trying to assume an available search endpoint guarantees current indexed data does not test the exact search index health condition where a knowledge assistant gives old policy answers after nightly ingestion; the relevant test is to modify a test source and verify its latest passage becomes retrievable. Acceptance should instead demonstrate that the service can modify a test source and verify its latest passage becomes retrievable, using the described failure as the test criterion.

C:

For private data telemetry, it can be sensible to submit a known sensitive test string and inspect who can retrieve telemetry if model traces risk capturing customer health details in plaintext. Without the actual change to modify a test source and verify its latest passage becomes retrievable, the answer lacks the correct operational scope even if the alternate action is technically valid elsewhere.

D:

The action to inspect indexer status document freshness and failed ingestion counts can contribute to search index health as a implementation step; here, a knowledge assistant gives old policy answers after nightly ingestion. In the large online retailer acceptance review, trying to inspect indexer status document freshness and failed ingestion counts does not test the exact search index health condition where a knowledge assistant gives old policy answers after nightly ingestion; the relevant test is to modify a test source and verify its latest passage becomes retrievable.

Question 181

At a financial services division, the AI application owner is preparing a data protection inspection. The concrete requirement is: A developer can unexpectedly edit all AI project resources. Which design action BEST addresses the stated need?

  1. Inspect inherited Azure role assignments and narrow write access to least-privilege scope
  2. Verify developers can deploy only permitted resources and cannot change unrelated ones
  3. Use distributed traces to separate model time from individual tool execution latency
  4. Assume application authentication automatically restricts administrator permissions

Explanation

Correct Answer

A:

The proposed implementation is to inspect inherited Azure role assignments and narrow write access to least-privilege scope; this matches the operational requirement that a developer can unexpectedly edit all AI project resources. The team can verify developers can deploy only permitted resources and cannot change unrelated ones. The team should also perform periodic privileged access reviews for AI project resources.

Incorrect Answers

B:

The action to verify developers can deploy only permitted resources and cannot change unrelated ones can contribute to azure role scope as a targeted acceptance check step; here, a developer can unexpectedly edit all AI project resources. Choosing to verify developers can deploy only permitted resources and cannot change unrelated ones cannot directly replace the specified action to inspect inherited Azure role assignments and narrow write access to least-privilege scope when a developer can unexpectedly edit all AI project resources.

C:

Choosing to use distributed traces to separate model time from individual tool execution latency would direct effort toward agent tool latency, whose characteristic issue is that an otherwise fast chatbot responds slowly after retrieving external data. The relevant corrective or preventive action here remains to inspect inherited Azure role assignments and narrow write access to least-privilege scope, with its own validation criteria.

D:

Choosing to assume application authentication automatically restricts administrator permissions cannot directly replace the specified action to inspect inherited Azure role assignments and narrow write access to least-privilege scope when a developer can unexpectedly edit all AI project resources. The actual implementation must inspect inherited Azure role assignments and narrow write access to least-privilege scope, because the stated service condition is that a developer can unexpectedly edit all AI project resources.

Question 182

After a quality regression test at a logistics operator, the team observes this failure: A developer can unexpectedly edit all AI project resources. Which flawed assumption or implementation choice would MOST DIRECTLY explain why the intended outcome was not achieved?

  1. Assume application authentication automatically restricts administrator permissions
  2. Inspect inherited Azure role assignments and narrow write access to least-privilege scope
  3. Verify developers can deploy only permitted resources and cannot change unrelated ones
  4. Assume citations prove factual support without checking cited text

Explanation

Correct Answer

A:

This design mistake is to assume application authentication automatically restricts administrator permissions; it conflicts with the actual azure role scope behavior needed when a developer can unexpectedly edit all AI project resources. The logistics operator should instead inspect inherited Azure role assignments and narrow write access to least-privilege scope, followed by a check to verify developers can deploy only permitted resources and cannot change unrelated ones.

Incorrect Answers

B:

The alternative to inspect inherited Azure role assignments and narrow write access to least-privilege scope is a implementation step rather than the faulty assumption being diagnosed. This logistics operator failure-analysis alternative of inspect inherited Azure role assignments and narrow write access to least-privilege scope does not diagnose the particular azure role scope defect where a developer can unexpectedly edit all AI project resources; the keyed mistake is assume application authentication automatically restricts administrator permissions.

C:

The alternative to verify developers can deploy only permitted resources and cannot change unrelated ones is a targeted acceptance check step rather than the faulty assumption being diagnosed. This logistics operator failure-analysis alternative of verify developers can deploy only permitted resources and cannot change unrelated ones does not diagnose the particular azure role scope defect where a developer can unexpectedly edit all AI project resources; the keyed mistake is assume application authentication automatically restricts administrator permissions.

D:

The option to assume citations prove factual support without checking cited text would normally serve a different grounding quality monitoring requirement, where a RAG bot returns fluent answers that cite irrelevant source passages. The alternative may be useful in its own context, but it does not directly supply assume application authentication automatically restricts administrator permissions for the stated decision.

Question 183

The energy cooperative is responding to a production incident. A AI platform engineer discovers this issue: A developer can unexpectedly edit all AI project resources. What corrective step should the team take to restore the intended functionality most directly?

  1. Verify developers can deploy only permitted resources and cannot change unrelated ones
  2. Assume application authentication automatically restricts administrator permissions
  3. Remove overbroad role grants and retest required developer workflows
  4. Raise suitable approved quota or reduce aggregate token demand

Explanation

Correct Answer

C:

The direct repair is to remove overbroad role grants and retest required developer workflows. Once the condition is corrected, the energy cooperative should verify developers can deploy only permitted resources and cannot change unrelated ones. To reduce recurrence, it should also perform periodic privileged access reviews for AI project resources; those steps provide different recovery and prevention functions.

Incorrect Answers

A:

The action to verify developers can deploy only permitted resources and cannot change unrelated ones can contribute to azure role scope as a targeted acceptance check step; here, a developer can unexpectedly edit all AI project resources. During energy cooperative remediation, the proposed step to verify developers can deploy only permitted resources and cannot change unrelated ones is not the direct restoration action for azure role scope when a developer can unexpectedly edit all AI project resources; the keyed repair is remove overbroad role grants and retest required developer workflows.

B:

During energy cooperative remediation, the proposed step to assume application authentication automatically restricts administrator permissions is not the direct restoration action for azure role scope when a developer can unexpectedly edit all AI project resources; the keyed repair is remove overbroad role grants and retest required developer workflows. After remediation the team must verify developers can deploy only permitted resources and cannot change unrelated ones; the action in this option does not itself establish that target recovery outcome.

D:

This approach relates to model request quota: a product launch drives higher token-per-minute demand than the configured quota. If the team chose it instead, the targeted check to verify developers can deploy only permitted resources and cannot change unrelated ones could still fail because the underlying required action is to remove overbroad role grants and retest required developer workflows.

Question 184

A compliance specialist at a industrial maintenance team wants the following issue to be prevented in later deployments: A developer can unexpectedly edit all AI project resources. Which enduring control or engineering guardrail BEST prevents recurrence?

  1. Remove overbroad role grants and retest required developer workflows
  2. Perform periodic privileged access reviews for AI project resources
  3. Define relevance and evidence-support thresholds with human audit samples
  4. Assume application authentication automatically restricts administrator permissions

Explanation

Correct Answer

B:

Standardizing the boundary to perform periodic privileged access reviews for AI project resources is preventive because the same azure role scope failure could otherwise return: a developer can unexpectedly edit all AI project resources. For this industrial maintenance team, the service should also inspect inherited Azure role assignments and narrow write access to least-privilege scope, and tests should verify developers can deploy only permitted resources and cannot change unrelated ones so that the ongoing requirement is measurable.

Incorrect Answers

A:

The action to remove overbroad role grants and retest required developer workflows can contribute to azure role scope as a corrective remediation step; here, a developer can unexpectedly edit all AI project resources. For prevention at the industrial maintenance team, the measure to remove overbroad role grants and retest required developer workflows is weaker or aimed at another issue than the azure role scope guardrail to perform periodic privileged access reviews for AI project resources needed when a developer can unexpectedly edit all AI project resources.

C:

The action to define relevance and evidence-support thresholds with human audit samples addresses grounding quality monitoring rather than the decisive azure role scope condition. The industrial maintenance team should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to perform periodic privileged access reviews for AI project resources.

D:

For prevention at the industrial maintenance team, the measure to assume application authentication automatically restricts administrator permissions is weaker or aimed at another issue than the azure role scope guardrail to perform periodic privileged access reviews for AI project resources needed when a developer can unexpectedly edit all AI project resources. The lasting guardrail for this specific threat is to perform periodic privileged access reviews for AI project resources, not simply to complete an adjacent service task.

Question 185

During a quality regression test, a product support lead must accept a change for azure role scope. The issue to be addressed is: A developer can unexpectedly edit all AI project resources. Which concrete verification action demonstrates that the relevant behavior works?

  1. Modify a test source and verify its latest passage becomes retrievable
  2. Assume application authentication automatically restricts administrator permissions
  3. Inspect inherited Azure role assignments and narrow write access to least-privilege scope
  4. Verify developers can deploy only permitted resources and cannot change unrelated ones

Explanation

Correct Answer

D:

The targeted acceptance test is to verify developers can deploy only permitted resources and cannot change unrelated ones. The design should first inspect inherited Azure role assignments and narrow write access to least-privilege scope. A robust research university deployment also needs to perform periodic privileged access reviews for AI project resources; passing this check provides relevant evidence but does not certify every possible input or security risk.

Incorrect Answers

A:

For search index health, it can be sensible to modify a test source and verify its latest passage becomes retrievable if a knowledge assistant gives old policy answers after nightly ingestion. Without the actual change to verify developers can deploy only permitted resources and cannot change unrelated ones, the answer lacks the correct operational scope even if the alternate action is technically valid elsewhere.

B:

In the research university acceptance review, trying to assume application authentication automatically restricts administrator permissions does not test the exact azure role scope condition where a developer can unexpectedly edit all AI project resources; the relevant test is to verify developers can deploy only permitted resources and cannot change unrelated ones. Acceptance should instead demonstrate that the service can verify developers can deploy only permitted resources and cannot change unrelated ones, using the described failure as the test criterion.

C:

The action to inspect inherited Azure role assignments and narrow write access to least-privilege scope can contribute to azure role scope as a implementation step; here, a developer can unexpectedly edit all AI project resources. In the research university acceptance review, trying to inspect inherited Azure role assignments and narrow write access to least-privilege scope does not test the exact azure role scope condition where a developer can unexpectedly edit all AI project resources; the relevant test is to verify developers can deploy only permitted resources and cannot change unrelated ones.

Question 186

A data engineer at a large online retailer is conducting a regional deployment concerning data-connector permissions. The observed problem is: An agent can read documents from projects it was never assigned. Which TWO actions together represent the needed implementation AND a durable preventive safeguard? (Select TWO answers.)

  1. Ask an agent to retrieve forbidden document IDs and confirm access is blocked
  2. Restrict retrieval connector data-plane permissions to authorized corpora
  3. Reuse a tenant-wide reader role for every agent knowledge source
  4. Test cross-project denial and log knowledge-source permission changes
  5. Treat retrieved text as untrusted content and evaluate prompt-injection resistance

Explanation

Correct Answers

B:

Choosing to restrict retrieval connector data-plane permissions to authorized corpora directly targets the described data-connector permissions gap: an agent can read documents from projects it was never assigned. As a lasting boundary, they also need to test cross-project denial and log knowledge-source permission changes, because an implementation by itself does not prove safe operation.

D:

Standardizing the boundary to test cross-project denial and log knowledge-source permission changes is preventive because the same data-connector permissions failure could otherwise return: an agent can read documents from projects it was never assigned. For this large online retailer, the service should also restrict retrieval connector data-plane permissions to authorized corpora, and tests should ask an agent to retrieve forbidden document IDs and confirm access is blocked so that the ongoing requirement is measurable.

Incorrect Answers

A:

The action to ask an agent to retrieve forbidden document IDs and confirm access is blocked can contribute to data-connector permissions as a targeted acceptance check step; here, an agent can read documents from projects it was never assigned. Choosing to ask an agent to retrieve forbidden document IDs and confirm access is blocked cannot directly replace the specified action to restrict retrieval connector data-plane permissions to authorized corpora when an agent can read documents from projects it was never assigned.

C:

Choosing to reuse a tenant-wide reader role for every agent knowledge source cannot directly replace the specified action to restrict retrieval connector data-plane permissions to authorized corpora when an agent can read documents from projects it was never assigned. The actual implementation must restrict retrieval connector data-plane permissions to authorized corpora, because the stated service condition is that an agent can read documents from projects it was never assigned.

E:

The option to treat retrieved text as untrusted content and evaluate prompt-injection resistance would normally serve a different grounding attack monitoring requirement, where a retrieved page contains instructions attempting to override an agent system policy. The alternative may be useful in its own context, but it does not directly supply restrict retrieval connector data-plane permissions to authorized corpora for the stated decision.

Question 187

After a architecture migration at a public library network, the team observes this failure: An agent can read documents from projects it was never assigned. Which flawed assumption or implementation choice would MOST DIRECTLY explain why the intended outcome was not achieved?

  1. Test cross-project denial and log knowledge-source permission changes
  2. Assume personal developer sign-in roles transfer to deployed managed identities
  3. Blame model decoding speed without observing external tool call durations
  4. Restrict retrieval connector data-plane permissions to authorized corpora
  5. Reuse a tenant-wide reader role for every agent knowledge source
  6. Ask an agent to retrieve forbidden document IDs and confirm access is blocked

Explanation

Correct Answer

E:

The faulty assumption is reuse a tenant-wide reader role for every agent knowledge source. A functioning alternative would be to restrict retrieval connector data-plane permissions to authorized corpora, and the relevant validation would be to ask an agent to retrieve forbidden document IDs and confirm access is blocked.

Incorrect Answers

A:

The alternative to test cross-project denial and log knowledge-source permission changes is a ongoing preventive rule step rather than the faulty assumption being diagnosed. This public library network failure-analysis alternative of test cross-project denial and log knowledge-source permission changes does not diagnose the particular data-connector permissions defect where an agent can read documents from projects it was never assigned; the keyed mistake is reuse a tenant-wide reader role for every agent knowledge source.

B:

The action to assume personal developer sign-in roles transfer to deployed managed identities addresses access token authorization rather than the decisive data-connector permissions condition. The public library network should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to reuse a tenant-wide reader role for every agent knowledge source.

C:

This approach relates to agent tool latency: an otherwise fast chatbot responds slowly after retrieving external data. If the team chose it instead, the targeted check to ask an agent to retrieve forbidden document IDs and confirm access is blocked could still fail because the underlying required action is to reuse a tenant-wide reader role for every agent knowledge source.

D:

The alternative to restrict retrieval connector data-plane permissions to authorized corpora is a implementation step rather than the faulty assumption being diagnosed. This public library network failure-analysis alternative of restrict retrieval connector data-plane permissions to authorized corpora does not diagnose the particular data-connector permissions defect where an agent can read documents from projects it was never assigned; the keyed mistake is reuse a tenant-wide reader role for every agent knowledge source.

F:

The alternative to ask an agent to retrieve forbidden document IDs and confirm access is blocked is a targeted acceptance check step rather than the faulty assumption being diagnosed. This public library network failure-analysis alternative of ask an agent to retrieve forbidden document IDs and confirm access is blocked does not diagnose the particular data-connector permissions defect where an agent can read documents from projects it was never assigned; the keyed mistake is reuse a tenant-wide reader role for every agent knowledge source.

Question 188

The software consultancy is responding to a operational readiness review. A cloud developer discovers this issue: An agent can read documents from projects it was never assigned. What corrective step should the team take to restore the intended functionality most directly?

  1. Revoke excess data grants and reindex through a properly scoped identity
  2. Ask an agent to retrieve forbidden document IDs and confirm access is blocked
  3. Mitigate capacity or dependency failures identified in the request trace
  4. Reuse a tenant-wide reader role for every agent knowledge source

Explanation

Correct Answer

A:

The appropriate remediation is to revoke excess data grants and reindex through a properly scoped identity, because the failure concerns data-connector permissions: an agent can read documents from projects it was never assigned. A meaningful verification should ask an agent to retrieve forbidden document IDs and confirm access is blocked, and the durable operating rule should test cross-project denial and log knowledge-source permission changes after the immediate fix.

Incorrect Answers

B:

The action to ask an agent to retrieve forbidden document IDs and confirm access is blocked can contribute to data-connector permissions as a targeted acceptance check step; here, an agent can read documents from projects it was never assigned. During software consultancy remediation, the proposed step to ask an agent to retrieve forbidden document IDs and confirm access is blocked is not the direct restoration action for data-connector permissions when an agent can read documents from projects it was never assigned; the keyed repair is revoke excess data grants and reindex through a properly scoped identity.

C:

This approach relates to deployment availability: a regional service has intermittent errors but its health endpoint reports green. If the team chose it instead, the targeted check to ask an agent to retrieve forbidden document IDs and confirm access is blocked could still fail because the underlying required action is to revoke excess data grants and reindex through a properly scoped identity.

D:

During software consultancy remediation, the proposed step to reuse a tenant-wide reader role for every agent knowledge source is not the direct restoration action for data-connector permissions when an agent can read documents from projects it was never assigned; the keyed repair is revoke excess data grants and reindex through a properly scoped identity. After remediation the team must ask an agent to retrieve forbidden document IDs and confirm access is blocked; the action in this option does not itself establish that target recovery outcome.

Question 189

A site reliability engineer at a regional hospital wants the following issue to be prevented in later deployments: An agent can read documents from projects it was never assigned. Which enduring control or engineering guardrail BEST prevents recurrence?

  1. Revoke excess data grants and reindex through a properly scoped identity
  2. Reuse a tenant-wide reader role for every agent knowledge source
  3. Set per-task token ceilings and alert on cost spikes
  4. Test cross-project denial and log knowledge-source permission changes

Explanation

Correct Answer

D:

The sustained prevention measure is to test cross-project denial and log knowledge-source permission changes. The implementation can still use the separate action to restrict retrieval connector data-plane permissions to authorized corpora, but a guardrail constrains future changes. The regional hospital can measure whether the rule works by arranging to ask an agent to retrieve forbidden document IDs and confirm access is blocked.

Incorrect Answers

A:

The action to revoke excess data grants and reindex through a properly scoped identity can contribute to data-connector permissions as a corrective remediation step; here, an agent can read documents from projects it was never assigned. For prevention at the regional hospital, the measure to revoke excess data grants and reindex through a properly scoped identity is weaker or aimed at another issue than the data-connector permissions guardrail to test cross-project denial and log knowledge-source permission changes needed when an agent can read documents from projects it was never assigned.

B:

For prevention at the regional hospital, the measure to reuse a tenant-wide reader role for every agent knowledge source is weaker or aimed at another issue than the data-connector permissions guardrail to test cross-project denial and log knowledge-source permission changes needed when an agent can read documents from projects it was never assigned. The lasting guardrail for this specific threat is to test cross-project denial and log knowledge-source permission changes, not simply to complete an adjacent service task.

C:

The action to set per-task token ceilings and alert on cost spikes addresses token cost anomaly rather than the decisive data-connector permissions condition. The regional hospital should not infer that fixing one adjacent AI service validates its unrelated workflow; the requested action is to test cross-project denial and log knowledge-source permission changes.

Question 190

During a architecture migration, a security engineer must accept a change for data-connector permissions. The issue to be addressed is: An agent can read documents from projects it was never assigned. Which concrete verification action demonstrates that the relevant behavior works?

  1. Reuse a tenant-wide reader role for every agent knowledge source
  2. Ask an agent to retrieve forbidden document IDs and confirm access is blocked
  3. Restrict retrieval connector data-plane permissions to authorized corpora
  4. Inspect a slow trace and identify the tool step consuming the delay

Explanation

Correct Answer

B:

To verify this change, the insurance platform should ask an agent to retrieve forbidden document IDs and confirm access is blocked. Operators still need the implementation to restrict retrieval connector data-plane permissions to authorized corpora and the preventive requirement to test cross-project denial and log knowledge-source permission changes.

Incorrect Answers

A:

In the insurance platform acceptance review, trying to reuse a tenant-wide reader role for every agent knowledge source does not test the exact data-connector permissions condition where an agent can read documents from projects it was never assigned; the relevant test is to ask an agent to retrieve forbidden document IDs and confirm access is blocked. Acceptance should instead demonstrate that the service can ask an agent to retrieve forbidden document IDs and confirm access is blocked, using the described failure as the test criterion.

C:

The action to restrict retrieval connector data-plane permissions to authorized corpora can contribute to data-connector permissions as a implementation step; here, an agent can read documents from projects it was never assigned. In the insurance platform acceptance review, trying to restrict retrieval connector data-plane permissions to authorized corpora does not test the exact data-connector permissions condition where an agent can read documents from projects it was never assigned; the relevant test is to ask an agent to retrieve forbidden document IDs and confirm access is blocked.

D:

For agent tool latency, it can be sensible to inspect a slow trace and identify the tool step consuming the delay if an otherwise fast chatbot responds slowly after retrieving external data. Without the actual change to ask an agent to retrieve forbidden document IDs and confirm access is blocked, 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