You should use Real-Time Speech-to-Text (Streaming STT) for this project.
Why Real-Time STT is Required
Low Latency: It transcribes audio within seconds.
Continuous Input: It processes live, ongoing audio streams.
Live Monitoring: Supervisors need immediate text to flag issues.
Reference:
https://learn.microsoft.com/en-us/azure/ai-services/speech-service/get-started-speech-to-text

Agentic retrieval in Azure AI Search uses a large language model to decompose a complex query into focused subqueries, runs them in parallel, semantically reranks each set of results, and merges them into a unified response, while taking conversation history into account. That is precisely the behaviour the scenario describes.

Explanation:
Deployment type: Standard
Version update policy: Once the current version expires
The correct deployment type is Standard . The case study specifies that Project1 is deployed in an EU Azure region and that model-processed data must remain within the EU. It also requires scalable, high-throughput generative AI workloads that dynamically handle variable customer support traffic without reserved throughput capacity. In Microsoft Foundry Models, Standard is a pay-per-token deployment type that processes data in a single Azure region, while Global Standard can process requests across regions and Global Provisioned uses reserved provisioned throughput. Microsoft's deployment-type guidance identifies Standard as single-region, pay-per-token, whereas Global Provisioned is cross-region with reserved capacity.
The correct version update policy is Once the current version expires . This keeps Agent1 on the selected model version during its supported lifecycle, which supports stable and consistent responses, but still preserves continuity by automatically moving to a supported replacement when the current version is retired.
Microsoft's model versioning guidance states that this policy updates only when the current model version expires, while upgrading when a new default is available changes the deployment sooner and opting out can cause the deployment to stop working after retirement. Reference topics: deployment types, regional data processing, model versioning, throughput capacity, and stable production deployments.

Correct:
* You configure a prompt shield for documents.
Prompt Shield for Documents: Highly Effective (Critical Defense)
How it helps: This shield specifically scans untrusted, third-party data inputs (like external documents or text extracted from uploaded images).
Mechanism: It evaluates the extracted image text before it is sent to the LLM to identify hidden jail
* You configure a prompt shield for user prompts.
Prompt Shield for User Prompts: Partially Effective (Defense in Depth)
How it helps: This shield targets direct jailbreak attempts written manually by the user in the text prompt field accompanying the upload.
Mechanism: It prevents the user from typing supporting instructions that prime the model to execute the hidden instructions found within the image.
* You configure image moderation to block unsafe content before processing the images.
Implementing rigorous image moderation is one of the most effective ways to secure multimodal AI systems against these threats. Moderation acts as a necessary gatekeeper, preventing malicious inputs from ever reaching the generative model.
Incorrect:
* You configure protected material detection.
Protected Material Detection: Ineffective for this Threat
Why it does not help: This feature is designed to scan model outputs to prevent the generation of copyrighted text, proprietary source code, or licensed imagery.
Limitation: It does not scan inputs for adversarial instructions and will not prevent a user from manipulating the model's logic.
Reference:
https://www.upgrad.com/blog/what-is-multimodal-ai/
https://learn.microsoft.com/en-us/azure/ai-services/content-safety/concepts/jailbreak-detection

The correct configuration is D. Enable mask_inpainting and supply both the input image and a mask indicating which part of the image to modify . The requirement is not to generate a new image, but to edit a specific region of an existing image while preserving the surrounding lighting, composition, and style. Azure OpenAI image editing in Microsoft Foundry supports modifying existing images by submitting an input image plus a prompt. For masked edits, the mask explicitly defines the part of the image the model is allowed to change; Microsoft states that the mask parameter defines the area to edit and must match the input image dimensions.
text_to_image would create a new image from a prompt and cannot guarantee preservation of the original image. image_variation generates related variants rather than targeted removals. image_to_image with high strength can regenerate broader areas and may alter unrelated visual details. Mask-based inpainting is the built-in editing control that limits modification to the selected region. Reference topics: Azure OpenAI image editing, mask inpainting, image edit API, input image, mask parameter, and computer vision image generation workflows.