The correct action is to change chunking to use semantic boundaries, splitting at clause or section headings. This approach preserves the natural meaning and context of each chunk, which is critical for legal document analysis in a RAG pattern. Page-level chunking often splits a clause across two pages, causing Azure Cognitive Search to retrieve incomplete or irrelevant information for the Azure OpenAI agent. By aligning chunks with the document’s logical structure, the vector search retrieves more coherent passages, directly improving retrieval accuracy. On the AI-102 exam, this scenario tests your understanding of chunking strategies within Azure Cognitive Search for RAG implementations, specifically how semantic chunking outperforms fixed-size or page-based methods for domain-specific content like legal contracts. A common trap is assuming smaller chunks always improve precision, but for legal documents, breaking at logical boundaries prevents context loss. Memory tip: think “clauses, not pages” — legal meaning lives in sections, not sheet edges.
AI-102 Implement agentic AI solutions Practice Question
This AI-102 practice question tests your understanding of implement agentic ai solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are building an agent for a legal firm that uses Azure OpenAI to analyze contracts. The agent must extract key clauses, identify risks, and summarize the contract. The agent uses a RAG pattern with Azure Cognitive Search as the vector database. After deployment, the agent sometimes returns irrelevant information or fails to find relevant clauses. You suspect the issue is with the chunking strategy. The contracts are large, typically 50-100 pages. Currently, you are chunking by page (each page is one chunk). You want to improve retrieval accuracy. Which action should you take?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change chunking to use semantic boundaries: split at clause or section headings.
Option D is correct because splitting contracts at semantic boundaries (clause or section headings) preserves the natural meaning and context of each chunk, which is critical for legal document analysis. Page-level chunking often splits a clause across two pages, causing the vector search to retrieve incomplete or irrelevant information. By aligning chunks with the document's logical structure, the RAG pattern retrieves more coherent and relevant passages for the Azure OpenAI agent to process.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Keep page-level chunking but add 50% overlap between chunks.
Why it's wrong here
Overlap helps but semantic coherence is more important.
✗
Use a different embedding model, such as text-embedding-3-large.
Why it's wrong here
Embedding model is not the root cause.
✗
Increase the chunk size to 5 pages per chunk and reduce overlap.
Why it's wrong here
Larger chunks may include irrelevant information.
✓
Change chunking to use semantic boundaries: split at clause or section headings.
Why this is correct
Semantic chunking improves relevance.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often focus on tuning parameters like overlap or chunk size, or switching embedding models, without recognizing that the fundamental issue is the chunking strategy's failure to respect the document's logical structure.
Detailed technical explanation
How to think about this question
In a RAG system using Azure Cognitive Search, the chunking strategy directly impacts the quality of vector embeddings and subsequent retrieval. Semantic chunking leverages document structure (e.g., headings, paragraphs) to create chunks that are self-contained and contextually complete, which improves cosine similarity scores between query embeddings and chunk embeddings. This approach is especially important for legal contracts where clauses are often cross-referenced and have specific legal meaning that can be lost if split across multiple chunks.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Implement agentic AI solutions — This question tests Implement agentic AI solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change chunking to use semantic boundaries: split at clause or section headings. — Option D is correct because splitting contracts at semantic boundaries (clause or section headings) preserves the natural meaning and context of each chunk, which is critical for legal document analysis. Page-level chunking often splits a clause across two pages, causing the vector search to retrieve incomplete or irrelevant information. By aligning chunks with the document's logical structure, the RAG pattern retrieves more coherent and relevant passages for the Azure OpenAI agent to process.
What should I do if I get this AI-102 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AI-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI-102 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.