Microsoft AI-102 (Designing and Implementing a Microsoft Azure AI Solution) Practice Test 1

Question 1

Two similar feedback messages have markedly different sentiment confidence scores. A product owner treats both as equally certain. How should the application respond?

  1. Use an approved terminology customization or supported custom translation workflow
  2. Use entity extraction to verify named-entity categories instead of interpreting key phrases as entities
  3. Use metadata or application filtering to exclude entries that have expired
  4. Apply a confidence-aware review policy instead of relying on the winning sentiment label alone

Explanation

Correct Answer

D:

Sentiment confidence reflects model uncertainty; consistent predicted labels can require different actions when confidence diverges. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after applying a confidence-aware review policy instead of relying on the winning sentiment label alone.

Incorrect Answers

A:

Domain terminology requires deliberate control of translated terms; generic translation alone may vary proper names across documents in its own workflow, but that is a different correction from the present requirement to apply a confidence-aware review policy instead of relying on the winning sentiment label alone. The reported issue would remain.

B:

Although useful elsewhere in the multilingual customer-support portal, a salient phrase need not identify an entity; key-phrase output is not typed person or organization recognition; the present case is different and calls for the team to apply a confidence-aware review policy instead of relying on the winning sentiment label alone.

C:

That change addresses another failure mode: an answer can match the wording of a question while being no longer valid; date applicability must be enforced by the consuming workflow; it does not address this case, for which the relevant intervention is to apply a confidence-aware review policy instead of relying on the winning sentiment label alone.

Question 2

FAQ records include “valid until” dates and an obsolete answer is still returned to an employee. What retrieval rule is needed?

  1. Apply a confidence-aware review policy instead of relying on the winning sentiment label alone
  2. Use metadata or application filtering to exclude entries that have expired
  3. Use entity extraction to verify named-entity categories instead of interpreting key phrases as entities
  4. Use an approved terminology customization or supported custom translation workflow

Explanation

Correct Answer

B:

An answer can match the wording of a question while being no longer valid; date applicability must be enforced by the consuming workflow. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after using metadata or application filtering to exclude entries that have expired.

Incorrect Answers

A:

That change addresses another failure mode: sentiment confidence reflects model uncertainty; consistent predicted labels can require different actions when confidence diverges; it does not address this case, for which the relevant intervention is to use metadata or application filtering to exclude entries that have expired.

C:

Although useful elsewhere in the multilingual customer-support portal, a salient phrase need not identify an entity; key-phrase output is not typed person or organization recognition; the present case is different and calls for the team to use metadata or application filtering to exclude entries that have expired.

D:

Domain terminology requires deliberate control of translated terms; generic translation alone may vary proper names across documents in its own workflow, but that is a different correction from the present requirement to use metadata or application filtering to exclude entries that have expired. The reported issue would remain.

Question 3

A support organization receives complete PDF customer complaints with tables and page formatting. It must translate whole supported documents into the requested language while retaining the document structure as far as supported. Which Azure AI service should the team select?

  1. Use Azure AI Language sentiment analysis
  2. Use custom question answering in Azure AI Language
  3. Use Azure AI Translator
  4. Use Azure AI Language named entity recognition

Explanation

Correct Answer

C:

Translator renders source-language text in selected target languages and can detect source language where supported. For this multilingual customer-support portal, the intended evidence is that the resulting message is in the requested target language. It does not synthesize spoken audio or retrieve an FAQ answer by itself.

Incorrect Answers

A:

Sentiment analysis estimates positive, neutral, or negative polarity and can expose confidence scores for the submitted text; it may be used to categorize the overall emotional polarity of feedback in a multilingual customer-support portal, but the current requirement is instead to translate the text of support messages into another language. That separate capability does not prove that the resulting message is in the requested target language; It is not a substitute for extracting an organization's legal name or classifying a document into custom business categories, so selecting that alternative would not meet the stated acceptance check.

B:

