GH-300 - Configure privacy, content exclusions, and safeguards (14% of the exam) - Section 6.2

Describe ownership and limitations of Copilot outputs and enable duplication detection.

Describe who owns GitHub Copilot output and the limitations on that ownership, and enable the duplication-detection filter that blocks suggestions matching public code. Explain why a team might enable matching-public-code blocking for licence hygiene.

Output ownershipDuplication detectionMatching public codeLicence hygiene

Practice question for this objective

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

A compliance reviewer states that enabling the policy that blocks suggestions matching public code means accepted Copilot output is guaranteed free of public code and free of licensing risk, so no further checks are needed. Which correction is most accurate?

  • AThe filter is purely advisory and never actually blocks a suggestion, so it provides no protection at all and the reviewer should disable it to avoid false confidence.
  • BThe filter inspects only comments and documentation strings, so it leaves executable code unchecked and provides no reduction in public-code matches whatsoever.
  • CThe filter guarantees freedom from public code but not from licensing risk, so only a separate licence-scanning tool is needed before any output is accepted.
  • DThe filter reduces verbatim matches against public code, but it offers no licensing guarantee, so developers still validate accepted output for licence concerns. Correct
Blocking suggestions matching public code reduces verbatim matches but gives no licensing guarantee, so developers must still validate accepted output. The matching-public-code filter lowers the probability of receiving long verbatim copies of public source, but it does not certify that accepted code is free of public code or of licence obligations. Responsible use keeps the developer accountable for validating licence hygiene.

Why A is wrong: This overcorrects; the filter does suppress matching suggestions, so calling it purely advisory and recommending its removal is wrong.

Why B is wrong: This invents a scope limitation; the filter matches code text generally, not just comments, so the claimed gap is fabricated.

Why C is wrong: It is tempting to split the two guarantees, but the filter does not guarantee freedom from public code either; it reduces, not eliminates, matches.

Why D is correct: Duplication detection lowers the chance of receiving public-code matches without certifying licence cleanliness, so human validation of accepted output remains necessary.

See more GH-300 practice questions, answers explained.

Exam traps in Configure privacy, content exclusions, and safeguards

Answers that look right on this material and are not. Each one is a distractor from a different question in the GH-300 bank for this domain.

  • It rewrites any flagged suggestion into a paraphrased version so the developer still receives working code without a public match.

    Why it is wrong: Duplication detection does not paraphrase and re-serve flagged code; it blocks the match rather than rewriting it, so this overstates what the filter does.

  • The filter guarantees clean output, because every suggestion is compared against the full text of all licensed code before it is shown.

    Why it is wrong: No filter compares against the full text of all licensed code or guarantees clean output, so this overstates the coverage and certainty of duplication detection.

  • GitHub retains a perpetual licence to the generated code, so the developer may use it only inside the same repository where it was suggested.

    Why it is wrong: GitHub does not retain a licence that confines reuse to one repository; tying ownership to the originating repository invents a restriction that the terms do not impose.

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