After GitHub Connect is established between GHES and GitHub.com, which two features can administrators selectively enable? (Choose two)
Select all correct answers, then click Submit.
Short Explanation and Infographic
GitHub Connect is a feature bridge, not a giant bidirectional mirror of every private repo and not a swap of your IdP. You pick capabilities like Unified Search and Dependabot alerts (plus things like unified contributions or Actions access depending on version and policy). Admins should enable only what policy allows — each switch can send limited metadata toward GitHub.com.
Full explanation below image
Full Explanation
The correct answers are Unified Search and Dependabot alerts. GitHub Connect links a GHES instance to a GitHub.com organization or enterprise so selected cloud capabilities can be used from the self-hosted instance. Typical selectable features include Unified Search, unified contributions, Dependabot/advisory data, license usage sync, and related Actions/content access features depending on release. Option B is wrong: Connect does not automatically mirror all private repositories bidirectionally. Option D is wrong: Connect does not replace GHES authentication with GitHub.com password logins; GHES still uses its configured authentication (for example LDAP, SAML, or built-in). Administrators should review data-sharing implications, enable only approved features, and document the linked GitHub.com account ownership for audits.