What is a key characteristic of GitHub Enterprise Server (GHES) compared to GitHub Enterprise Cloud (GHEC)?

Question

Options

• AGHES is hosted by GitHub and offers automatic scaling, while GHEC requires self-hosting.
• BGHEC offers data residency options in regions that GHES does not support.
• CGHES allows enterprises to have complete control over their hosting environment, including data
• DGHES users cannot integrate with external identity providers for authentication.

• A
  7% (2)
• B
  4% (1)
• C
  85% (23)
• D
  4% (1)

Explanation

Option C is correct because GHES is a self-hosted deployment of GitHub that enterprises install and manage on their own infrastructure (on-premises or private cloud). This gives organizations full control over where data lives, network configuration, maintenance schedules, and security policies - a critical requirement for regulated industries or security-sensitive organizations.

Why the distractors are wrong:

• A is backwards: GHEC is the GitHub-hosted option with automatic scaling; GHES is the self-hosted one.
• B is incorrect: GHEC actually does support data residency in specific regions (e.g., EU) - this is a feature of the cloud offering, not a limitation of GHES.
• D is incorrect: GHES does support external identity providers (SAML, LDAP, CAS) for SSO authentication.

Memory tip: Think of the "S" in GHES as "Self-hosted" - the enterprise runs the Server themselves. The "C" in GHEC stands for "Cloud" - GitHub hosts it for you. Whenever a question mentions complete control over hosting environment, that's the self-hosted (GHES) story.

No community discussion yet for this question.