Free GitHub Copilot practice — 6 questions on Privacy Fundamentals and Context Exclusions, with explanations. No sign-up.
Full 12-question mixed test →
Question 1 of 6 · Privacy Fundamentals and Context Exclusions
An organization owner configures a content exclusion rule at the organization level that excludes all files matching `**/vendor/**` from Copilot's context across every repository. A repository administrator in one specific repo wants Copilot to see files in that repo's `vendor/` folder because they contain internally maintained code, and creates a repo-level rule attempting to re-include them. What actually happens?
Content exclusions are additive and security-first: organization-level and repository-level exclusion rules combine, and the most restrictive applicable rule always wins. Repository settings cannot un-exclude files that an organization has excluded.
Question 2 of 6 · Privacy Fundamentals and Context Exclusions
Where must repository-level Copilot content exclusion rules be defined for GitHub Copilot Business or Enterprise?
Repository-scoped content exclusions are defined in `.github/copilot.yml`, specifying glob patterns under an exclude/content-exclusion key, which Copilot Business/Enterprise honors when building context.
Question 3 of 6 · Privacy Fundamentals and Context Exclusions
A GitHub Copilot Business administrator wants to guarantee that no developer in the organization can disable the filter that blocks suggestions matching publicly available code. What should the administrator do, and how does this compare to Copilot Individual?
Copilot Business/Enterprise admins can set an org-wide policy for the duplication-detection (public code matching) filter that locks the setting for all members, whereas Copilot Individual only exposes this as a personal, per-user toggle with no centralized enforcement.
Question 4 of 6 · Privacy Fundamentals and Context Exclusions
A company evaluating Copilot Business is concerned about intellectual property risk from suggestions that might reproduce public code verbatim. Which statement correctly describes GitHub's Copilot IP indemnification commitment?
GitHub's Copilot IP indemnification commitment is extended to Business and Enterprise customers and is conditioned on having the filter that blocks suggestions matching public code turned on, among other required settings.
Question 5 of 6 · Privacy Fundamentals and Context Exclusions
How do GitHub Copilot Individual and Copilot Business/Enterprise differ regarding whether a developer's code is used to train GitHub's underlying models?
GitHub differentiates data handling by plan: Copilot Individual users can opt in/out of allowing their code snippets to be used for product improvement/training, while Copilot Business and Enterprise contractually guarantee customer prompts and code are not used to train GitHub's models.
Question 6 of 6 · Privacy Fundamentals and Context Exclusions
A developer working in a repository with a content exclusion configured for `config/secrets.yaml` asks Copilot Chat, "Summarize the contents of config/secrets.yaml." What should happen?
Content exclusions apply uniformly across Copilot's features, including both code completions and Copilot Chat — an excluded file is not read into context for either, and Chat will indicate it cannot access that file.
Ready for the real thing?
The full course has two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed answer explanations.