Home / Claude Certified Developer – Foundations / Objective 6.1

Domain 6: Prompt and Context Engineering · 11% of the exam · Full exam outline

6.1 Context Engineering

What this objective covers · 4% of the exam

Context and memory management techniques for Claude applications, including context window management, prevention of context drift and bloat (tool output pruning, compaction), and context isolation through subagents or multi-step agentic workflows.

Practice questions

Question 1easy

An accessibility service receives a single product image, writes alt text for it, returns the text and ends. No request ever refers back to an earlier one. Which memory scope fits this agent?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

External storage is the right scope when state must survive across sessions or users. Here no request reuses earlier state, so it only adds retrieval latency and engineering for data that is never read back.

Keeping everything in context feels safe, but cost then scales with history length. Unrelated past jobs add tokens to every call without helping the current image.

Summarized memory helps a long-running conversational agent that has outgrown its token budget. These jobs are not a conversation, so a summary of unrelated images is pure overhead.

Stateless memory suits task agents that finish and close, and independent pipelines. Each alt-text job is self-contained, so there is no prior context worth paying to keep.

Question 2easy

An agent needs to find where a setting is defined across a large, unfamiliar codebase. The search will read many files, but the answer is a single file path. Which context strategy fits best?

Included in Master: master every domain.See plans