Microsoft AI-103 Practice Test 74 - Prepaway
Practice Exams:

Pass Microsoft AI-103 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$89.99 $98.99

AI-103 Premium ETE File


  • Premium File 187 Questions & Answers. Last Update: Nov 15, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-103 Practice Test 74

Question 730

Production requirement: A multinational support desk extracts customer IDs and amounts from mixed French and English complaints. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Inspect records that explain the affected process, then check the result described in this case: A multinational support desk extracts customer IDs and amounts from mixed French and English complaints
  2. Fill missing customer account IDs with plausible values inferred from sentiment
  3. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text
  4. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests
  5. Use the document sentiment label as a substitute for exact named entities

Explanation

Correct Answer

B:

“Fill missing customer account IDs with plausible values inferred from sentiment” would violate the requirement. The appropriate control instead is to use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

E:

“Use the document sentiment label as a substitute for exact named entities” would violate the requirement.

Incorrect Answers

A:

“Inspect records that explain the affected process, then check the result described in this case: A multinational support desk extracts customer IDs and amounts from mixed French and English complaints” adds a relevant safeguard or verification step rather than weakening the solution.

C:

“Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text” is the controlled implementation, not an unsafe workaround.

D:

“Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests” is the required outcome of a working control, not an action that weakens it. Confirm that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Question 731

A team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. Which design decision is justified by the failure and the required outcome?

  1. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters
  2. Treat all currencies and dates as the same locale
  3. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text
  4. Translate legal notices without testing locale-specific negation and date phrasing

Explanation

Correct Answer

C:

Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Confirm that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

A:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a city service center needs sentiment trends while keeping exact street names” does not implement the control that the facts call for. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

B:

“Treat all currencies and dates as the same locale” does not implement the control that the facts call for. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

D:

“Translate legal notices without testing locale-specific negation and date phrasing” would not meet the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

Question 732

Situation: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. Which underlying technical principle explains the recommended implementation?

  1. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts
  2. The most powerful or least restricted model is always the safest choice regardless of task conditions
  3. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  4. The fact that the team started work is enough to prove correctness for this exact case: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters

Explanation

Correct Answer

A:

Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

Incorrect Answers

B:

“The most powerful or least restricted model is always the safest choice regardless of task conditions” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. The implementation must use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

C:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

D:

“The fact that the team started work is enough to prove correctness for this exact case: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. The implementation must use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

Question 733

Architecture case: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. What observable acceptance condition should be required before closing the task?

  1. The operator reports success without reproducing the observed behavior: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters
  2. The team closes a change ticket without replaying a representative positive and negative test
  3. A project dashboard remains green, although the affected request, output and permissions were not checked
  4. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests

Explanation

Correct Answer

D:

Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests. If this test fails, compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples.

Incorrect Answers

A:

“The operator reports success without reproducing the observed behavior: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters” alone does not establish all the required behavior. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

B:

Because a team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

C:

Because a team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters, “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

Question 734

Production requirement: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. Which first investigation is more useful than an unrelated health indicator?

  1. Assume the general service is at fault without checking the affected operation in this case: a city service center needs sentiment trends while keeping exact street names and case numbers from resident letters
  2. Read only the broad service-health summary and skip actual workload evidence
  3. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples
  4. Restart every affected component before collecting request or tool traces

Explanation

Correct Answer

C:

Because a team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters, compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

A:

“Assume the general service is at fault without checking the affected operation in this case: a city service center needs sentiment trends while keeping exact street names” would not meet the requirement. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

B:

Because a team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters, “Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

D:

A team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. “Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

Question 735

A team is investigating this task: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters. Which TWO actions could conceal a serious failure while appearing faster? Select TWO answers.

  1. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests
  2. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text
  3. Inspect records that explain the affected process, then check the result described in this case: A city service center needs sentiment trends while keeping exact street names and case numbers from resident letters
  4. Use the document sentiment label as a substitute for exact named entities
  5. Fill missing customer account IDs with plausible values inferred from sentiment

Explanation

Correct Answer

D:

“Use the document sentiment label as a substitute for exact named entities” would violate the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

E:

“Fill missing customer account IDs with plausible values inferred from sentiment” would violate the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

Incorrect Answers

A:

“Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests” is the required outcome of a working control, not an action that weakens it. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

B:

“Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text” is the controlled implementation, not an unsafe workaround. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Confirm that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

C:

“Inspect records that explain the affected process, then check the result described in this case: A city service center needs sentiment trends while keeping exact street names” adds a relevant safeguard or verification step rather than weakening the solution. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Confirm that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Question 736

