Question 390
A user-acceptance test fails with the following observation: A literal translator preserves words but loses a required conversational form of address in a nuanced reply. What is the best correction?
- Translate with context and explicit tone requirements, then assess semantic fidelity
- Detect probable language and route to a supported pipeline with uncertainty handling
- Use a source-constrained summary prompt and validate coverage of required clauses
- Call the supported text translation service for each target locale and evaluate results
Explanation
Correct Answer
A:The fault signal is that a literal translator preserves words but loses a required conversational form of address in a nuanced reply; the targeted fix works because a multilingual model can use conversation context and style constraints; factual meaning and fluent tone need separate verification, restoring the ability to translate a conversational response while preserving a specified tone and contextual meaning.
Incorrect Answers
B:If the failing function were to handle incoming tickets whose language varies and is not declared by the sender, this change could be relevant because language detection supplies a routing signal to a suitable translation or analysis path; short or mixed-language texts need caution; the actual symptom is that a literal translator preserves words but loses a required conversational form of address in a nuanced reply, which calls for a different repair.
C:If the failing function were to condense a long policy document while preserving key exceptions and source support, this change could be relevant because grounded summarization uses supplied text as its evidence; a fluent summary must not introduce unsupported policy claims; the actual symptom is that a literal translator preserves words but loses a required conversational form of address in a nuanced reply, which calls for a different repair.
D:If the failing function were to translate stable product instructions into multiple supported target languages, this change could be relevant because translator provides text translation with language configuration; domain terminology still requires quality review; the actual symptom is that a literal translator preserves words but loses a required conversational form of address in a nuanced reply, which calls for a different repair.
Question 391
A Foundry-based application is being scoped for production. The non-negotiable task is to extract account ID, reason category, and decision text into fixed machine-consumable fields. Which implementation fits?
- Detect sensitive personal information before reuse
- Extract named entities from reports
- Use domain examples to disambiguate terms
- Request schema-constrained entity JSON
Explanation
Correct Answer
D:For the stated requirement to extract account ID, reason category, and decision text into fixed machine-consumable fields, structured output controls field names and types for downstream code; domain validation must still check allowed values; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to find private identifiers in user-provided text so they can be minimized or masked, PII recognition identifies supported sensitive spans for redaction or controlled processing; keeping the raw text is a separate policy decision; this does not directly meet the required outcome to extract account ID, reason category, and decision text into fixed machine-consumable fields.
B:For a system whose objective is to identify the people, organizations and places mentioned in incident narratives, named entity recognition identifies and classifies mentions in text; it does not by itself establish who authored the document or whether claims are true; this does not directly meet the required outcome to extract account ID, reason category, and decision text into fixed machine-consumable fields.
C:For a system whose objective is to extract a specialized compliance category when generic terminology is overloaded, task-specific definitions and examples help a model map ambiguous words to the intended domain meaning; this does not directly meet the required outcome to extract account ID, reason category, and decision text into fixed machine-consumable fields.
Question 392
The engineering change request is to generate a grounded document summary. What is the most direct acceptance criterion?
- Evaluate language identification accuracy on short and code-switched messages
- Evaluate correct action owners, due dates, and decision coverage on labeled calls
- Audit summaries for leakage of labeled private data while checking utility
- Measure factual consistency and exception recall against annotated document sections
Explanation
Correct Answer
D:The accepted change is to generate a grounded document summary; this evaluation checks whether it can condense a long policy document while preserving key exceptions and source support, since grounded summarization uses supplied text as its evidence; a fluent summary must not introduce unsupported policy claims.
Incorrect Answers
A:This test concerns the ability to handle incoming tickets whose language varies and is not declared by the sender, for which language detection supplies a routing signal to a suitable translation or analysis path; short or mixed-language texts need caution; it does not establish whether the change to generate a grounded document summary works for the current release.
B:This test concerns the ability to create a handoff note that preserves commitments and unresolved action items from a long support call, for which conversation summaries must capture speakers, decisions and next steps rather than merely extract generic keywords; it does not establish whether the change to generate a grounded document summary works for the current release.
C:This test concerns the ability to produce a useful incident synopsis without retaining unnecessary personal identifiers, for which a redaction stage can remove sensitive spans from the generated artifact; summarization alone does not guarantee privacy; it does not establish whether the change to generate a grounded document summary works for the current release.
Question 393
What test should engineers run after they detect sensitive personal information before reuse, rather than relying solely on a successful API response?
- Measure valid-schema rate and field-level extraction accuracy on labeled requests
- Evaluate correct action owners, due dates, and decision coverage on labeled calls
- Check sensitive-span recall and false-positive removal on realistic tickets
- Review class-wise F1 and routing errors on a representative labeled set
Explanation
Correct Answer
C:The accepted change is to detect sensitive personal information before reuse; this evaluation checks whether it can find private identifiers in user-provided text so they can be minimized or masked, since PII recognition identifies supported sensitive spans for redaction or controlled processing; keeping the raw text is a separate policy decision.
Incorrect Answers
A:This test concerns the ability to extract account ID, reason category, and decision text into fixed machine-consumable fields, for which structured output controls field names and types for downstream code; domain validation must still check allowed values; it does not establish whether the change to detect sensitive personal information before reuse works for the current release.
B:This test concerns the ability to create a handoff note that preserves commitments and unresolved action items from a long support call, for which conversation summaries must capture speakers, decisions and next steps rather than merely extract generic keywords; it does not establish whether the change to detect sensitive personal information before reuse works for the current release.
D:This test concerns the ability to route written requests into one of several approved service categories, for which a classifier assigns labels from an agreed taxonomy; named entity extraction alone does not decide message intent; it does not establish whether the change to detect sensitive personal information before reuse works for the current release.
Question 394
The team plans to request schema-constrained entity JSON. Which test provides the clearest evidence that this change works?
- Use human adequacy and terminology checks for representative translated instructions
- Check sensitive-span recall and false-positive removal on realistic tickets
- Review class-wise F1 and routing errors on a representative labeled set
- Measure valid-schema rate and field-level extraction accuracy on labeled requests
Explanation
Correct Answer
D:The accepted change is to request schema-constrained entity JSON; this evaluation checks whether it can extract account ID, reason category, and decision text into fixed machine-consumable fields, since structured output controls field names and types for downstream code; domain validation must still check allowed values.
Incorrect Answers
A:This test concerns the ability to translate stable product instructions into multiple supported target languages, for which translator provides text translation with language configuration; domain terminology still requires quality review; it does not establish whether the change to request schema-constrained entity JSON works for the current release.
B:This test concerns the ability to find private identifiers in user-provided text so they can be minimized or masked, for which PII recognition identifies supported sensitive spans for redaction or controlled processing; keeping the raw text is a separate policy decision; it does not establish whether the change to request schema-constrained entity JSON works for the current release.
C:This test concerns the ability to route written requests into one of several approved service categories, for which a classifier assigns labels from an agreed taxonomy; named entity extraction alone does not decide message intent; it does not establish whether the change to request schema-constrained entity JSON works for the current release.
Question 395
The acceptance criteria for a production AI solution require it to identify the people, organizations and places mentioned in incident narratives. Which design should be approved?
- Analyze sentiment in customer feedback
- Flag potentially harmful text in a moderation flow
- Extract named entities from reports
- Use opinion mining for aspect-level sentiment
Explanation
Correct Answer
C:For the stated requirement to identify the people, organizations and places mentioned in incident narratives, named entity recognition identifies and classifies mentions in text; it does not by itself establish who authored the document or whether claims are true; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to detect broadly positive, negative or neutral attitudes expressed in reviews, sentiment analysis estimates evaluative polarity in text; it should not be used as a precise diagnosis of the reviewer's emotions; this does not directly meet the required outcome to identify the people, organizations and places mentioned in incident narratives.
B:For a system whose objective is to review user messages for policy-relevant hate, violence or self-harm content before generation, text safety classification identifies supported content categories; moderation decisions depend on configured policy and context; this does not directly meet the required outcome to identify the people, organizations and places mentioned in incident narratives.
D:For a system whose objective is to identify that a reviewer likes delivery speed but dislikes package quality in one comment, opinion mining links sentiment to specific targets or aspects instead of reporting only a document-level score; this does not directly meet the required outcome to identify the people, organizations and places mentioned in incident narratives.
Question 396
An engineering team has a requirement to condense a long policy document while preserving key exceptions and source support. Which capability should be in the initial design?
- Classify messages against a defined taxonomy
- Generate a grounded document summary
- Redact private details from summarized text
- Summarize a conversation chronologically
- Apply terminology constraints to regulated translations
Explanation
Correct Answer
B:For the stated requirement to condense a long policy document while preserving key exceptions and source support, grounded summarization uses supplied text as its evidence; a fluent summary must not introduce unsupported policy claims; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to route written requests into one of several approved service categories, a classifier assigns labels from an agreed taxonomy; named entity extraction alone does not decide message intent; this does not directly meet the required outcome to condense a long policy document while preserving key exceptions and source support.
C:For a system whose objective is to produce a useful incident synopsis without retaining unnecessary personal identifiers, a redaction stage can remove sensitive spans from the generated artifact; summarization alone does not guarantee privacy; this does not directly meet the required outcome to condense a long policy document while preserving key exceptions and source support.
D:For a system whose objective is to create a handoff note that preserves commitments and unresolved action items from a long support call, conversation summaries must capture speakers, decisions and next steps rather than merely extract generic keywords; this does not directly meet the required outcome to condense a long policy document while preserving key exceptions and source support.
E:For a system whose objective is to preserve an approved glossary of medical or legal terms across translated responses, glossary or controlled terminology guidance reduces inconsistent domain-language choices; blind literal translation may be unsafe; this does not directly meet the required outcome to condense a long policy document while preserving key exceptions and source support.
Question 397
An architecture board is assessing 2 separate deliverables: (1) preserve an approved glossary of medical or legal terms across translated responses; and (2) handle incoming tickets whose language varies and is not declared by the sender. Which distinct implementations meet these deliverables? Choose TWO.
- Use LLM translation with contextual instructions
- Apply terminology constraints to regulated translations
- Detect source language before routing text
- Use Azure Translator for text localization
- Classify messages against a defined taxonomy
Explanation
Correct Answers
B:For the stated requirement to preserve an approved glossary of medical or legal terms across translated responses, glossary or controlled terminology guidance reduces inconsistent domain-language choices; blind literal translation may be unsafe; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to preserve an approved glossary of medical or legal terms across translated responses, while the other deliverables require separate capabilities.
C:For the stated requirement to handle incoming tickets whose language varies and is not declared by the sender, language detection supplies a routing signal to a suitable translation or analysis path; short or mixed-language texts need caution; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to handle incoming tickets whose language varies and is not declared by the sender, while the other deliverables require separate capabilities.
Incorrect Answers
A:For a system whose objective is to translate a conversational response while preserving a specified tone and contextual meaning, a multilingual model can use conversation context and style constraints; factual meaning and fluent tone need separate verification; this does not directly meet the required outcome to preserve an approved glossary of medical or legal terms across translated responses.
D:For a system whose objective is to translate stable product instructions into multiple supported target languages, translator provides text translation with language configuration; domain terminology still requires quality review; this does not directly meet the required outcome to preserve an approved glossary of medical or legal terms across translated responses.
E:For a system whose objective is to route written requests into one of several approved service categories, a classifier assigns labels from an agreed taxonomy; named entity extraction alone does not decide message intent; this does not directly meet the required outcome to preserve an approved glossary of medical or legal terms across translated responses.
Question 398
A cloud engineering team must find private identifiers in user-provided text so they can be minimized or masked. What is the most appropriate Azure AI implementation?
- Classify messages against a defined taxonomy
- Request schema-constrained entity JSON
- Detect source language before routing text
- Detect sensitive personal information before reuse
Explanation
Correct Answer
D:For the stated requirement to find private identifiers in user-provided text so they can be minimized or masked, PII recognition identifies supported sensitive spans for redaction or controlled processing; keeping the raw text is a separate policy decision; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to route written requests into one of several approved service categories, a classifier assigns labels from an agreed taxonomy; named entity extraction alone does not decide message intent; this does not directly meet the required outcome to find private identifiers in user-provided text so they can be minimized or masked.
B:For a system whose objective is to extract account ID, reason category, and decision text into fixed machine-consumable fields, structured output controls field names and types for downstream code; domain validation must still check allowed values; this does not directly meet the required outcome to find private identifiers in user-provided text so they can be minimized or masked.
C:For a system whose objective is to handle incoming tickets whose language varies and is not declared by the sender, language detection supplies a routing signal to a suitable translation or analysis path; short or mixed-language texts need caution; this does not directly meet the required outcome to find private identifiers in user-provided text so they can be minimized or masked.
Question 399
An engineer receives this incident report: An executive summary omits the exception that changes the policy's eligibility rule. What should be changed?
- Use a source-constrained summary prompt and validate coverage of required clauses
- Translate with context and explicit tone requirements, then assess semantic fidelity
- Identify sensitive spans and sanitize source and output under the retention policy
- Apply supported text content-safety checks and enforce category-specific handling
Explanation
Correct Answer
A:The fault signal is that an executive summary omits the exception that changes the policy's eligibility rule; the targeted fix works because grounded summarization uses supplied text as its evidence; a fluent summary must not introduce unsupported policy claims, restoring the ability to condense a long policy document while preserving key exceptions and source support.
Incorrect Answers
B:If the failing function were to translate a conversational response while preserving a specified tone and contextual meaning, this change could be relevant because a multilingual model can use conversation context and style constraints; factual meaning and fluent tone need separate verification; the actual symptom is that an executive summary omits the exception that changes the policy's eligibility rule, which calls for a different repair.
C:If the failing function were to produce a useful incident synopsis without retaining unnecessary personal identifiers, this change could be relevant because a redaction stage can remove sensitive spans from the generated artifact; summarization alone does not guarantee privacy; the actual symptom is that an executive summary omits the exception that changes the policy's eligibility rule, which calls for a different repair.
D:If the failing function were to review user messages for policy-relevant hate, violence or self-harm content before generation, this change could be relevant because text safety classification identifies supported content categories; moderation decisions depend on configured policy and context; the actual symptom is that an executive summary omits the exception that changes the policy's eligibility rule, which calls for a different repair.
Question 400
What test should engineers run after they use LLM translation with contextual instructions, rather than relying solely on a successful API response?
- Measure unsafe-content recall and benign-request false-block rate
- Compare meaning preservation and style adherence using bilingual human review
- Evaluate language identification accuracy on short and code-switched messages
- Measure terminology consistency and reviewer corrections across languages
Explanation
Correct Answer
B:The accepted change is to use LLM translation with contextual instructions; this evaluation checks whether it can translate a conversational response while preserving a specified tone and contextual meaning, since a multilingual model can use conversation context and style constraints; factual meaning and fluent tone need separate verification.
Incorrect Answers
A:This test concerns the ability to review user messages for policy-relevant hate, violence or self-harm content before generation, for which text safety classification identifies supported content categories; moderation decisions depend on configured policy and context; it does not establish whether the change to use LLM translation with contextual instructions works for the current release.
C:This test concerns the ability to handle incoming tickets whose language varies and is not declared by the sender, for which language detection supplies a routing signal to a suitable translation or analysis path; short or mixed-language texts need caution; it does not establish whether the change to use LLM translation with contextual instructions works for the current release.
D:This test concerns the ability to preserve an approved glossary of medical or legal terms across translated responses, for which glossary or controlled terminology guidance reduces inconsistent domain-language choices; blind literal translation may be unsafe; it does not establish whether the change to use LLM translation with contextual instructions works for the current release.