Microsoft • GH-200
Validates proficiency in automating workflows and accelerating development with GitHub Actions, covering workflow creation, automation, CI/CD pipeline management, and enterprise-level strategies.
Questions
310
Duration
100 minutes
Passing Score
Not publicly disclosed
Difficulty
IntermediateLast Updated
Jan 2026
The GitHub Actions certification (GH-200) is an intermediate-level credential issued by GitHub and delivered through Microsoft's certification ecosystem via Pearson VUE. It validates expertise in automating software development workflows using GitHub Actions, covering the full lifecycle from authoring event-driven workflows and custom actions to managing automation at enterprise scale. The exam was significantly updated in January 2026, adding new objectives around security hardening, OIDC federation, artifact attestations, and YAML tooling, reflecting the platform's rapid evolution.
The certification spans five functional domains: authoring and managing workflows, consuming and troubleshooting workflows, authoring and maintaining actions, managing GitHub Actions for the enterprise, and securing and optimizing automation. Candidates are assessed on practical skills such as configuring matrix strategies, implementing reusable workflows, scoping GITHUB_TOKEN permissions, pinning third-party actions to full commit SHAs, and enforcing organization-level action usage policies. The exam emphasizes applied problem-solving over theoretical knowledge, making hands-on experience with GitHub Actions a prerequisite to success.
This certification is designed for DevOps engineers, software developers, build and release engineers, platform engineers, and technical team leads who work with GitHub Actions at an intermediate or advanced level. Suitable candidates are already comfortable reading and writing YAML workflow files, understand CI/CD concepts, and have direct experience navigating GitHub repositories, workflow run logs, and Actions configuration.
The credential is particularly valuable for professionals responsible for designing and maintaining CI/CD pipelines, scaling automation infrastructure across teams, and enforcing security and governance policies within GitHub organizations and enterprises. Solution architects who specify automation strategies and students pursuing DevOps career paths are also recognized target roles by Microsoft.
There are no formal prerequisites or mandatory prior certifications required to sit for GH-200. However, the exam is pitched at an intermediate level, and Microsoft recommends that candidates have hands-on experience automating software development workflows with GitHub Actions before attempting it. Familiarity with CI/CD principles, GitHub repositories, GitHub Packages, and integrating third-party services is expected.
Candidates should be comfortable with YAML syntax (including anchors, aliases, and merge keys), understand GitHub-hosted and self-hosted runner behavior, and have working knowledge of security concepts such as encrypted secrets, environment protections, OIDC token-based cloud federation, and the GITHUB_TOKEN lifecycle. Completing the Microsoft Learn path 'Automate your workflow with GitHub Actions' is the officially recommended preparatory resource.
The GH-200 exam is administered by Pearson VUE and allows 100 minutes to complete. It is available in English, Spanish, Portuguese (Brazil), Korean, and Japanese, with an additional 30 minutes granted if the exam is taken in a non-native language. The exam is proctored and may include interactive components in addition to standard question types; candidates can preview the interface via the official exam sandbox at GHCertDemo.starttest.com before exam day.
A score of 700 or greater (on a scale typically up to 1000) is required to pass. The exact number of questions is not publicly disclosed by Microsoft, and the exam may include unscored pilot questions. If a candidate fails, a retake is permitted after a 24-hour waiting period; subsequent retakes follow Microsoft's standard retake policy. The exam is priced based on the country or region where it is proctored, with a typical cost of approximately $99 USD.
The GH-200 certification signals specialized proficiency in GitHub Actions to employers at a time when CI/CD automation skills are a standard expectation for mid- to senior-level DevOps, platform engineering, and build engineering roles. GitHub is one of the most widely used development platforms globally, and Actions has become a dominant workflow automation tool, making this credential directly relevant to a broad range of job descriptions. Certified professionals are well-positioned for roles including DevOps Engineer, Platform Engineer, Build and Release Engineer, and Software Automation Engineer.
Salary impact varies by region and experience level, but DevOps and automation-focused engineers in the United States typically earn between $120,000 and $180,000 USD annually, with the certification serving as a differentiator during hiring and promotion discussions. According to Pearson VUE's Value of IT Certification research, 32% of certified professionals receive salary increases after earning a credential, and 79% report producing higher quality work. Compared to broader cloud certifications, GH-200 is narrowly focused on GitHub's native toolchain, making it a strong complement to cloud provider certifications (AWS, Azure, GCP) rather than a replacement — candidates with both categories of credentials demonstrate end-to-end CI/CD and deployment pipeline expertise.
5 sample questions with correct answers and explanations. Start a practice session to test yourself across all 310 questions.
1. TokenPermissions Corporation needs to implement security hardening for their GitHub Actions workflows by applying principle of least privilege to token permissions. What approach provides optimal token permission management?
Explanation
Applying principle of least privilege to token permissions means granting only minimal permissions required for specific workflow tasks. Configure GITHUB_TOKEN permissions explicitly in workflows using permissions section, use repository-scoped tokens when possible instead of user-scoped tokens, implement environment-specific secrets for deployment scenarios, and regularly audit token usage to identify over-privileged access. This approach minimizes security risks by ensuring tokens cannot perform actions beyond their intended scope, reducing potential damage from compromised workflows or token exposure.
2. IssueAutomation Solutions wants to create workflows that respond to various issue activities including issue creation, labeling, assignment, and closure. They need comprehensive issue event handling for repository management automation. What issue events enable complete issue lifecycle automation?
Explanation
Issue events with specific types enable comprehensive issue lifecycle automation: issues: types: [opened, labeled, assigned, closed, reopened, edited]. Each type triggers workflows for specific issue activities, enabling automated responses like welcome comments for new issues, project board management for labeled issues, notification systems for assignments, and cleanup activities for closed issues. This granular event handling enables sophisticated repository management automation that responds appropriately to different issue lifecycle stages and maintains organized issue management processes.
3. SecureSecrets Management Corporation handles multiple types of sensitive information including database credentials, API keys, certificates, and deployment tokens. They need to implement a comprehensive secret management strategy that addresses different security requirements and access patterns. What approach provides the most secure and manageable secret handling?
Explanation
Using a combination of GitHub Secrets and external secret management systems provides comprehensive security while addressing different organizational needs. GitHub Secrets are ideal for workflow-specific credentials and integration tokens, while external systems like Azure Key Vault, AWS Secrets Manager, or HashiCorp Vault can handle enterprise-grade secret rotation, auditing, and compliance requirements. This hybrid approach allows organizations to leverage GitHub's integrated secret management for development workflows while maintaining enterprise security standards for critical infrastructure credentials. Integration between systems can be achieved through authentication workflows and secret synchronization processes.
4. StatusBadge Corporation wants to display their workflow status in their repository README file so that visitors can quickly see if their latest build is passing or failing. What should they add to their README to show a workflow status badge?
Explanation
A GitHub Actions status badge URL provides a visual indicator of workflow status that can be embedded in README files. The badge URL follows the format https://github.com/owner/repo/actions/workflows/workflow-file.yml/badge.svg and displays the current status of the workflow (passing, failing, or unknown). This badge automatically updates when workflow runs complete and provides a quick visual reference for the project's build status. The badge can be customized with different branches and includes click-through functionality to view detailed workflow results.
5. OrganizationWide Corporation wants to provide standardized workflow templates for their 200+ repositories to ensure consistent CI/CD practices across all development teams. The DevOps team needs a centralized way to distribute and maintain these templates. How should they implement organization-wide workflow templates?
Explanation
Creating a .github repository at the organization level with workflow files in the workflow-templates directory makes templates automatically discoverable through GitHub's interface. When teams create new workflows, they can select from organization templates alongside GitHub's default templates, ensuring consistent adoption of standardized practices. This approach provides centralized maintenance, automatic distribution, and seamless integration with GitHub's workflow creation process, making it easy for teams to adopt approved CI/CD patterns while maintaining organizational standards.
One-time access to this exam