Okay, this is where the vibe shifts. Administration is not a “skim the docs the night before” exam, it’s genuinely dense.
The core challenge here is scope. GitHub settings exist at three different levels repository, organization, and enterprise and this exam loves testing whether you know which setting lives where. On top of that, you’re expected to know SAML/SSO configuration, billing structures, org policies, and general governance stuff that, honestly, most individual developers never touch unless they’ve been handed the keys to an actual GitHub org.
What tripped me up: The repo vs. org vs. enterprise scoping, no contest. It’s incredibly easy to know that a setting exists but blank on which level it lives at. I got a few questions wrong in practice tests purely because I mixed up org-level policy inheritance with enterprise-level enforcement.
How I prepped: I basically built myself a cheat sheet three columns, repo/org/enterprise, and every setting I came across went into the right column. Sounds tedious, it was, but it’s the only thing that made the scoping stick. Beyond that, Microsoft Learn’s study guide plus GitHub Docs’ admin section were non-negotiable reading.
Who should take it: People who actually administer, or want to administer a GitHub org, DevOps leads, platform engineers, IT admins. If you’ve never touched org settings in real life, budget extra prep time here.
Resources