Exam GH-600 Topic 1 Question 99 Discussion
Actual exam question for Microsoft's GH-600 exam
Question #: 99
Topic #: 1
Question #: 99
Topic #: 1
You are running a long GitHub Copilot CLI session. The session has been running for several hours, and you have made significant progress on a multi-file implementation.
Suddenly, you see the Compaction completed message appear without running a command.
What caused the compaction to occur?
Suddenly, you see the Compaction completed message appear without running a command.
What caused the compaction to occur?
Suggested Answer: C Vote an answer
Automatic compaction occurs when the conversation approaches the context-window threshold. The system summarizes or compresses earlier context so that the session can continue without exceeding the model's available context capacity.
Compaction is driven by conversational context volume, not by the size of a local state file or elapsed session duration. It also does not mean that the agent switched models. The purpose is to retain the most relevant working information while reducing the amount of prior detail that must remain in the active context.
For long implementation sessions, developers should preserve important decisions in durable artifacts such as repository files, task lists, plans, issues, and commits. This reduces reliance on the conversation retaining every implementation detail verbatim. After compaction, the developer should verify the current plan, changed files, and pending tasks before authorizing consequential operations.
Study-guide topics: context-window management, compaction, durable state, and long-running agent sessions.
Compaction is driven by conversational context volume, not by the size of a local state file or elapsed session duration. It also does not mean that the agent switched models. The purpose is to retain the most relevant working information while reducing the amount of prior detail that must remain in the active context.
For long implementation sessions, developers should preserve important decisions in durable artifacts such as repository files, task lists, plans, issues, and commits. This reduces reliance on the conversation retaining every implementation detail verbatim. After compaction, the developer should verify the current plan, changed files, and pending tasks before authorizing consequential operations.
Study-guide topics: context-window management, compaction, durable state, and long-running agent sessions.
by Mavis at Oct 13, 2026, 01:31 PM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).