| Topic | Details |
| Topic 1 | - Describe how GitHub is deployed, distributed, and licensed: This section of the exam measures skills of GitHub Enterprise Administrators and highlights the deployment models of GitHub Enterprise Server, Enterprise Cloud, and GitHub AE. It covers licensing structures, billing for seat licenses and metered services, support options, and monitoring license usage across users and machine accounts.
|
| Topic 2 | - Manage access and permissions based on membership: This section of the exam measures skills of DevOps Engineers and reviews how to manage organizations, teams, and repository permissions. It includes default permission settings, team synchronization through AD, scripting across multiple organizations, and aligning enterprise policies with trust requirements. It also contrasts roles such as organization members, owners, collaborators, and billing managers.
|
| Topic 3 | - Manage GitHub Packages:This section of the exam measures skills of GitHub Enterprise Administrators and focuses on managing GitHub Packages, their use in workflows, and how they differ from releases. It involves accessing, writing, and sharing packages across teams while ensuring integration into CI
- CD pipelines.
|
| Topic 4 | - Support GitHub Enterprise for users and key stakeholders: This section of the exam measures skills of GitHub Enterprise Administrators and covers supporting users, identifying issues that can be resolved internally versus those needing GitHub Support, and generating support bundles and diagnostics. It also involves recognizing underutilized features, managing workflows like branching and pull requests, understanding CI
- CD strategies, recommending tooling, and extending capabilities through APIs or Marketplace apps.
|
| Topic 5 | - Manage user identities and GitHub authentication: This section of the exam measures skills of DevOps Engineers and focuses on managing authentication and identity across organizations using SAML SSO, SCIM, and team synchronization. Candidates need to understand identity providers, user membership implications, authorization models, and enforcing security measures such as two-factor authentication.
|