Microsoft GH-600 Exam Questions

Workflow artifacts provide an explicit mechanism for transferring serialized agent state between jobs. The producing job writes the required state to files and uploads those files as an artifact. Subsequent jobs download the artifact and load the state before continuing the integration-test workflow.

This is necessary because jobs do not automatically share process memory or a common workspace. They may execute on different runners, and even jobs assigned to similar runner types must not depend on incidental machine reuse. Uploading the state establishes a deliberate persistence boundary rather than relying on temporary execution infrastructure.

Committing state after every job introduces repository mutations merely to transport workflow data. Environment variables are also unsuitable as a general cross-job state store: setting a variable in one job does not automatically expose it in another, and complex state is better represented in structured files.

The application must serialize the information needed for continuation, such as completed steps, relevant decisions, and test progress. Uploading an arbitrary directory does not automatically restore a running agent process.

Relevant curriculum topics are durable state, cross-environment continuity, and resuming work without repeating completed steps.

===============

The correct command is /clear. In GitHub Copilot CLI, /clear starts a fresh conversational state by removing the current chat history from the active session. This is the appropriate action when the requirement is to discard prior conversation context completely rather than compress or summarize it.

/compact is specifically designed for context management during long-running sessions. It summarizes older conversation history so that useful information can be retained while freeing context-window capacity. Because the question explicitly says ''without summarization,'' /compact does not satisfy the requirement.

/usage displays session consumption and usage information rather than modifying conversation state. /reset-context is not the standard slash command used for clearing Copilot CLI conversation history in this scenario.

The operational distinction is important in agentic workflows. Compaction preserves semantic continuity, while clearing abandons the prior conversational state and gives the agent a clean starting point. Clearing is therefore appropriate when accumulated context has become irrelevant, misleading, or overly large and you deliberately do not want previous reasoning, instructions, or task history carried forward.

Study Guide Reference Topics: Manage Memory, State, and Execution; conversation-state management; context-window control; session reset versus context compaction.

The primary failure is insufficient task definition. ''Fix the login bug'' does not identify the observed behavior, expected behavior, reproduction conditions, affected component, or completion criteria. The agent must infer these details, creating a substantial risk of incomplete changes or work outside the intended scope. A clear issue description supplies the information needed to construct and implement an appropriate plan.

For this scenario, the description should identify how the login failure occurs, which authentication path is affected, what successful behavior looks like, and which existing behavior must remain intact. Relevant error messages, reproduction steps, and expected tests make the task independently verifiable. These details turn an ambiguous request into a bounded engineering assignment.

Enabling memory does not supply missing requirements reliably. MCP rate limits govern service interaction rather than task clarity. Additional setup resources address environmental capacity or dependency preparation, not uncertainty about what must change.

The corrective action therefore belongs at task intake, where developers define the agent's inputs and success conditions. The relevant curriculum topics are defining agent inputs, outputs, and success criteria and mitigating poorly scoped task assignments.

===============

The gh agent-task view command supports inspecting an individual agent task. Combining --log with --follow selects session log output and continues following that output as the session progresses. The official CLI reference describes these flags as ''Show agent session logs'' and ''Follow agent session logs,'' respectively.

This combination is appropriate when an agent appears stalled because a task-level status alone cannot explain what the agent is currently doing. Following the log allows the operator to observe additional activity, identify the last reported operation, and distinguish ongoing execution from a task awaiting intervention.

The list command is useful for discovering tasks and obtaining an overview of concurrent activity. It does not replace following the detailed output of the relevant session. The --jq parameter filters structured JSON output; it does not provide the continuous log-following behavior requested here. Opening a browser with a web option also fails the terminal streaming requirement.

Viewing logs is an observational action. It does not itself restart, cancel, or unblock the agent.

Study-guide topics: monitoring concurrent agents, execution visibility, and troubleshooting. Reference: GitHub CLI---gh agent-task view.

===============

Copilot memory is an organization-level capability. Configuring it through the organization's Copilot settings establishes the governance boundary, availability, and policy controls consistently for the developers and repositories covered by that organization.

Personal settings are unsuitable because they create inconsistent behavior between developers and do not provide centralized administration. A repository-level configuration can supply repository instructions and scoped context, but it does not replace the organization-level control that enables and governs the memory capability. An individual agent profile defines role behavior, tool access, prompts, and delegation settings; it is not the tenant-level location for enabling Copilot memory.

Organization configuration is particularly important when agents must retain approved context, recurring pReference, and workflow guidance across sessions without each developer configuring behavior independently. Central governance also allows administrators to maintain predictable controls over which organizational information is available to Copilot.

Study-guide topics: organizational governance, persistent context, and centralized agent configuration.