GitHub GH-300: Configure Privacy, Content Exclusions, and Safeguards Practice Questions

Three correct statements: (C) Copilot uses the issue title and any content the user has already typed as context to generate a suggested description — it works with partial input. (A) Copilot for Issues is a feature that must be enabled by an org administrator in the Copilot policy settings; it is not on by default. (D) The generated description is a suggestion that populates the issue body field, which the user can freely edit before submitting. Option F is incorrect — a pre-defined issue template is not required; Copilot can generate content even from a blank or minimally filled form. Option B is incorrect — Copilot does not automatically create, submit, or assign issues; it only generates suggested text. Option E is incorrect — Copilot for Issues is a managed feature tied to Copilot Business/Enterprise plans and requires administrator enablement, not available freely to all GitHub accounts.

The Copilot Seat management page (Organization Settings → Copilot → Seats) includes a 'Last activity' column that shows when each seat holder last had Copilot activity. This is the direct, supported UI method for identifying inactive seat holders. Option C is incorrect — all assigned Copilot Business seats are billed at the same per-seat rate regardless of usage; there is no $0 charge for unused seats. Option B is incorrect — while the Metrics API provides usage data, it returns aggregated organizational or team-level statistics, not an individual per-seat activity breakdown suitable for filtering inactive specific users in this manner. Option D is incorrect — individual suggestion acceptance events are not individually logged as audit events per user in the audit log; the audit log tracks administrative actions (seat assignment, policy changes), not per-suggestion activity.

Two correct actions: (1) Adding the corporate proxy's root CA certificate to the trusted store allows the IDE (and OS) to validate the proxy's re-signed certificates, resolving SSL errors. (2) Setting HTTPS_PROXY ensures Copilot's extension routes its HTTPS traffic through the corporate proxy so it can reach GitHub's endpoints. Option C is incorrect — disabling TLS verification is a security anti-pattern and not a supported or recommended Copilot configuration. Option D describes bypassing TLS inspection, which may resolve the certificate error but is a network-layer change; however, this alone does not ensure the proxy is configured for routing (both A and B together are the standard solution), and this option doesn't address the client-side configuration. Option E is incorrect — Copilot only operates over HTTPS; downgrading to HTTP is not supported and would be a serious security risk.

GitHub's audit log records Copilot seat assignment and removal events under the action category copilot.seat_assignment (and related actions like copilot.seat_cancel). Filtering the audit log for these events provides a historical record of who was assigned a seat and when. Option D is incorrect — the Copilot Metrics API provides usage/activity telemetry (suggestions accepted, lines of code, etc.) and does not log seat assignment history. Option B is incorrect — the Seats page shows the current state of seat assignments, not historical changes. Option A is incorrect — billing and invoice history shows charge amounts and active user counts but does not provide the detailed event-level audit trail of individual assignments.

Copilot PR summaries are triggered by clicking the Copilot (sparkle) icon inside the PR description text area and selecting 'Generate summary'. This populates the description field with an AI-generated summary of the diff. Option A is incorrect — there is no 'copilot: summarize' commit message convention that triggers summaries. Option B is incorrect — labels do not trigger Copilot PR summaries. Option C is incorrect — mentioning @github-copilot in comments is how you request a code review, not a PR description summary.