GH-100 Microsoft GitHub Administration Free Practice Exam Questions (2025 Updated)

Outside collaborators aren’t organization members; instead, they’re granted explicit access - at read, write, or admin level - to only the repositories you choose.

GitHub Enterprise gives you a suite of configurable controls - like a comprehensive audit log, enforced SAML single sign‑on, and enterprise‑level rulesets - that you can tailor and enforce to meet your organization’s compliance mandates.

Delete branch operations aren’t tracked as Git-activity events; the Git activity audit log only records Git events such as clone, fetch (pull), and push.

Use the Repository Settings → Manage Access page to view all users and teams with access and their assigned permission levels.

If you enable multiple rulesets that target the same branch, GitHub will evaluate every matching ruleset and enforce the aggregate of their rules - so all constraints from all applicable rulesets apply.

By using enterprise‑level teams with inherited enterprise policies, you can group members across all your organizations and enforce the same security settings globally - ensuring every team abides by the enterprise’s mandatory policies.

Business‑impact security issues (for example, a critical vulnerability affecting your organization) are classified as High‑priority tickets and are covered under your Premium Support SLA.

Outages on GitHub.com that disrupt core Git or web application functionality trigger Urgent‑priority responses under Premium Support’s SLA.

GitHub App Installation Access Tokens are privileged to the exact permissions you grant the App - down to individual repositories - and rotate automatically, making them the recommended choice for CI/CD automation workflows that demand least‑privilege, fine‑grained access.

CodeQL differs from traditional static analysis tools by ingesting your code into a queryable database and letting you write QL queries - its own database‑style language - to express semantic checks and find patterns across the codebase.

Dependabot relies on your repository’s enabled Dependency Graph and Dependabot Alerts to identify vulnerable dependencies; it then automatically opens pull requests to update to the patched versions that resolve those alerts.

GitHub Premium Support includes assistance with installing and using GitHub Enterprise Server, ensuring your deployment is configured correctly and any installation issues are resolved.

GitHub’s larger runners let you reserve dedicated static IP addresses for your workflows - so you can allow‑list those IPs in your firewall and be sure they aren’t shared with any other tenant.

GitHub Advanced Security equips developers with built‑in code scanning (CodeQL), secret scanning, dependency review, and other AppSec tools - helping them find, fix, and prevent security vulnerabilities while maintaining code quality.

Run the ghe-support-bundle command over SSH on your appliance and redirect its output to a file. For example:

ssh -p 122 admin@ghe.avocado.corp -- 'ghe-support-bundle -o' > support-bundle.tgz

This invokes the built‑in support‑bundle utility on your GitHub Enterprise Server instance and captures the resulting archive locally.

When you enforce the “Allow enterprise actions and reusable workflows” policy, GitHub will block all workflows from using actions or reusable workflows that aren’t defined in a repository within your enterprise - so only actions created inside your enterprise are allowed.

EMU accounts are provisioned and authenticated exclusively through your identity provider - users sign in via the IdP and cannot use or manage GitHub-native credentials.

Fine‑grained personal access tokens let you scope permissions down to individual repositories, whereas classic PATs grant access across every repo the user can reach.

Users granted Write permission can push commits to non‑protected branches, allowing them to update code without needing administrative rights.