The correct answer is C because the requirement is a localized image edit: remove only the competitor logo while preserving the rest of the already generated image. Azure OpenAI image editing is designed for modifying existing images based on a text instruction, rather than regenerating the entire image from scratch.
Microsoft's Azure OpenAI image guidance states that the Image Edit API modifies existing images and requires an input image as part of the request. In a mask-based inpainting workflow, the mask identifies the exact region to change, allowing the model to replace only the logo area while retaining surrounding background, composition, lighting, and product content.
Increasing prompt guidance strength would affect adherence during generation, but it would not safely remove a specific logo from a completed image. Modifying the original prompt and regenerating may create a different image and does not guarantee preservation of the approved visual content. Rerunning with a different random seed also changes the image unpredictably and may introduce new brand or legal issues.
Mask-based inpainting is the minimal-change remediation method for post-generation brand cleanup.
Reference topics: Azure OpenAI image editing, inpainting, mask-guided edits, image generation governance, and computer vision solutions.

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.

The correct recommendation is B. Add a connection to the Azure AI Search resource . Microsoft Foundry project connections are used to centrally define access from a project to external resources, including Azure AI Search. The official connection guidance states that you can add a connection by selecting an external service such as Azure AI Search , choosing the resource, and selecting the authentication method for that resource. This creates a reusable project-level configuration rather than requiring each agent to store or duplicate search credentials independently.
For Foundry agents that use Azure AI Search, the Azure AI Search tool requires a project_connection_id, which is the resource ID of the project connection to Azure AI Search. This allows multiple agents to reference the same managed connection while using the configured endpoint and authentication settings consistently. RBAC may be part of a keyless authentication design, but it does not by itself create a centrally managed Foundry credential configuration. Disabling key-based access improves security posture but does not connect the agents. A managed private endpoint addresses network isolation, not credential centralization.
Reference topics: Microsoft Foundry project connections, Azure AI Search tool, project connection IDs, authentication, and agent grounding.

Set tool_choice to the named Grounding with Bing Search tool:
{ " type " : " bing_grounding " }
A named tool choice directs the model to invoke a specific tool rather than allowing it to select from all tools attached to the agent. Microsoft's SDK specification describes AgentsNamedToolChoice as the mechanism used to force the model to call a particular tool and lists bing_grounding and azure_ai_search as supported named tool types.
Grounding with Bing Search retrieves current public information from the internet and supplies the results to the model for response generation. Selecting bing_grounding therefore directs the run to the public web source rather than the private Azure AI Search index.
Setting tool_choice to " required " only establishes that a tool must be invoked; when multiple tools are available, it does not identify which one must be selected. " auto " delegates the decision entirely to the model. Selecting { " type " : " azure_ai_search " } would force retrieval from the private product- documentation index, which is the opposite of the requirement.
Study Guide alignment: configure agent tools, control tool selection, integrate web grounding, and connect agents to enterprise knowledge sources .

Ensuring that an incident manager agent can assign work to a DevOps agent in Azure AI Foundry is primarily achieved through a Connected Agents configuration. This setup allows a "main" agent to delegate tasks to "specialized" agents via natural language or defined function calls.
Key Implementation Steps
1. Configure Connected Agents
Within the Azure AI Foundry portal, you must register the DevOps agent as a "Connected Agent" of the incident manager.
2. Define Tool-Based Delegation
Use the ConnectedAgentToolDefinition in the Azure Python SDK or C# SDK to programmatically link them. This exposes the DevOps agent to the incident manager as a callable "tool".
3. Implement Handoff Orchestration Patterns
Choose an orchestration pattern that fits the triage-to-resolve workflow.
4. Manage Context and State
5. Enable Permissions and Roles
Reference:
https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/connected-agents