Custom question answering matches user questions with answers drawn from configured knowledge sources, including alternate phrasing; it may be used to retrieve the best matching published FAQ answer in a multilingual customer-support portal, but the current requirement is instead to translate the text of support messages into another language. That separate capability does not prove that the resulting message is in the requested target language; It cannot replace general text translation or perform free-form image analysis, so selecting that alternative would not meet the stated acceptance check.

D:

Language named entity recognition identifies predefined entity types and their spans in text, allowing structured extraction without inventing a new taxonomy; it may be used to identify people, organizations, and locations mentioned in unstructured tickets in a multilingual customer-support portal, but the current requirement is instead to translate the text of support messages into another language. That separate capability does not prove that the resulting message is in the requested target language; It does not answer a ticket from a curated FAQ or detect the speaker's audio, so selecting that alternative would not meet the stated acceptance check.

Question 4

A team responsible for a multilingual customer-support portal needs to categorize the overall emotional polarity of feedback; the acceptance check is that the output provides sentiment labels and scores. Which capability should be selected?

  1. Use Azure AI Language named entity recognition
  2. Use Azure AI Language key phrase extraction
  3. Use custom question answering in Azure AI Language
  4. Use Azure AI Language sentiment analysis

Explanation

Correct Answer

D:

Sentiment analysis estimates positive, neutral, or negative polarity and can expose confidence scores for the submitted text. For this multilingual customer-support portal, the intended evidence is that the output provides sentiment labels and scores. It is not a substitute for extracting an organization's legal name or classifying a document into custom business categories.

Incorrect Answers

A:

Language named entity recognition identifies predefined entity types and their spans in text, allowing structured extraction without inventing a new taxonomy; it may be used to identify people, organizations, and locations mentioned in unstructured tickets in a multilingual customer-support portal, but the current requirement is instead to categorize the overall emotional polarity of feedback. That separate capability does not prove that the output provides sentiment labels and scores; It does not answer a ticket from a curated FAQ or detect the speaker's audio, so selecting that alternative would not meet the stated acceptance check.

B:

Key phrase extraction identifies salient terms and phrases in natural-language content without requiring user-defined entity labels; it may be used to return the most representative concepts from each review in a multilingual customer-support portal, but the current requirement is instead to categorize the overall emotional polarity of feedback. That separate capability does not prove that the output provides sentiment labels and scores; It does not produce an overall customer rating or guarantee that each phrase is a named entity, so selecting that alternative would not meet the stated acceptance check.

C:

Custom question answering matches user questions with answers drawn from configured knowledge sources, including alternate phrasing; it may be used to retrieve the best matching published FAQ answer in a multilingual customer-support portal, but the current requirement is instead to categorize the overall emotional polarity of feedback. That separate capability does not prove that the output provides sentiment labels and scores; It cannot replace general text translation or perform free-form image analysis, so selecting that alternative would not meet the stated acceptance check.

Question 5

A customer-support application submits English and Japanese tickets to key-phrase extraction but incorrectly labels every document as English. The Japanese results are unreliable. Which implementation change should the developer make?

  1. Combine Japanese and English tickets into one long English-labeled document
  2. Increase the number of desired result phrases without changing the document language
  3. Force every input to use the English language identifier for consistent indexing
  4. Send each supported document with its appropriate language identifier

Explanation

Correct Answer

D:

Key-phrase extraction processes text according to its supported document language. Supplying the correct source-language identifier prevents the service from interpreting Japanese tokens with an incorrect English locale; validate language support for the configured model and API version.

Incorrect Answers

A:

Concatenating separate-language tickets removes useful per-document boundaries and does not make the Japanese text English. Each document should carry its actual supported source-language identifier before extraction.

B:

Changing output volume cannot repair incorrect language metadata supplied to text analytics. The extractor still analyzes Japanese content under the English-language assumption and may return poor or empty phrases.

C:

