The requirement is to extract structured fields, including nested values, from invoices by using a defined schema . In Azure Content Understanding, an analyzer is the processing unit that defines how content is analyzed, what information is extracted, and how the output is structured, including JSON fields.

Microsoft’s Content Understanding document solutions documentation states that Content Understanding uses customizable analyzers to extract essential information, fields, and relationships from documents and forms. Microsoft’s quickstart also shows invoice processing with the prebuilt-invoice analyzer to extract structured data from an invoice document.

Why the other options are incorrect:

A. transcription workflow in Azure Speech is for converting audio to text, not invoice field extraction.

B. OCR-only document processing can extract text but does not meet the requirement for structured fields and nested values by schema.

D. Azure AI Search is for indexing and querying content, not defining invoice extraction schemas.

Therefore, the correct answer is C. an analyzer in Azure Content Understanding in Foundry Tools .

The completed code is:

poller = client.begin_analyze(

analyzer_id="invoice",

input_url=url

)

result = poller.result()

Azure Content Understanding analysis uses a long-running operation pattern. The Python SDK returns a poller from begin_analyze(), and Microsoft documentation states that the SDK poller handles polling automatically when you call .result() .

Therefore, to retrieve the analysis results after processing completes, the correct option is:

result

The other options are incorrect because status checks operation state, wait waits without returning the final analysis object, and get_results is not the method shown for retrieving the begin_analyze() result in this code pattern.

The Microsoft responsible AI principle of inclusiveness means AI systems should be designed to empower and engage everyone, including people with different abilities, languages, and accessibility needs.

Therefore, designing the interface to support multiple languages and screen readers is an example of inclusiveness .

Why the other options are incorrect:

A. Provide explanations about how predictions are generated = Transparency

C. Evaluate model outputs across demographic groups to reduce bias = Fairness

D. Encrypt stored customer data and restrict access by using role-based controls = Privacy and security

When using the OpenAI Responses API and a vision-enabled model, you can include an image in a request by providing the image as a base64-encoded image data .

Azure OpenAI / Microsoft Foundry vision requests support image input as an input_image item. The image can be provided by URL or as base64-encoded image data in the request. Microsoft documentation for Azure OpenAI batch examples also lists Base64 encoded image and Image URL as supported input patterns for Responses API requests.

The other options are incorrect:

a CSV file attachment is not an image input format for vision analysis.

an MP4 video stream is video content, not an image format.

a shared access signature (SAS) token is only an access token for a protected resource; it is not the image data itself.

The requirement is to produce new product images based on written descriptions . This is an image generation workload, because the AI system is creating entirely new images from natural language prompts.

Why the other options are incorrect:

B. image analysis is used to examine and interpret existing images.

C. object detection is used to identify and locate objects within an existing image.

D. optical character recognition (OCR) is used to extract text from images or scanned documents.

Since the solution must generate new visual content from user-provided descriptions, the correct answer is:

A. image generation

Fairness

Privacy and security

Transparency

Reliability and safety

Comprehensive and Detailed Explanation with all Azure AI documents : =

Evaluating model outputs to ensure that decisions are NOT biased against specific demographic groups: Fairness

Microsoft’s responsible AI principle of fairness means AI systems should treat people fairly and avoid unfair bias across demographic groups.

Encrypting sensitive customer data and restricting system access to authorized personnel: Privacy and security

The privacy and security principle requires AI systems to protect personal and sensitive data and prevent unauthorized access.

Informing users when they are interacting with an AI system and explaining the system’s capabilities and limitations: Transparency

The transparency principle requires that people understand when they are interacting with AI and understand the system’s purpose, capabilities, and limitations.

Testing AI systems under different conditions to reduce unexpected failures: Reliability and safety

The reliability and safety principle means AI systems should operate reliably and safely, including through testing and validation under expected and unexpected conditions.

Microsoft’s Foundry Agent Service documentation states that tool_choice provides deterministic control over tool calling:

auto means the model decides whether to call tools.

required means the model must call one or more tools .

none means the model does not call tools.

Therefore:

A. auto = Incorrect, because the model may or may not call the Azure function.

B. none = Incorrect, because this prevents tool/function calls.

C. required = Correct, because it forces the agent to call a tool.

The Azure OpenAI function-calling documentation also confirms that tool_choice="auto" lets the model decide whether to call a function, while tool_choice="none" forces a user-facing response without a tool call.