Black Friday Reward - Upto 75% off - Ends in 0d 00h 00m 00s - Coupon code: CFsave75

Databricks Certified Context Engineer Associate Context-Engineer-Associate Question # 7 Topic 1 Discussion

Databricks Certified Context Engineer Associate Context-Engineer-Associate Question # 7 Topic 1 Discussion

Context-Engineer-Associate Exam Topic 1 Question 7 Discussion:
Question #: 7
Topic #: 1

A context engineer is tuning a compaction prompt for a Databricks agent that summarizes customer support ticket histories before sending them to a downstream LLM. The trace being compacted spans 40 turns, and the compacted output must fit within the downstream LLM’s context window. During initial evaluation against a benchmark of escalated support cases, the engineer observes that the compaction output consistently omits several prior resolutions and key escalation events, even though it fits well within the downstream LLM’s context window.

What tuning step should the engineer take next?


A.

Add a token-count cap to the compaction prompt to shorten the summary and lower downstream inference cost and latency, then check afterward whether the key events were retained.


B.

Add a recency rule that keeps the most recent turns in full and compresses the earlier turns, since the latest exchanges usually carry the most relevant context.


C.

Broaden the compaction prompt’s retention rules to capture all events, resolutions, and escalation signals, accepting a longer summary for now and tightening verbosity in a later iteration.


D.

Add retention rules and pruning rules in the same iteration so recall and precision are tuned together rather than over separate passes.


Get Premium Context-Engineer-Associate Questions

Contribute your Thoughts:


Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.