The correct choice is Organization wide privacy controls with content exclusions that keep sensitive code out of Copilot prompts. This capability lets administrators enforce enterprise policies across all teams while preventing confidential material from being sent to the service and it supports governance and audit needs for regulated data.

These organization wide controls enable content exclusions that block selected repositories paths or patterns from being included in prompts so sensitive code stays within the organization. Admins can centrally manage who can use Copilot and how it behaves and they can rely on enterprise audit events to review activity. This combination is designed to maintain security and compliance while still allowing teams to benefit from AI assistance.

Shared suggestion streams that let developers view Copilot outputs from other teams is not a capability of Copilot Enterprise and it would undermine privacy by exposing generated content across squads rather than preventing leakage.

Premier support from GitHub with dedicated advisors for incident response is a support offering rather than a product capability that governs model prompts or data handling and it does not provide the required preventive controls or auditing.

Autonomous project generation to produce complete applications with minimal developer input is not a Copilot Enterprise feature and it would not address the need for strict data protection or policy based governance.

Full AWS Practitioner Certification Question