A common language label does not translate input text. This would preserve the incorrect locale information responsible for the Japanese errors, even if downstream reporting groups all phrases into one index.

Question 6

In a multilingual customer-support portal, engineers must retrieve the best matching published FAQ answer. The expected evidence is that the system returns a known answer drawn from curated support content. Which implementation is the best match?

  1. Use Azure AI Translator
  2. Use Azure AI Language sentiment analysis
  3. Use custom question answering in Azure AI Language
  4. Use Azure AI Language key phrase extraction

Explanation

Correct Answer

C:

Custom question answering matches user questions with answers drawn from configured knowledge sources, including alternate phrasing. For this multilingual customer-support portal, the intended evidence is that the system returns a known answer drawn from curated support content. It cannot replace general text translation or perform free-form image analysis.

Incorrect Answers

A:

Translator renders source-language text in selected target languages and can detect source language where supported; it may be used to translate the text of support messages into another language in a multilingual customer-support portal, but the current requirement is instead to retrieve the best matching published FAQ answer. That separate capability does not prove that the system returns a known answer drawn from curated support content; It does not synthesize spoken audio or retrieve an FAQ answer by itself, so selecting that alternative would not meet the stated acceptance check.

B:

Sentiment analysis estimates positive, neutral, or negative polarity and can expose confidence scores for the submitted text; it may be used to categorize the overall emotional polarity of feedback in a multilingual customer-support portal, but the current requirement is instead to retrieve the best matching published FAQ answer. That separate capability does not prove that the system returns a known answer drawn from curated support content; It is not a substitute for extracting an organization's legal name or classifying a document into custom business categories, so selecting that alternative would not meet the stated acceptance check.

D:

Key phrase extraction identifies salient terms and phrases in natural-language content without requiring user-defined entity labels; it may be used to return the most representative concepts from each review in a multilingual customer-support portal, but the current requirement is instead to retrieve the best matching published FAQ answer. That separate capability does not prove that the system returns a known answer drawn from curated support content; It does not produce an overall customer rating or guarantee that each phrase is a named entity, so selecting that alternative would not meet the stated acceptance check.

Question 7

A ticket contains “Paris” and a reviewer assumes the entity result also supplies authoritative latitude and longitude. What integration is actually required?

  1. Apply supported metadata filtering to restrict answers to the employee's division
  2. Resolve recognized place names against a separate geocoding or gazetteer source
  3. Validate the requested target locale against the Translator language list
  4. Normalize and group synonymous extracted key phrases for cross-ticket reporting

Explanation

Correct Answer

B:

Named entity recognition extracts and categorizes mentions, but it does not independently validate a place name or supply authoritative geographic coordinates. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after resolving recognized place names against a separate geocoding or gazetteer source.

Incorrect Answers

A:

Question-answering metadata can constrain eligible knowledge-base entries before ranking; without scope, a plausible but wrong policy may win in its own workflow, but that is a different correction from the present requirement to resolve recognized place names against a separate geocoding or gazetteer source. The reported issue would remain.

C:

Although useful elsewhere in the multilingual customer-support portal, translation targets must be supported language codes; retries or key rotation cannot make an invalid target locale valid; the present case is different and calls for the team to resolve recognized place names against a separate geocoding or gazetteer source.

D:

That change addresses another failure mode: key-phrase extraction returns text phrases rather than a guaranteed canonical taxonomy; normalization is an application-level reporting choice; it does not address this case, for which the relevant intervention is to resolve recognized place names against a separate geocoding or gazetteer source.

Question 8

A customer submits HTML-formatted help text for translation, but raw text processing destroys links and formatting. Which Translator request control should be used?

  1. Apply a suitable answer confidence threshold and return an approved no-match response
  2. Set the supported text format to HTML and validate the returned markup
  3. Aggregate and normalize extracted key phrases within supported language cohorts before cross-language comparison
  4. Use sentence-level spans or offsets when available to align negative classifications with the source text

Explanation

Correct Answer

B:

