GitHub · GH-200
GitHub Actions (GH-200) Practice Tests
Validates proficiency in automating workflows and accelerating development with GitHub Actions, covering workflow creation, automation, CI/CD pipeline management, and enterprise-level strategies.
Exam Details
Practice Questions
310
≈ 4 practice exams
Duration
100 minutes
Passing Score
Not publicly disclosed
Difficulty
IntermediateLast Updated
Jan 2026
Topics Covered
Author and maintain workflows (40%)Consume workflows (20%)Author and maintain actions (25%)Manage GitHub Actions for the enterprise (15%)
GitHub Actions (GH-200) Practice Exam Preparation
Use this GH-200 practice exam to prepare for GitHub Actions (GH-200) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 310 questions for GitHub GH-200, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as Author and maintain workflows (40%), Consume workflows (20%), Author and maintain actions (25%), and Manage GitHub Actions for the enterprise (15%). Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
Exam Domain Breakdown
Author and manage workflows23%
Consume and troubleshoot workflows18%
Author and maintain actions18%
Manage GitHub Actions for the enterprise23%
Secure and optimize automation13%
Exam Overview
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.
Who Should Take This Exam
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.
Prerequisites
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.
Exam Format
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.
Skills Measured
- 1.Author and manage workflows (20–25%): Configure scheduled, manual, webhook, and repository event triggers; design job and step dependencies with conditional logic; use service containers, matrix strategies with include/exclude and fail-fast controls, YAML anchors and aliases, predefined contexts (github, runner, env, secrets, needs, matrix, etc.), and expression evaluation; manage caching, artifact retention, environment files (GITHUB_ENV, GITHUB_OUTPUT), job summaries via GITHUB_STEP_SUMMARY, and workflow status badges.
- 2.Consume and troubleshoot workflows (15–20%): Interpret workflow triggers and execution results from logs and run history; diagnose failed runs; analyze matrix expansions and selectively rerun individual matrix jobs; locate and download artifacts and logs via the UI and REST API; differentiate and consume starter workflows, reusable workflows (workflow_call), and composite actions; contrast disabling vs. deleting workflows.
- 3.Author and maintain actions (15–20%): Create and troubleshoot JavaScript, Docker, and composite custom actions; understand immutable actions rollout implications for version pinning and registry sources; define required metadata files and directory structure; implement workflow commands within actions; select public, private, or GitHub Marketplace distribution models; apply versioning and release strategies.
- 4.Manage GitHub Actions for the enterprise (20–25%): Define and govern reusable workflows and organization-level templates; configure organizational use policies and access controls; provision and monitor GitHub-hosted and self-hosted runners; apply IP allow lists, runner groups, and networking settings; manage encrypted secrets and variables at organization, repository, and environment scope; access and manage secrets programmatically via REST APIs; identify preinstalled software on hosted runners and install additional tools at runtime.
- 5.Secure and optimize automation (10–15%): Use environment protections and approval gates; mitigate script injection via input sanitization, least-privilege permissions, and proper shell quoting; configure granular GITHUB_TOKEN permissions and contrast with PATs; use OIDC tokens (id-token permission) for cloud provider federation to eliminate long-lived secrets; pin third-party actions to full commit SHAs; enforce action allow/deny lists; generate and verify artifact attestations and provenance (SLSA); optimize workflow performance through caching strategies and retention policy management via REST APIs.
Study Tips
- Work through the official Microsoft Learn path 'Automate your workflow with GitHub Actions' (learn.microsoft.com/training/paths/github-actions/) before anything else — it maps directly to the exam domains and is the resource Microsoft explicitly recommends in the study guide.
- Take the free official practice assessment on Microsoft Learn (linked from the GH-200 certification page) to calibrate your readiness. It mirrors the style and difficulty of real exam questions and identifies which of the five domains need the most attention.
- Build hands-on experience with the January 2026 exam updates: practice configuring OIDC token federation with a cloud provider (AWS, Azure, or GCP), pinning third-party actions to full commit SHAs, and generating artifact attestations. These topics were explicitly added in the most recent revision.
- Study the GitHub Actions documentation for workflow syntax (docs.github.com/actions/writing-workflows/workflow-syntax-for-github-actions) with special focus on matrix strategies (include/exclude, fail-fast, max-parallel), YAML anchors and aliases, and all predefined contexts — the exam tests nuanced knowledge of these features.
- Use the GitHub Actions VS Code extension during practice workflow authoring to get real-time YAML schema validation and metadata IntelliSense — the exam guide lists editor tooling proficiency as an assessable skill, and this reinforces correct syntax habits.
- Practice the enterprise management domain by setting up a GitHub organization in a free account and experimenting with runner groups, organization-level secrets, action usage policies (allow/deny lists), and required reviewers — these governance controls are weighted at 20–25% of the exam.
- Use the official exam sandbox at GHCertDemo.starttest.com to familiarize yourself with the exam interface and interactive question types before exam day, so UI mechanics do not cost you time during the real assessment.
Career Benefits
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.
Sample Questions
5 sample questions with answers and explanations. The full bank has 310 questions, enough for 4 full-length practice exams.
Preview — answers shown1. DataSecure Corporation needs to create a workflow that can be triggered manually by their release managers when they decide to deploy to production. The workflow should not run automatically on code changes. Which trigger configuration enables manual workflow execution?
Aon: manual_trigger
Bon: manual_run
Con: user_initiated
Don: workflow_dispatch
Explanation
The workflow_dispatch event enables manual triggering of workflows through the GitHub interface or API. This trigger allows authorized users to manually start workflow runs without requiring code changes or other automated events. The workflow_dispatch trigger can also accept input parameters that users can specify when manually starting the workflow, making it ideal for deployment scenarios where human oversight is required. The other options are not valid GitHub Actions trigger types and would result in workflow syntax errors.
2. CloudNative Solutions wants their deployment workflow to trigger whenever their automated testing system completes a check run on pull requests. The integration team needs to configure a webhook event that responds to external testing tool results. Which webhook event should they configure?
Aon: status_check
Bon: external_check
Con: check_run
Don: pull_request_review
Explanation
The check_run event triggers workflows when check runs are created, updated, or completed by external applications or GitHub Apps. This event is specifically designed for integrating with external testing tools, CI systems, or automated checks that report their status back to GitHub through the Checks API. When a check run completes, the workflow can respond by performing additional actions like deployments or notifications. The other options either don't exist as GitHub webhook events or serve different purposes in the GitHub Actions ecosystem.
3. TechVision Systems wants to automatically trigger their continuous integration workflow whenever developers push code changes to any branch in their repository. What configuration should they implement in their GitHub Actions workflow file?
AUse on: push in the workflow YAML
BEnable repository push notifications
CConfigure automatic push detection
DSet up manual workflow triggers
Explanation
The configuration on: push in the workflow YAML file is the correct method for triggering workflows on push events. This trigger specification tells GitHub Actions to execute the workflow whenever any push occurs to the repository. You can further customize this trigger by specifying particular branches, paths, or other conditions, but the basic on: push syntax establishes the fundamental push event trigger. The other options either use incorrect terminology or refer to configurations that don't exist in GitHub Actions. This approach ensures immediate workflow execution following code pushes, enabling rapid feedback for continuous integration processes.
4. AutomationFirst Corporation needs to conditionally execute a step in their workflow only when the current branch is the main branch. The DevOps team wants to prevent certain deployment steps from running on feature branches. What conditional syntax should they implement?
Acondition: github.branch == 'main'
Bif: current_branch == 'main'
Cwhen: branch.name == 'main'
Dif: github.ref == 'refs/heads/main'
Explanation
The correct syntax uses if: github.ref == 'refs/heads/main' to conditionally execute steps based on the current branch. The github.ref context variable contains the full reference name including refs/heads/ prefix for branches. This conditional prevents the step from executing unless the workflow is running on the main branch. The if condition can be applied to individual steps or entire jobs, providing flexible control over workflow execution based on various context variables like branch names, event types, or custom conditions.
5. ScaleTech Industries needs to optimize their testing processes by running their application tests across multiple operating systems, programming language versions, and configuration combinations simultaneously. What GitHub Actions feature enables parallel execution across different configurations?
AWorkflow scheduling mechanisms
BArtifact sharing between jobs
CMatrix build strategy
DConditional job execution
Explanation
The matrix build strategy in GitHub Actions allows running workflows in parallel across different configurations, such as multiple operating systems, programming language versions, or environment variables. By defining a matrix with different parameter combinations, GitHub Actions automatically creates separate job instances for each combination and executes them concurrently. This dramatically reduces testing time while ensuring comprehensive coverage across supported platforms and configurations. Matrix builds are essential for cross-platform applications and help identify compatibility issues early in the development process.
More GitHub Practice Exams
$17.99
One-time access to this exam
310 questions (4 practice exams' worth)
Unlimited timed exam simulations
Yours forever — no subscription
Detailed explanations
Free preview stays available