GH-300 domain - 14% of the exam

Configure privacy, content exclusions, and safeguards

Configure privacy, content exclusions, and safeguards is 14% of the GH-300 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

38
Practice questions
3
Objectives
38
Medium

Where people go wrong

  • Treating content exclusions as access control

    The wrong answers describe content exclusions as a permission system, as encryption, or as deletion from the repository. An excluded file stays on disk, unchanged, and developers can still open, read and edit it. Exclusions are a Copilot context control only: Copilot stops using the matched files as context for inline completions and Copilot Chat, while repository permissions remain the separate mechanism for who can read a file.

    See it in a sample question
  • Reading the public code filter as a guarantee

    The wrong answers treat the filter as proof that accepted output is clean. The filter blocks suggestions that match or closely match publicly available code, which reduces matches but does not eliminate them and carries no licensing guarantee. A developer who accepts a block resembling a copyleft snippet must still review it and validate its licence position before merging. Disabling the filter, or pasting in a copyleft licence, does not settle that.

    See it in a sample question
  • Placing ownership of accepted suggestions outside the user

    The wrong answers place ownership of accepted suggestions somewhere other than the user: GitHub, the model provider, the public repository behind the training data, joint ownership, or the public domain. Others tie ownership to a plan or confine reuse to one repository. Under the terms for Copilot Business, rights in accepted suggestions are assigned to the user, so the company owns the code. GitHub gives no warranty of correctness or security, and the licence position is the user's responsibility.

    See it in a sample question
  • Overstating how far an exclusion reaches

    The wrong answers stretch a content exclusion past where it was configured. A rule set for one repository does not govern a separate repository that lacks its own, and it is not a personal profile setting. It also stops only the named files being used as context, so identical code elsewhere or learned by the model can still surface. Organisation-level rules are the way to cover many repositories at once.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

An organisation sets a content exclusion to keep a vendor library directory out of GitHub Copilot's context. A developer asks what behaviour they should expect once the rule is active and propagated. Which expectation about the excluded directory is accurate?

  • ACopilot will redact the excluded directory from existing pull requests and rewrite any previously merged suggestion that drew on those files so the history no longer references them.
  • BCopilot will continue reading the directory but will mask any sensitive token it finds there, replacing each secret with a safe placeholder before it is used as suggestion context.
  • CCopilot will block the developer from opening or editing files inside the excluded directory until an administrator grants a temporary exception to the active exclusion rule.
  • DCopilot will stop using files in that directory as context for suggestions, so completions will no longer be informed by the contents of the excluded vendor library files. Correct
Recognise that an active content exclusion stops the named files being used as Copilot context rather than altering history or file access. A content exclusion tells GitHub Copilot not to use the matching files as context, so once it is active and propagated the excluded vendor directory no longer informs completions, while the rule neither rewrites past suggestions, masks tokens in still-readable files, nor restricts the developer from opening those files.

Why A is wrong: Exclusions act on future context and have no power to rewrite merged code or pull request history, so expecting retroactive redaction misreads what the rule does.

Why B is wrong: Exclusions stop the files being read at all rather than masking tokens within still-readable files, so describing in-place secret masking misstates the mechanism.

Why C is wrong: Exclusions affect Copilot's use of files as context, not the developer's ability to open or edit them, so this confuses a context rule with a file access restriction.

Why D is correct: A content exclusion removes the named files from the context Copilot reads, so suggestions will no longer be shaped by the excluded directory once the rule is in effect.

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

A developer accepts a substantial Copilot suggestion that happens to resemble a snippet from a copyleft project, even though duplication detection is enabled. Which practice best maintains good licence hygiene for the accepted output?

  • ARely on duplication detection alone, treating an enabled filter as proof that the accepted code carries no licence obligations whatsoever.
  • BReview the suggestion for similarity to licensed sources and validate its licence position before merging, since the developer stays accountable. Correct
  • CAssume that because the developer owns accepted output, any resemblance to licensed code transfers no obligations onto the project.
  • DDisable duplication detection so the suggestion arrives faster, then document the snippet's origin only if a reviewer later asks about it.
Understand that the accountable developer must review accepted suggestions for licence concerns, as duplication detection alone is not a licence guarantee. Duplication detection lowers the chance of reproducing public code but does not certify a suggestion's licence status, and accepted output may still resemble licensed material. The accountable developer must review for similarity and confirm the licence position before merging.

