The correct option is Context exclusions let organization administrators specify repositories or organizations that Copilot must not use as context for code suggestions.

This feature allows administrators to block specific repositories or entire organizations so Copilot does not use their content as context when generating completions or answers. The policy is enforced at suggestion time in supported IDEs and on GitHub.com and it limits what content can influence Copilot without affecting normal product operation.

If a repository or file is later excluded Copilot continues to draw on prior suggestions derived from that source is incorrect. Copilot Business does not train on your private code and it generates suggestions from the currently allowed context. Once a source is excluded it is not used to shape future suggestions.

Context exclusions prevent Copilot from using any code in the developer's local workspace when generating suggestions is incorrect. The policy targets GitHub repositories and organizations and it does not block the immediate local files or buffers in the editor. Copilot can still use the code you are actively working on.

By default Copilot Business enforces context exclusions on any repository that contains private data without any administrator setup is incorrect. There is no automatic enforcement based on content and an organization administrator must configure exclusions explicitly.

Full AWS Practitioner Certification Question