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 3 Discussion

You have a chat app in a Microsoft Foundry project and an Azure AI Search vectorized index.You need to connect to the index to meet the following requirements:* Complex questions must retrieve information from multiple chunks.* Multi-turn conversations must influence retrieval planning.* Retrievals must run in parallel to reduce latency.Which retrieval approach should you use?
C) agentic Retrieval Augmented Generation (RAG)
A) classic Retrieval Augmented Generation (RAG)
B) chain of thought
D) iterative retrieval

Microsoft AI-103 Exam - Topic 2 Question 3 Discussion

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

You have a chat app in a Microsoft Foundry project and an Azure AI Search vectorized index.

You need to connect to the index to meet the following requirements:

* Complex questions must retrieve information from multiple chunks.

* Multi-turn conversations must influence retrieval planning.

* Retrievals must run in parallel to reduce latency.

Which retrieval approach should you use?

Show Suggested Answer Hide Answer
Suggested Answer: C

The correct answer is agentic Retrieval Augmented Generation (RAG) because the requirements describe the agentic retrieval pipeline in Azure AI Search. Agentic retrieval is designed for chat and copilot scenarios where a user's request can be complex, conversational, and dependent on prior turns. Azure AI Search agentic retrieval uses an LLM-assisted planning stage to break a complex request into focused subqueries, allowing the system to retrieve grounding information from multiple chunks rather than relying on a single query path. Microsoft's Azure AI Search guidance describes agentic retrieval as a multi-query pipeline for complex questions in chat and agent workflows, with subqueries that can include chat history for additional context.

This also satisfies the latency requirement because agentic retrieval runs the generated subqueries in parallel and then merges and reranks the best results for use by the generative model. Classic RAG is simpler and typically sends a single query to search, making it less suitable for multi-hop or conversational retrieval planning. Chain of thought is a reasoning technique, not an Azure AI Search retrieval approach, and iterative retrieval does not specifically provide the built-in query planning, conversation-aware retrieval, and parallel execution described here. Reference topics: Azure AI Search agentic retrieval, RAG with Azure AI Search, knowledge bases, query planning, and generative AI grounding.


Contribute your Thoughts:

0/2000 characters
Emerson
3 days ago
Wait, can multi-turn conversations really affect retrieval planning?
upvoted 0 times
...
Becky
8 days ago
A) classic RAG seems outdated for this use case.
upvoted 0 times
...
Moon
13 days ago
I think C) agentic RAG is the best fit here.
upvoted 0 times
...
Rodolfo
18 days ago
Chain of thought sounds familiar, but I can't recall if it really supports parallel retrievals like the question asks. I might lean towards classic RAG instead.
upvoted 0 times
...
Meaghan
23 days ago
I practiced a question similar to this, and I think iterative retrieval was mentioned as a way to improve response times, but I'm not confident it meets all the requirements here.
upvoted 0 times
...
Dyan
29 days ago
I feel like the agentic RAG might be the right choice since it can handle multi-turn conversations better, but I need to double-check the specifics.
upvoted 0 times
...
Tawna
1 month ago
I think I remember something about RAG being useful for retrieving information from multiple sources, but I'm not sure which version to choose.
upvoted 0 times
...

Save Cancel