Explanation:
* Orchestration pattern: The sequential template that passes outputs node-by-node
* Approval checkpoints: Add a condition statement
Use the sequential orchestration template because the agents must execute in a fixed, predictable order.
PolicyWriter first generates the proposed policy update, and its output is then passed directly to RiskReviewer. Microsoft defines the sequential pattern as passing the result from one agent to the next in a defined order, making it appropriate for deterministic, multistage processing. The group-chat pattern would allow control to move dynamically between agents, which would reduce execution predictability.
After RiskReviewer returns a structured risk classification, add a condition statement that evaluates the result. The low-risk branch can proceed directly to the finalization action without requesting human input. A separate higher-risk branch can route to an approval step, such as an Ask a question node. Adding an Ask a question node without conditional branching would pause every workflow execution, including low-risk updates, and therefore would not satisfy the automation requirement. Microsoft Foundry workflows support if
/else branching and condition expressions for selecting the next action.
Study Guide alignment: implement orchestrated multi-agent solutions and build autonomous or semiautonomous workflows with safeguards and approval-flow controls .

Multiple-file task: Required over a single-file task. Your pipeline needs to reconcile data across two separate active transactional documents (the invoice and the purchase order) within a single analyzer request.
Pro mode is required instead of standard mode. Pro mode is specifically designed for advanced scenarios requiring multi-step reasoning, cross-file analysis, and validation against a knowledge base. Note that Pro mode currently supports classify and generate fields but does not support confidence scores for specific extracted fields.
Vendor contract files as reference data: Required. Because the vendor contracts are static compliance documents, they should be uploaded and treated as the analyzer's background knowledge base (reference data) to guide the validation logic.
Reference:
https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/concepts/standard-pro-modes

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.

You should set the input_fidelity parameter to "high" in this scenario.
In Microsoft Foundry (built on Azure AI Foundry), the input_fidelity parameter specifically dictates how strictly the image generation model adheres to the visual features, layout, and style of the source image.
Why "high" is the Correct Choice
Preserves Product Identity: Setting input_fidelity="high" ensures that critical branding details, logos, structures, and product contours are preserved exactly as they appear in the original photo.
Designed for E-commerce: Microsoft explicitly designed this setting for e-commerce, commercial marketing assets, and product photography to prevent the model from hallucinating or altering key product characteristics.
Model Support: This parameter is natively supported when configuring agent image generation tools (such as the ImageGenerationTool or ImageGenTool classes in the Foundry Agent Service) leveraging advanced models like GPT-image-1 or GPT-image-2.
Reference:
https://developers.openai.com/cookbook/examples/generate_images_with_high_input_fidelity

The correct answer is B. Modify the system message instructions . The case study states that Agent1 answers general questions about Contoso products and that the business requirement is for Agent1 to answer questions only about the products sold by Contoso . This is a behavioral boundary for the agent, so it should be implemented in the highest-priority instructions that define the agent's role, allowed scope, and refusal behavior.
Microsoft Foundry guidance states that a system message is used to steer model behavior, define the assistant' s role and boundaries, and add safety or quality constraints for the scenario. The system message should instruct Agent1 to answer only when the question concerns Contoso products, use the configured Contoso product documentation as grounding, and politely refuse or redirect questions about non-Contoso products.
Top-p sampling and temperature control randomness, not business-domain scope. Increasing temperature would make responses less deterministic. Few-shot examples can support desired behavior, but examples alone are weaker than explicit system-level instructions for defining operating boundaries. Reference topics:
system message design, prompt engineering, agent instructions, response constraints, and grounded generative AI behavior.