Situation: A retailer processes multilingual refund requests containing local currency formats and missing account fields. Which implementation best meets the requirement while honoring the stated constraints?

  1. Translate legal notices without testing locale-specific negation and date phrasing
  2. Treat all currencies and dates as the same locale
  3. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text
  4. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retailer processes multilingual refund requests containing local currency formats and missing account fields

Explanation

Correct Answer

C:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

A:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. “Translate legal notices without testing locale-specific negation and date phrasing” would not meet the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

B:

Because a retailer processes multilingual refund requests containing local currency formats and missing account fields, “Treat all currencies and dates as the same locale” does not implement the control that the facts call for. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

D:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retailer processes multilingual refund requests containing local currency formats” does not implement the control that the facts call for. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Instead, use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

Question 737

Architecture case: A retailer processes multilingual refund requests containing local currency formats and missing account fields. Which design boundary is most relevant to this decision?

  1. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts
  2. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  3. The most powerful or least restricted model is always the safest choice regardless of task conditions
  4. The fact that the team started work is enough to prove correctness for this exact case: a retailer processes multilingual refund requests containing local currency formats and missing account fields

Explanation

Correct Answer

A:

Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text. The decisive evidence is that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

B:

Because a retailer processes multilingual refund requests containing local currency formats and missing account fields, “Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. The implementation must use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

C:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. “The most powerful or least restricted model is always the safest choice regardless of task conditions” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. The implementation must use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text.

D:

“The fact that the team started work is enough to prove correctness for this exact case: a retailer processes multilingual refund requests containing local currency formats and missing account fields” does not fully explain the decisive technical boundary in this case. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

Question 738

Production requirement: A retailer processes multilingual refund requests containing local currency formats and missing account fields. Which evidence is strongest for proving this requirement was met?

  1. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests
  2. The operator reports success without reproducing the observed behavior: a retailer processes multilingual refund requests containing local currency formats and missing account fields
  3. The team closes a change ticket without replaying a representative positive and negative test
  4. A project dashboard remains green, although the affected request, output and permissions were not checked

Explanation

Correct Answer

A:

Because a retailer processes multilingual refund requests containing local currency formats and missing account fields, sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

B:

“The operator reports success without reproducing the observed behavior: a retailer processes multilingual refund requests containing local currency formats and missing account fields” alone does not establish all the required behavior. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

C:

Because a retailer processes multilingual refund requests containing local currency formats and missing account fields, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

D:

Because a retailer processes multilingual refund requests containing local currency formats and missing account fields, “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Question 739

A team is investigating this task: A retailer processes multilingual refund requests containing local currency formats and missing account fields. What targeted records should the responder inspect to distinguish configuration from runtime behavior?

  1. Restart every affected component before collecting request or tool traces
  2. Assume the general service is at fault without checking the affected operation in this case: a retailer processes multilingual refund requests containing local currency formats and missing account fields
  3. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples
  4. Read only the broad service-health summary and skip actual workload evidence

Explanation

Correct Answer

C:

Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

Incorrect Answers

A:

“Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

B:

“Assume the general service is at fault without checking the affected operation in this case: a retailer processes multilingual refund requests containing local currency formats and missing account fields” would not meet the requirement. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples.

D:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Compare input language detection, token/character spans, JSON schema failures, locale formats and human-reviewed translation examples.

Question 740

Situation: A retailer processes multilingual refund requests containing local currency formats and missing account fields. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests
  2. Fill missing customer account IDs with plausible values inferred from sentiment
  3. Inspect records that explain the affected process, then check the result described in this case: A retailer processes multilingual refund requests containing local currency formats and missing account fields
  4. Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text
  5. Use the document sentiment label as a substitute for exact named entities

Explanation

Correct Answer

B:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. “Fill missing customer account IDs with plausible values inferred from sentiment” would violate the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

E:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. “Use the document sentiment label as a substitute for exact named entities” would violate the requirement. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

Incorrect Answers

A:

A retailer processes multilingual refund requests containing local currency formats and missing account fields. “Entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests” is the required outcome of a working control, not an action that weakens it. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts. Confirm that entity fields retain the correct spans and locale, missing values are null, and bilingual tests preserve the meaning of the original requests.

C:

“Inspect records that explain the affected process, then check the result described in this case: A retailer processes multilingual refund requests containing local currency formats” adds a relevant safeguard or verification step rather than weakening the solution. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

D:

“Use task-specific structured extraction with schema validation, language-aware evaluation and explicit handling of missing or ambiguous text” is the controlled implementation, not an unsafe workaround. Sentiment, named-entity extraction and translation serve different information goals; ambiguous source text needs uncertainty rather than invented structured facts.

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