hardMultiple Choice
AIF-C01 Practice Question: A retail company uses Amazon Bedrock with…
A retail company uses Amazon Bedrock with Anthropic Claude to generate personalized marketing emails. They want to include dynamic content such as the customer's name and recent purchase history. Which API should they use to enable multi-turn conversations with context management?
⚠ Common exam trap
AWS often tests the distinction between low-level (InvokeModel) and high-level (Converse) APIs, where candidates mistakenly choose InvokeModel because they think it offers more control, but they overlook that Converse is purpose-built for multi-turn conversations with built-in context management.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Converse API
The Converse API (option B) is the correct choice because it is specifically designed for multi-turn conversations with context management in Amazon Bedrock. It automatically handles conversation history, allowing the model to maintain context across multiple exchanges, which is essential for generating personalized marketing emails that reference dynamic content like customer names and purchase history from previous interactions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Amazon Comprehend API
Why it's wrong here
Amazon Comprehend performs entity, sentiment and keyphrase extraction; it holds no conversational state and cannot call Claude. It is tempting because it processes customer text, but the requirement is multi-turn context management, which the Bedrock Converse API provides through its messages array.
- ✓
Converse API
Why this is correct
Converse API provides a unified, model-agnostic interface with built-in conversation history handling, so prior turns are passed as structured messages. This maintains context across turns, enabling dynamic personalisation such as customer names and purchase history in generated emails.
- ✗
InvokeModel API
Why it's wrong here
InvokeModel issues a single stateless request; the caller must resend the full prompt each time, and it offers no built-in conversation history handling. It is tempting because it directly reaches Claude models, but the Converse API is the one that manages multi-turn context natively.
- ✗
Amazon Lex API
Why it's wrong here
Amazon Lex builds conversational voice and text chatbots, not Bedrock model inference; it cannot manage Claude's multi-turn context. It is tempting because Lex handles dialogue state for contact-centre bots, which would suit a standalone chatbot, but the stem requires the Bedrock Converse API for message history.
Go deeper
Related to this question
About these practice questions
One of 862 original AIF-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AIF-C01 practice question is part of Courseiva's free Amazon Web Services 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 AIF-C01 exam.