Translator text translation supports an HTML input mode for supported text; treating markup as ordinary plain text risks altering tags. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after setting the supported text format to HTML and validate the returned markup.

Incorrect Answers

A:

That change addresses another failure mode: curated question answering can return ranked candidates, but uncertain matches should not be presented as verified policy statements; it does not address this case, for which the relevant intervention is to set the supported text format to HTML and validate the returned markup.

C:

Key phrase boundaries and wording differ across languages; cross-language dashboards need deliberate translation or normalization before combining concepts in its own workflow, but that is a different correction from the present requirement to set the supported text format to HTML and validate the returned markup. The reported issue would remain.

D:

Although useful elsewhere in the multilingual customer-support portal, document-level sentiment does not identify where individual evaluations occur; span metadata supports localized UI highlighting; the present case is different and calls for the team to set the supported text format to HTML and validate the returned markup.

Question 9

The assistant sometimes returns the holiday policy for another division although both divisions have an entry. What runtime control should be considered?

  1. Apply supported metadata filtering to restrict answers to the employee's division
  2. Validate the requested target locale against the Translator language list
  3. Handle neutral and mixed sentiment explicitly and consider the returned confidence values
  4. Normalize and group synonymous extracted key phrases for cross-ticket reporting

Explanation

Correct Answer

A:

Question-answering metadata can constrain eligible knowledge-base entries before ranking; without scope, a plausible but wrong policy may win. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after applying supported metadata filtering to restrict answers to the employee's division.

Incorrect Answers

B:

Translation targets must be supported language codes; retries or key rotation cannot make an invalid target locale valid in its own workflow, but that is a different correction from the present requirement to apply supported metadata filtering to restrict answers to the employee's division. The reported issue would remain.

C:

That change addresses another failure mode: sentiment results are not merely positive versus negative; treating neutral feedback as a complaint creates avoidable false escalations; it does not address this case, for which the relevant intervention is to apply supported metadata filtering to restrict answers to the employee's division.

D:

Although useful elsewhere in the multilingual customer-support portal, key-phrase extraction returns text phrases rather than a guaranteed canonical taxonomy; normalization is an application-level reporting choice; the present case is different and calls for the team to apply supported metadata filtering to restrict answers to the employee's division.

Question 10

A multilingual reporting team pools German and Japanese key phrases into one frequency chart and gets misleading rankings. What aggregation change improves interpretability?

  1. Aggregate and normalize extracted key phrases within supported language cohorts before cross-language comparison
  2. Use sentence-level spans or offsets when available to align negative classifications with the source text
  3. Apply a suitable answer confidence threshold and return an approved no-match response
  4. Match the entity offsets' string-index convention to the client's text-indexing convention

Explanation

Correct Answer

A:

Key phrase boundaries and wording differ across languages; cross-language dashboards need deliberate translation or normalization before combining concepts. In the multilingual customer-support portal, confirm the fix by retesting the affected behavior after aggregating and normalize extracted key phrases within supported language cohorts before cross-language comparison.

Incorrect Answers

B:

That change addresses another failure mode: document-level sentiment does not identify where individual evaluations occur; span metadata supports localized UI highlighting; it does not address this case, for which the relevant intervention is to aggregate and normalize extracted key phrases within supported language cohorts before cross-language comparison.

C:

Although useful elsewhere in the multilingual customer-support portal, curated question answering can return ranked candidates, but uncertain matches should not be presented as verified policy statements; the present case is different and calls for the team to aggregate and normalize extracted key phrases within supported language cohorts before cross-language comparison.

D:

NER returns spans relative to an indexing convention; mismatched Unicode indexing, rather than a lack of entity recognition, causes misplaced highlights in its own workflow, but that is a different correction from the present requirement to aggregate and normalize extracted key phrases within supported language cohorts before cross-language comparison. The reported issue would remain.

Designing and Implementing a Microsoft Azure AI Solution (AI-102) Practice Tests