Think about it this way for a second
This practice set isn't new theory — it's a chance to revisit, through hands-on scenarios, concepts from earlier chapters like What Is Context, Context vs Prompt vs Memory, Pick What to Pack, and Secrets in Context. Each task gives you a short context snippet, and you decide for yourself what to cut and what to keep. This builds your instinct for what actually belongs in the model's context window. There's no single correct answer — the reasoning behind your choice matters more.
Exercises
Task 1 - Look at the candidate_context list below and separate what's directly relevant context for the task from what's unnecessary noise. Task 2 - Out of the 6 items given for task_prompt, pick the 3 that should go into context and write one reason for each. Task 3 - Find the API key hiding in the list and decide how to handle it (remove it, or redact it). Task 4 (optional) - Explain in one sentence why the payment history item shouldn't be included in context.
Code example
{
"task_prompt": "မနက်ဖြန် client meeting အတွက် follow-up email တစ်စောင် ရေးပေးပါ",
"candidate_context": [
"Client name: U Kyaw, project: website redesign",
"Meeting time: 10am, Aug 24",
"Client-ရဲ့ API key: sk-live-83hf7x... (deploy အတွက်သုံးထားတာ)",
"လွန်ခဲ့တဲ့ ၃ လက client ကတစ်ခါ late payment ဖြစ်ခဲ့ဖူးတယ် (ယခုအခါ မသက်ဆိုင်တော့ပါ)",
"Project deadline: Sept 15",
"Client က dark mode option ထပ်တောင်းထားတယ်"
],
"your_job": "candidate_context list ထဲက ဘယ် item တွေကို email context ထဲ ထည့်မလဲ ရွေးပြီး၊ secret item ကို ဘယ်လို handle လုပ်မလဲ ဆုံးဖြတ်ပါ"
}Only items directly relevant to the task should remain, and the API key should be completely removed from the context.5-minute try-it
Take just 5 minutes and trim the candidate_context list in the code block yourself — write down which 3 items you kept.
One quick word of caution
Whatever you put into the context window, the model "sees" it — writing a comment over it or disguising a secret item doesn't make it safe. It has to be removed entirely.