Answer: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application.

## Detailed Explanation Based on the requirements for an AI application that enables employees to view open customer claims, retrieve details for individual claims, and access associated claim documents, the optimal solution is **B: Use Agents for Amazon Bedrock with Amazon Bedrock knowledge bases to build the application**. ### Why Option B is Correct 1. **Agents for Amazon Bedrock**: This service provides AI-powered conversational agents that can understand natural language queries from employees. These agents can be configured to handle specific workflows like checking claim status, retrieving claim details, and accessing documents through conversational interfaces. 2. **Amazon Bedrock Knowledge Bases**: This feature allows you to create repositories of structured and unstructured data that can be accessed by Bedrock agents. For this use case: - Claim details (structured data like claim numbers, dates, status, amounts) can be stored and indexed - Associated documents (unstructured data like PDFs, images, forms) can be stored and made searchable - The knowledge base provides semantic search capabilities to find relevant information based on natural language queries 3. **Integration Capabilities**: The combination allows seamless integration where: - Employees ask questions in natural language (e.g., "Show me all open claims for customer X" or "What documents are associated with claim #12345?") - The agent processes the query and retrieves relevant information from the knowledge base - The system can present structured claim details alongside associated documents ### Why Other Options Are Less Suitable **A: Use Agents for Amazon Bedrock with Amazon Fraud Detector** - Amazon Fraud Detector is specifically designed for fraud detection and prevention, not for general claim management and document retrieval - While it could potentially identify fraudulent claims, it doesn't provide the comprehensive claim viewing, detail retrieval, and document access capabilities required **C: Use Amazon Personalize with Amazon Bedrock knowledge bases** - Amazon Personalize is a recommendation service for creating personalized user experiences - It's not designed for querying and retrieving specific claim information and documents - While knowledge bases could store the data, Personalize wouldn't provide the conversational interface or direct query capabilities needed **D: Use Amazon SageMaker to build the application by training a new ML model** - This would require significant development effort to build a custom solution from scratch - While technically possible, it's not the most efficient or cost-effective approach - SageMaker is better suited for custom ML model development and training, not for rapid deployment of conversational AI applications with document retrieval capabilities - This approach would require building all the conversational, query processing, and document retrieval functionality that Bedrock agents and knowledge bases provide out-of-the-box ### Key Considerations The solution using Agents for Amazon Bedrock with knowledge bases is optimal because: 1. It provides a ready-to-use conversational interface 2. It offers built-in document retrieval and semantic search capabilities 3. It can be implemented quickly without extensive custom development 4. It scales automatically with AWS managed services 5. It maintains security and access controls for sensitive claim data This approach aligns with AWS best practices for building generative AI applications that need to access and process both structured and unstructured enterprise data.