AIF-C01 Fundamentals of Generative AI Practice Question
A developer is using Amazon Bedrock's Converse API to build a multi-turn conversation. They notice the model forgets earlier context after a few exchanges. What is the most likely cause?
⚠ Common exam trap
The trap here is that candidates may incorrectly attribute memory loss to model limitations (like context window size) rather than the developer's failure to include conversation history in each request.
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
✓
The developer is not sending the previous messages in each request
The Converse API is stateless by design, meaning it does not retain conversation history between API calls. To maintain context across multiple turns, the developer must explicitly include the entire message history (previous user and assistant messages) in each new request. If the developer omits these previous messages, the model has no memory of earlier exchanges and will appear to forget context.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The API has a rate limit that truncates history
Why it's wrong here
Rate limits throttle request throughput; they do not silently truncate the message history you send. The Converse API is stateless, so the developer must resend prior turns each call. Rate limiting would instead be the concern when a workload exceeds provisioned requests per minute, producing throttling errors rather than lost context.
- ✗
The model's context window is too small for the conversation
Why it's wrong here
A small context window would truncate history, but the stem describes forgetting after only a few exchanges, which points to the developer not resending prior turns at all. Converse is stateless, so each call must include the full message array. A larger context window is the fix when genuinely long conversations exceed the token limit.
- ✗
The model's maximum output length is set too low
Why it's wrong here
Maximum output length caps how many tokens the model generates in its reply, not how much input history it retains. Earlier turns vanish because the developer is not resending them, since Converse is stateless. Raising output length would be right when replies are being cut off mid-sentence, not when context is forgotten.
- ✓
The developer is not sending the previous messages in each request
Why this is correct
The Converse API is stateless: it retains no memory between calls, so multi-turn context exists only if the developer resends prior messages each request. Omitting earlier turns means the model receives no history, causing it to forget context after a few exchanges.
Go deeper
Related to this question
About these practice questions
This AIF-C01 question is part of Courseiva's 862-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.