The correct option is GitHub blocks external access to private workflow badges to prevent unauthorized embedding or linking.

Private repository workflow badges require authentication and repository access. GitHub only serves the badge image to viewers who are signed in and authorized, which prevents the badge from loading on an external status page for users outside GitHub who lack access.

It only works with GitHub Enterprise Server installations is incorrect because workflow badges work on both GitHub Enterprise Server and GitHub.com. The limitation comes from private repository access rules rather than the hosting product.

The use of self hosted runners in the workflow disables public badge visibility is incorrect because runner type does not affect badge visibility. Badge access is controlled by repository privacy and authentication, not whether the job uses self hosted or GitHub hosted runners.

Badges are visible exclusively to repository collaborators and not to any external viewer is incorrect because badges for public repositories are visible to everyone. For private repositories the badge is visible to authenticated users with access, so the statement is overly absolute and does not reflect the actual permission checks.

Full AWS Practitioner Certification Question