The correct option is Configure an organization wide Copilot policy in GitHub Enterprise that enforces telemetry for all members.

An enterprise or organization level Copilot policy lets administrators centrally require telemetry and it prevents developers from turning it off in their IDEs. Once users authenticate with their enterprise account, the policy overrides local preferences so the telemetry setting is enforced consistently for all members. This satisfies audit requirements because it provides a single source of control and verifiable governance across the entire enterprise.

GitHub Enterprise policy controls for Copilot are designed for compliance and they take precedence over client settings. When telemetry is enforced by policy, the in editor toggle is locked and data collection follows the centrally defined configuration. This approach scales, is auditable, and is the method recommended by the vendor for organization wide enforcement.

Block access to IDE preferences through device management controls is not the most effective solution because it attempts to manage settings at the device layer and can be bypassed or broken by IDE updates. It also does not guarantee that the Copilot extension will honor telemetry, since the authoritative setting is the GitHub policy.

Limit Copilot licenses to organization administrators only does not meet the requirement because it restricts usage rather than enforcing telemetry for developers who need Copilot. This avoids the compliance need instead of solving it and it harms developer productivity.

Tell developers to keep telemetry on in their IDE settings relies on manual compliance and cannot prevent users from disabling telemetry. The scenario requires enforcement for all users, which only a centralized policy can achieve.

Full AWS Practitioner Certification Question