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

Apply security warnings and troubleshoot issues with suggestions and content exclusions.

Enable security warnings that flag risky patterns such as hardcoded secrets, and troubleshoot common problems: suggestions not appearing, content exclusions not taking effect, and authentication or policy issues. Resolve them by checking settings, scope, and propagation.

Security warningsTroubleshootingHardcoded secretsExclusion propagation

Practice question for this objective

Free sampleConfigure privacy, content exclusions, and safeguardsmedium

A developer expects a content exclusion on a secrets file to also stop that file appearing in GitHub Copilot suggestions in a different repository they work in, but it has no effect there. Which fact about exclusion propagation explains why the rule does not carry across?

  • AContent exclusions are scoped to where they are configured, so a rule defined for one repository does not automatically govern files in a separate repository unless it is also set there. Correct
  • BContent exclusions propagate to every repository a developer has ever cloned, so the rule failed only because the second repository was cloned before the exclusion was first created.
  • CContent exclusions are stored in the developer's editor profile, so the rule only follows the individual user and never applies once a teammate opens the same secrets file instead.
  • DContent exclusions only suppress matching suggestions, so the rule did apply but the second repository simply produced no completion that matched the excluded secrets file pattern.
Understand that content exclusions are scoped to where they are configured and do not automatically propagate across separate repositories. Content exclusions take effect within the repository or organisation where they are defined, so a rule created for one repository does not extend to a separate repository, which must have its own exclusion configured for the same file to be ignored there.

Why A 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 B is wrong: Exclusions do not blanket every cloned repository based on clone order, so this invents a timing rule and misses that exclusions are scoped to where they are defined.

Why C 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 D is wrong: Exclusions govern what context Copilot may read rather than matching suggestion text, so describing them as suppressing matching completions misrepresents how they work.

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.

  • Organisation-level rules are the only way to exclude content, because repository administrators cannot define their own exclusion rules.

    Why it is wrong: Tempting as a clean hierarchy, but repository administrators can also set exclusions, so the organisation level is not the sole place to configure them.

  • Exclusions stop working entirely as soon as the excluded directory grows beyond a few hundred files in a single repository.

    Why it is wrong: Tempting as a hidden limit, but there is no such file-count threshold that switches exclusions off; the rule keeps applying to matched paths.

  • At the repository level in each repository's Copilot settings, because repository exclusions automatically cascade upward and become the organisation default for new repositories.

    Why it is wrong: Repository exclusions are scoped to their own repository and do not cascade up to become an organisation default, so this misreads the direction of exclusion scope.

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