GH-600 Exam Dumps : Developing in Agentic AI Systems

Target

Value

Top-level property

concurrency

Concurrency-group property

group

Cancellation property

cancel-in-progress

Result:

concurrency:

group: production

cancel-in-progress: true

The concurrency block defines a shared execution group. Assigning group: production places all production deployment runs into the same group, preventing simultaneous deployments to that target.

Setting cancel-in-progress: true changes the default behavior by cancelling an active deployment when a newer workflow run enters the group. This ensures that only the latest production deployment continues rather than allowing an outdated deployment to finish after a newer version has been requested.

The concurrency block is normally placed at the workflow level when the policy applies to the full deployment workflow. It can also be scoped to a job when only a specific deployment job needs coordination. The environment name identifies the production target, but environment configuration alone does not impose the required single-active-run and cancellation behavior.

A production concurrency group should be reserved for operations that genuinely target the same deployment resource. Reusing it for unrelated jobs would unintentionally serialize unrelated work.

Study-guide topics: deployment coordination, concurrency groups, cancellation policy, and safe production execution. Reference: GitHub Actions—Control concurrency .

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 preferences, 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.

The first statement is Yes . When an MCP server is configured for a repository, GitHub Copilot cloud agents can use the enabled MCP tools autonomously during assigned tasks. GitHub specifically notes that Copilot does not request interactive approval before invoking configured MCP tools, making careful tool allowlisting and credential protection important.

The second statement is No . For repository-level MCP integration, Copilot cloud agent currently supports MCP tools , but it does not support MCP resources or MCP prompts exposed by the server. Resources and prompts are available in other MCP-capable Copilot experiences, such as IDE chat, but they are not consumed by the cloud coding agent in this configuration.

The third statement is Yes under the planned configuration. Litware requires agent1 to access all available tools . GitHub custom-agent configuration supports this by omitting the tools property or specifying tools: [ " * " ]. Likewise, an MCP server can use " * " to expose all of its tools. Consequently, newly introduced MCP1 tools fall within that wildcard authorization and become available without individually adding each tool name.

Study Guide Reference Topics: MCP tool integration, custom-agent tool configuration, autonomous tool invocation, MCP capability boundaries, and least-privilege agent execution.