Practice English vocabulary for LLM context windows: context length limits, prompt construction, context stuffing, chunking strategies, and context window management.
0 / 10 completed
1 / 10
What is 'the context window' of an LLM?
The context window is the LLM's working memory for a single call. Everything the model can 'see' when generating a response must fit within the limit (e.g., 128K tokens for Claude 3). Input + output combined cannot exceed this limit.
2 / 10
What does 'prompt construction' mean in the context of LLM applications?
Prompt construction is an engineering concern: assembling components in the right order, managing token budgets for each section (system: 500 tokens, history: 2000, context: 8000, query: 200), and ensuring the result fits the context window while maximizing information quality.
3 / 10
What is 'context stuffing' and why is it problematic?
Context stuffing (adding large amounts of raw text) seems intuitive but hurts quality: models lose focus in very long contexts (the 'lost in the middle' effect), it increases latency and cost, and it prevents targeted retrieval. Curated, relevant context outperforms raw volume.
4 / 10
What is 'chunking strategy' for documents in a RAG pipeline?
Chunking strategy significantly impacts RAG quality. Too-small chunks lack context; too-large chunks include irrelevant content that dilutes the signal. Semantic chunking (splitting at natural boundaries) outperforms fixed-size chunking for most document types.
5 / 10
What does 'context window management' mean in a multi-turn application?
In long conversations, history grows until it exceeds the context window. Strategies: sliding window (drop oldest turns), summarization (compress old history into a summary), selective memory (keep only turns with tool calls or key facts), and vector memory (retrieve relevant past turns).
6 / 10
During a code review of the new sentiment analysis API integration, Sarah notices that the developer, David, is repeatedly adding more and more customer feedback snippets to the LLM's prompt. The API response times are noticeably increasing. What does David's approach likely represent? context stuffing
Context stuffing happens when you add excessive amounts of information to a prompt beyond what the LLM's context window can effectively process. While providing more data *can* improve accuracy in some cases, it overwhelms the model, leading to slower response times and potentially inaccurate results as it struggles to prioritize relevant details within the constrained window. The core issue is exceeding the limit – the API is likely timing out or returning errors due to this.
7 / 10
In a Slack channel for the 'Phoenix' project, Mark asks: 'Can we use embeddings to find similar user reviews to help us identify potential product issues?' Liam replies with: 'We should definitely explore using a vector database and semantic search to efficiently retrieve relevant context.' What is Liam referring to?
Semantic search leverages embeddings – vector representations of text – to understand the *meaning* behind words and phrases. Instead of simply matching keywords, it finds reviews with similar semantic relationships, which is crucial for tasks like identifying related product issues based on user feedback. This contrasts with keyword-based searches that rely solely on literal string matches.
8 / 10
You're drafting the description for a Pull Request to update the 'Hydra' application with a new feature. You want to clearly explain your approach to managing context window usage. Which of the following best describes the goal of chunking strategy in this scenario?
Chunking strategy is about intelligently dividing large documents or datasets into smaller pieces that *each* fit within the LLM's context window. This allows you to process information sequentially without exceeding limits and ensures that relevant context is maintained across different segments – it's a core technique for RAG pipelines.
9 / 10
During the daily standup meeting, Alex reports: 'I'm currently experimenting with different prompt engineering techniques to improve the accuracy of our chatbot's responses when handling complex user queries.' What is Alex primarily focusing on?
Prompt engineering techniques involve designing and refining the prompt itself – the instructions and context you provide to the LLM. It's about shaping the model's response by carefully controlling the wording, structure, and examples within the prompt to elicit more accurate and relevant answers. This is distinct from optimizing the underlying model or monitoring server resources.
10 / 10
The 'Orion' system uses a multi-turn chatbot for customer support. The team is noticing inconsistent answers from the bot when handling complex questions about product features. They suspect an issue with context window management. What does this term typically refer to?
Context window management focuses on how the system decides what information to keep from previous turns of a conversation within the LLM's context window. It's about intelligently selecting and retaining relevant dialogue history to maintain coherence and provide accurate responses in multi-turn interactions – simply having a large window isn't enough; you need to actively manage its contents.
What will I practise in "Context Window Vocabulary"?
Practice English vocabulary for LLM context windows: context length limits, prompt construction, context stuffing, chunking strategies, and context window management.
How many exercises are in this module?
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more LLM App Development exercises?
Browse the full LLM App Development hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.