AIP-C01 · Question #44
A legal research company has a Retrieval Augmented Generation (RAG) application that uses Amazon Bedrock and Amazon OpenSearch Service. The application stores 768-dimensional vector embeddings for…
The correct answer is C. Update the chunking strategy to use semantic boundaries such as complete legal arguments. Option C directly addresses both retrieval relevance and performance scalability. Fixed token chunking breaks semantic continuity in legal texts, causing incomplete context retrieval and degraded response quality. By switching to semantic chunking--based on legal arguments…
Question
A legal research company has a Retrieval Augmented Generation (RAG) application that uses Amazon Bedrock and Amazon OpenSearch Service. The application stores 768-dimensional vector embeddings for 15 million legal documents, including statutes, court rulings, and case summaries. The company's current chunking strategy segments text into fixed-length blocks of 500 tokens. The current chunking strategy often splits contextually linked information such as legal arguments, court opinions, or statute references across separate chunks. Researchers report that generated outputs frequently omit key context or cite outdated legal information. Recent application logs show a 40% increase in response times. The p95 latency metric exceeds 2 seconds. The company expects storage needs for the application to grow from 90 GB to 360 GB within a year. The company needs a solution to improve retrieval relevance and system performance at scale. Which solution will meet these requirements?
Options
- AIncrease the embedding vector dimensionality from 768 to 4,096 without changing the existing
- BReplace dynamic retrieval with static, pre-written summaries that are stored in Amazon S3. Use
- CUpdate the chunking strategy to use semantic boundaries such as complete legal arguments,
- DMigrate from OpenSearch Service to Amazon DynamoDB. Implement keyword-based indexes to
How the community answered
(25 responses)- A16% (4)
- B8% (2)
- C72% (18)
- D4% (1)
Explanation
Option C directly addresses both retrieval relevance and performance scalability. Fixed token chunking breaks semantic continuity in legal texts, causing incomplete context retrieval and degraded response quality. By switching to semantic chunking--based on legal arguments, clauses, or sections--the application preserves contextual integrity, improving retrieval accuracy and reducing hallucinations. Regenerating embeddings aligned with the new chunk structure also improves vector search efficiency, reducing unnecessary comparisons and helping control latency as the dataset scales.
Topics
Community Discussion
No community discussion yet for this question.