Free Microsoft GH-100 Actual Exam Questions - Question 12 Discussion

Question No. 12
What is a key characteristic of GitHub Enterprise Server (GHES) compared to GitHub Enterprise Cloud
(GHEC)?
Select one option, then reveal solution.
US
AX
Andrew X.
2026-02-17

Option C stands out because GHES is about self-hosting, so you get to manage your data and security policies directly. Options A and D don’t really fit since GitHub hosts GHEC, not GHES, and GHES can integrate with external identity providers. B is more about cloud features. So C really nails the main difference here.

0
SM
Sohail M.
2026-02-16

Probably C, since GHES is meant for self-hosting and full control over infrastructure.

0
SM
Sohail M.
2026-02-16

This seems pretty straightforward since GHES is all about on-prem control. So C fits best because it highlights hosting control and data security, which the cloud option doesn’t offer. C

0
SM
Sohail M.
2026-02-13

C. GHES is designed for on-premises hosting, letting companies manage everything from data storage to network policies themselves, unlike the cloud version which is fully managed by GitHub.

0
ZP
Zain P.
2026-01-31

It’s C. GHES is all about companies running their own servers and managing their own data, which isn’t the case for the cloud option. A and D are off since GHES isn’t hosted by GitHub and does support external auth providers.

0
ZP
Zain P.
2026-01-30

C makes the most sense since GHES is designed for full self-hosting control.

0
ZP
Zain P.
2026-01-28

C imo, because GHES is all about on-prem control and customization, unlike GHEC which is managed by GitHub. B doesn’t fit as well since GHES doesn’t usually offer the same global data center options as cloud.

0
MX
Michael X.
2026-01-24

C/B? I’m sticking with C because GHES is definitely about self-hosting, giving full control over where everything lives and how it’s secured. B sounds tempting since cloud services often have regional data centers, but that’s more about cloud infrastructure than a core feature difference. D doesn’t add up since GHES does integrate with external identity providers. A is just backwards—GHES isn’t hosted by GitHub, it’s self-hosted. So, C feels like the most defining characteristic here.

0
MX
Michael X.
2026-01-18

C/B? C definitely fits since GHES is about self-hosting and control, which GHEC doesn’t offer. B also seems plausible because GHEC’s cloud setup often includes data residency options that might not be possible with GHES, depending on where you host it yourself. A and D feel off given the nature of cloud vs self-hosted solutions. So between C and B, I’d pick C mainly for the control aspect since that’s a big selling point for GHES.

0
MX
Michael X.
2026-01-15

Maybe D, but isn’t GHES supposed to support external identity providers? That option seems off. Could someone clarify how GHES handles authentication compared to GHEC?

0