Why A is wrong: Duplication detection reduces but does not eliminate the chance of a match, so treating it as proof of a clean licence status removes the human check that is still needed.

Why B is correct: Because the developer is accountable for accepted output, reviewing it for licence concerns and confirming its position before merging is the practice that maintains licence hygiene.

Why C is wrong: Owning the accepted code does not extinguish third-party licence obligations that attached to matching material, so this misreads ownership as a licence waiver.

Why D is wrong: Disabling the filter removes a safeguard against public code matches and defers licence review, which weakens rather than maintains licence hygiene.

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

A new starter believes that GitHub Copilot suggestions are owned by GitHub and that the company will therefore vouch for their correctness and security. Which statement best corrects this understanding of output ownership and accountability?

  • AGitHub owns the suggestions and underwrites their quality, so the developer can merge accepted output without performing a security review.
  • BOwnership depends on the plan, so Copilot Free output belongs to the developer while Copilot Business output is retained by the organisation's vendor.
  • CGitHub owns the suggestion only until duplication detection clears it, after which responsibility for security passes to the model provider.
  • DThe developer owns the accepted suggestions and stays accountable for their correctness and security, so GitHub does not vouch for the output. Correct
Understand that the developer owns accepted Copilot output and stays accountable for its correctness and security, with no quality guarantee from GitHub. GitHub's terms assign ownership of accepted suggestions to the developer rather than to GitHub, and the company does not warrant the correctness or security of generated code. Accountability therefore stays with the developer, who must review accepted output before relying on it.

Why A is wrong: GitHub neither claims ownership of accepted output nor underwrites its quality, so relying on a guarantee that does not exist is the misconception being corrected.

Why B is wrong: Ownership of accepted output rests with the developer regardless of plan, so making it conditional on Free versus Business misrepresents the terms.

Why C is wrong: Duplication detection does not transfer ownership or push security responsibility to the model provider, so this invents a handover that does not occur.

Why D is correct: Accepted suggestions belong to the developer, who remains accountable for validating them, and GitHub makes no quality guarantee, so this correctly states the position.

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

A developer assumes that a GitHub Copilot content exclusion set on a secrets file in one repository will follow them everywhere and shield the file under every circumstance. Which two statements about the scope and limits of content exclusions are accurate? Select TWO.

  • AAn exclusion is stored in the developer's personal editor profile, so the rule follows that one user across every machine and never applies once a teammate opens the same secrets file instead.
  • BAn exclusion is scoped to where it is configured, so a rule defined for one repository does not govern a separate repository unless that repository also has its own matching exclusion set. Correct
  • CAn exclusion propagates to every repository the developer has ever cloned, so the rule applies in the second repository automatically as long as it was cloned after the exclusion was created.
  • DAn exclusion retroactively rewrites previously merged code and pull request history so that any earlier suggestion drawn from the excluded file is removed from the repository's record.
  • EAn exclusion stops the named file being used as context for Copilot, but it does not guarantee that the same code can never appear in any suggestion, since similar code may be learned from elsewhere. Correct
Recognise that content exclusions are scoped to where they are configured and stop a file being used as context without guaranteeing identical code never appears. Content exclusions take effect only within the repository or organisation where they are defined, so they do not follow a developer into a separate repository, and they remove a file from Copilot's context rather than scanning output, which means similar code learned elsewhere can still appear, while no exclusion is tied to a personal profile, cloning order, or retroactive rewriting of history.

Why A is wrong: Exclusions are configured at the repository or organisation level rather than per user profile, so framing them as a personal editor setting describes the wrong scope.

Why B is correct: Exclusions apply within the repository or organisation scope in which they are set, so a per-repository rule has no reach into a different repository that lacks its own configuration.

Why C is wrong: Exclusions do not blanket every cloned repository based on clone order, so this invents a timing rule and contradicts how scoped exclusions actually work.

Why D is wrong: Exclusions act on future context only and have no power to rewrite merged code or history, so expecting a retroactive cleanup misreads the control.

Why E is correct: Exclusions remove a file from the context Copilot reads, yet they cannot promise identical code will never surface, because comparable patterns may exist outside the excluded path.

Other domains in this exam

See also the GH-300 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.