Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AI-103 Exam - Topic 2 Question 6 Discussion

You are planning a Microsoft Foundry project named Project1 that will contain multiple agents. Each agent will access the same Azure Al Search resource.You need to recommend a solution to centrally manage the Azure Al Search credentials within Project1. The solution must be implemented across all the agents.What should you recommend?
B) Add a connection to the Azure Al Search resource.
A) Enable role-based access control (RBAC) for the Azure Al Search resource.
C) Disable key-based access control on the Azure Al Search resource.
D) Create a managed private endpoint that connects to the Azure Al Search resource.

Microsoft AI-103 Exam - Topic 2 Question 6 Discussion

Actual exam question for Microsoft's AI-103 exam
Question #: 6
Topic #: 2
[All AI-103 Questions]

You are planning a Microsoft Foundry project named Project1 that will contain multiple agents. Each agent will access the same Azure Al Search resource.

You need to recommend a solution to centrally manage the Azure Al Search credentials within Project1. The solution must be implemented across all the agents.

What should you recommend?

Show Suggested Answer Hide Answer
Suggested Answer: B

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.


Contribute your Thoughts:

0/2000 characters
Izetta
3 days ago
Wait, can you really manage multiple agents with just RBAC?
upvoted 0 times
...
Tiffiny
8 days ago
Definitely agree, RBAC keeps things secure!
upvoted 0 times
...
Lenna
13 days ago
I think enabling RBAC is the best way to manage credentials.
upvoted 0 times
...
Celestina
18 days ago
Creating a managed private endpoint sounds familiar, but I’m not sure how it would help with credential management across multiple agents.
upvoted 0 times
...
Sabine
23 days ago
I’m a bit confused about disabling key-based access control. Wouldn’t that limit access instead of managing it?
upvoted 0 times
...
Patria
29 days ago
I remember practicing a question about managing credentials, and I feel like adding a connection might just be a temporary fix rather than a centralized solution.
upvoted 0 times
...
Elliot
1 month ago
I think enabling RBAC could be the right approach since it allows for centralized management of permissions, but I'm not entirely sure if it's the best fit for this scenario.
upvoted 0 times
...

Save Cancel