Q: 3
Scenario: A company needs to optimize its RAG application for semantic search on a vast document
repository in S3. Goal: retrieve relevant, context-aware results based on the deeper meaning of
queries.
Question- Which AWS solution will optimize the company's RAG application and enable semantic
search?.
Options:
Options
Discussion
Option D, encountered exactly similar question in my exam. Kendra is built for semantic search and processes unstructured data from S3 directly. The other services don't handle semantic queries natively.
So with this one, wouldn't Kendra (D) be the best fit? SageMaker or OpenSearch can handle embeddings and search, but they're a lot more manual for RAG semantic queries. Kendra's pretty much designed for semantic/contextual search straight from S3 using its connector. Option C is tempting but Textract/OpenSearch won't do deep semantic out of the box. Am I missing a use case where C would be better?
Not D, I'm thinking C because Textract plus Redshift lets you analyze text, then OpenSearch can handle queries.
C tbh
D , Kendra's the AWS service made for semantic search right out of S3. Official guide covers this use case pretty well.
Kendra feels right for semantic search, so D, but not 100 percent certain here.
Probably C
I saw a super similar question show up in recent exam reports, pretty sure it's asking for the built-in semantic search, which is Kendra (D). The others do bits and pieces but not end-to-end semantic queries straight from S3 like Kendra. Anyone disagree?
D imo, since Kendra is made for semantic search and can connect to S3 out of the box. OpenSearch in C does keyword and vector stuff but not as plug-and-play for deep meaning queries. Pretty sure Kendra fits the RAG use case better, correct me if I missed something.
Be respectful. No spam.
Question 3 of 15