An organisation administrator must stop a directory holding configuration secrets from ever being sent as context to GitHub Copilot, while still letting developers use Copilot on the rest of the repository. Which GitHub Copilot control should the administrator configure?
- AModel Context Protocol, so the secrets directory is routed through an approved external server that decides when Copilot may read those files.
- BDuplication detection, which compares each generated suggestion against public code and suppresses any match before it reaches the developer.
- CContent exclusions, which prevent the specified files and paths from being used as context for completions and chat in the affected repositories. Correct
- DCopilot Spaces, which package the secrets directory into a curated context bundle that developers attach when they want grounded answers.
Why A is wrong: Model Context Protocol connects Copilot to external tools and data sources; it does not block files from being used as context, so it cannot enforce the exclusion the administrator wants.
Why B is wrong: Duplication detection filters suggestions that match public code; it does not stop named local files being read as context, so it addresses output matching rather than input exclusion.
Why C is correct: Content exclusions let an administrator name files or paths that Copilot must not read as context for completions or chat, which precisely stops the secrets directory feeding suggestions while the rest of the repository stays usable.
Why D is wrong: Copilot Spaces curate context to include in chat, the opposite of excluding it; using a Space would expose the secrets rather than prevent them being read.