AIP-C01 · Question #91
A company is building a generative AI (GenAI) application that processes financial reports and provides summaries for analysts. The application must run two compute environments. In one environment…
The correct answer is D. Use the Amazon Bedrock Converse API and IAM roles for authentication. Pass previous. The Amazon Bedrock Converse API is designed for multi-turn conversational interactions-it natively supports passing prior conversation turns (message history) in each request, preserving context across interactions. Using IAM roles for authentication is consistent across both…
Question
A company is building a generative AI (GenAI) application that processes financial reports and provides summaries for analysts. The application must run two compute environments. In one environment, AWS Lambda functions must use the Python SDK to analyze reports on demand. In the second environment, Amazon EKS containers must use the JavaScript SDK to batch process multiple reports on a schedule. The application must maintain conversational context throughout multi-turn interactions, use the same foundation model (FM) across environments, and ensure consistent authentication. Which solution will meet these requirements?
Options
- AUse the Amazon Bedrock InvokeModel API with a separate authentication method for each
- BUse the Amazon Bedrock Converse API directly in both environments with a common
- CCreate a centralized Amazon API Gateway REST API endpoint that handles all model
- DUse the Amazon Bedrock Converse API and IAM roles for authentication. Pass previous
How the community answered
(56 responses)- A14% (8)
- B4% (2)
- C7% (4)
- D75% (42)
Explanation
The Amazon Bedrock Converse API is designed for multi-turn conversational interactions-it natively supports passing prior conversation turns (message history) in each request, preserving context across interactions. Using IAM roles for authentication is consistent across both Lambda (Python SDK) and EKS (JavaScript SDK) environments because IAM roles are AWS-native, work identically regardless of compute environment, and support the same foundation model. Option A fails because InvokeModel does not natively manage conversational context and uses separate auth. Option B is partially correct but the truncated answer omits the critical detail of passing conversation history. Option C adds unnecessary complexity via API Gateway without solving the multi-turn context problem natively.
Topics
Community Discussion
No community discussion yet for this question.