The correct answer is A. Enable estimateFieldSourceAndConfidence . Azure Content Understanding document analyzers support an opt-in confidence and grounding capability for field extraction. Microsoft documentation states that to opt in for confidence and grounding, you set estimateFieldSourceAndConfidence
= true in the analyzer configuration, or configure estimateSourceAndConfidence = true for specific fields.
This enables each extracted field to include a confidence score and references back to the original document source location.
This directly satisfies both stakeholder requirements: source grounding allows users to verify where the extracted value came from in the scanned PDF, and the confidence score supports downstream automation rules, such as sending low-confidence fields to manual review. Microsoft's analyzer improvement guidance describes confidence scoring as a value between 0 and 1 and grounding as references or citations for extracted outputs to the original document content.
Generative extraction does not guarantee per-field confidence and source grounding. enableSegment is used for document segmentation, not confidence scoring. Labeled samples can improve extraction quality, but they do not by themselves enable confidence and grounding output. Reference topics: Content Understanding document analyzers, field extraction, confidence scoring, grounding, and RAG ingestion.

Explanation:
Box 1: AnalyzeTextOptions(text=comment)
To set up the request in your Python script, you must use AnalyzeTextOptions(text=comment), passing the text as a single string rather than a list.
Example:
Build the request options focusing on Text analysis
# You can optionally restrict analysis to specific categories
request_options = AnalyzeTextOptions(
text=user_comment,
categories=[TextCategory.SELF_HARM]
Box 2: client.analyze_text(request)
You must use client.analyze_text(request)
1. Send the request: Call client.analyze_text(request) to retrieve the multi-severity results.
2. Extract the self-harm result: Locate the self-harm categories from the response list.
3. Return the severity: Access the .severity attribute
Reference:
https://learn.microsoft.com/en-us/python/api/overview/azure/ai-contentsafety-readme

Foundry User is the least-privilege built-in role for Microsoft Foundry projects and grants the data- plane actions needed to call a project endpoint, run inference, and use agents. Microsoft recommends assigning the project's managed identity the Foundry User role on the Foundry resource.

The correct answer is A. Speech recognition requests will fall back to the most recent base model for the same locale . Microsoft's custom speech model lifecycle guidance states that when a model expires, it is no longer available for transcription. For the custom endpoint route, speech recognition requests fall back to the most recent base model for the same locale. The documentation also warns that recognition results might still be returned, but the transcription may no longer reflect the domain-specific adaptation of the custom model.
This distinguishes real-time custom endpoint behavior from batch transcription behavior. Batch transcription requests that specify an expired model fail with a 4xx error, but that is not the route described in this question.
The agent is using a custom endpoint for real-time recognition, so fallback to the latest base model is the expected behavior. The model is not automatically deleted merely because it expires, and it does not continue to use the expired custom model indefinitely. The operational recommendation is to update the endpoint's model before expiration by redeploying the endpoint with a newer custom model. Reference topics: Azure Speech custom speech model lifecycle, custom endpoints, model expiration, real-time speech recognition, and endpoint redeployment.

Correct:
* You add a reflection pass that regenerates the response if the required clauses are missing.
This is Self-Correction Strategy: A reflection pass allows an agent to evaluate its own initial output against specified constraints (e.g., checking for the presence of mandatory regulatory clauses). If the required text is missing, the agent triggers a programmatic self-correction or regeneration loop to include them before final delivery.
Incorrect:
* You increase the value of the max_tokens parameter.
Increasing the max_tokens parameter prevents the response from being cut off mid-sentence due to length constraints. However, it does not force the model's logic to explicitly include missing information that it chose to leave out earlier in the text.
* You increase the value of the temperature parameter.
Raising the temperature parameter increases randomness and creativity. For rigid compliance tasks like summarizing regulatory documents, higher temperature actually increases the risk of hallucination and omission.
* You run an evaluation flow that scores responses for completeness and blocks responses that fall below a defined threshold.
Evaluation Flow Block: Running an evaluation flow to score completeness and blocking bad responses identifies and stops low-quality outputs, but it does not fix or actively improve the response completeness. It simply filters failures out of the system.
Reference:
https://pub.towardsai.net/reflection-with-llm-how-to-make-ai-review-its-own-work-2db122fca1d8