The correct answer is D. Set the output_content_format=ContentFormat.MARKDOWN value . Azure Document Intelligence Layout API can return extracted document content in Markdown format, preserving semantic structure such as headings, paragraphs, sections, tables, and other layout elements. Microsoft's Document Intelligence layout guidance shows the Python SDK pattern for analyzing a document with the prebuilt-layout model and setting output_content_format=ContentFormat.MARKDOWN in the begin_analyze_document call. The Markdown output is returned in the top-level content section of the analysis result.
This minimizes development effort because the service produces structure-preserving Markdown directly, rather than requiring custom post-processing to reconstruct sections and table formatting from raw OCR spans. Microsoft's Markdown output documentation states that specifying Markdown output produces semantically structured content that maintains paragraphs, headings, tables, and other document elements in their proper hierarchy.
Option A only changes validation behavior and does not generate Markdown. Option B requests figures, not structured Markdown. Option C uses an incorrect parameter name; the documented SDK setting is output_content_format, not content. Reference topics: Azure Document Intelligence Layout API, Markdown output, PDF analysis, table extraction, and Foundry Tools document processing.

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

Agent1 requires memory because the business requirement explicitly states that the agent must retain conversation context and recall relevant information during future interactions. Microsoft Foundry Agent Service memory provides persistent knowledge that can be retained and retrieved across separate conversations, sessions, devices, and workflows. It can store meaningful information extracted from prior interactions, including user preferences, relevant facts, and summarized context, and then retrieve that information when personalizing later responses.
Short-term memory maintains context within the current conversation. Long-term memory supports continuity across future sessions, which directly addresses Contoso's requirement. Memory scopes should be associated with individual user identities so that one customer's stored information cannot be retrieved during another customer's interaction.
Guardrails enforce safety or behavioral restrictions but do not provide conversation recall. Tools enable the agent to access external systems, while instructions define the agent's role and operating boundaries. Neither tools nor instructions persist user-specific information across sessions.
The AI-103 Study Guide maps this requirement to choose appropriate memory, tool, and knowledge integration services and build agents that integrate retrieval, function calling, and conversation memory
.

Use vector search because it performs similarity matching based on semantic meaning rather than requiring literal keyword overlap. During ingestion, the product manuals should be divided into appropriately sized chunks. An embedding model converts each chunk into a numerical vector, which Azure AI Search stores in a vector field. At query time, the user's question is also converted into an embedding, and the service retrieves chunks whose vectors are closest to the query vector. Consequently, wording such as "reset the device to factory settings" can match manual content such as "restore the unit's original configuration," despite minimal lexical overlap. Azure AI Search explicitly defines vector fields as enabling similarity searches over mathematically represented content and supports this retrieval pattern for RAG applications.
Semantic ranking improves the ordering of an existing result set but is not the indexing mechanism that stores embeddings and performs nearest-neighbor similarity matching. Suggesters provide search-as-you-type functionality, while analyzers control tokenization and lexical processing for text fields.
This aligns with the AI-103 Study Guide objectives for implementing RAG, configuring Azure AI Search grounding, generating embeddings, and selecting vector retrieval techniques for agentic solutions.