Microsoft · 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
≈ 6 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 Microsoft 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 6 full-length practice exams.
Preview — answers shown1. ContinueOnError Corporation has workflows where certain steps may fail without affecting overall workflow success. They need some steps to be allowed to fail while others must succeed for workflow completion. What mechanism enables selective step failure tolerance?
AUse external error handling systems without GitHub-native failure tolerance
BUse try-catch logic in all workflow steps for comprehensive error handling
CUse continue-on-error: true for specific steps that can fail without stopping workflow
DUse separate workflows for steps that might fail to isolate failure impact
Explanation
The continue-on-error: true parameter allows specific steps to fail without stopping workflow execution or causing overall workflow failure. Use this for optional steps like non-critical testing, experimental features, or informational tasks that shouldn't block main workflow progress. Combine with if: success() or if: failure() conditions on subsequent steps to implement sophisticated error handling logic. This selective failure tolerance enables resilient workflows that complete successfully even when optional components fail, supporting robust automation with graceful degradation.
2. DistributedActions Solutions has developed several custom actions that provide core functionality for their development workflows. They want to make these actions available across their enterprise while maintaining proper version control and access controls. What is the best approach for distributing actions within their enterprise?
ACreate internal action repositories with appropriate access permissions
BPublish actions to GitHub Marketplace for public access
CUse Git submodules to share action code across repositories
DInclude action code directly in each consuming repository
Explanation
Creating internal action repositories with appropriate access permissions is the best approach for enterprise action distribution. This method allows organizations to maintain version control, access controls, and proper documentation for their custom actions. Internal repositories can be made accessible to specific teams or the entire organization while keeping proprietary logic secure. Actions can be referenced using the repository/action-name@version syntax, enabling proper versioning and updates. This approach provides the benefits of code reuse and centralized maintenance while maintaining enterprise security requirements.
3. ProxyConfiguration Industries operates in a corporate environment with mandatory proxy servers and firewall restrictions. Their self-hosted runners need to communicate with GitHub services through corporate network infrastructure. How should they configure proxy settings for self-hosted runners?
AUse VPN connections exclusively without proxy configuration for GitHub service access
BImplement external gateway services without runner-level proxy configuration
CSet HTTP_PROXY and HTTPS_PROXY environment variables with appropriate proxy configurations
DConfigure runners with direct internet access bypassing all proxy requirements
Explanation
Configure self-hosted runners with proxy settings using HTTP_PROXY and HTTPS_PROXY environment variables pointing to corporate proxy servers (export http_proxy=http://proxy.company.com:8080). Include NO_PROXY settings for localhost and internal addresses that should bypass proxy. Apply these settings system-wide or in runner service configuration to ensure GitHub service communication works properly. Proxy configuration enables runners to register with GitHub, download actions, upload artifacts, and report job status while complying with corporate network security policies and firewall requirements.
4. CommandFlow Industries wants their workflow to output custom messages and set environment variables that can be used by subsequent steps. The development team needs to implement workflow commands to communicate with the runner environment. Which syntax correctly sets an environment variable named API_ENDPOINT?
Aecho '::set-env name=API_ENDPOINT::https://api.example.com'
Becho 'API_ENDPOINT=https://api.example.com' >> $GITHUB_ENV
Cexport API_ENDPOINT=https://api.example.com
Dset-env name=API_ENDPOINT value=https://api.example.com
Explanation
The correct syntax for setting environment variables in GitHub Actions is to append the variable assignment to the $GITHUB_ENV file using echo 'VARIABLE_NAME=value' >> $GITHUB_ENV. This method makes the environment variable available to subsequent steps in the same job. The $GITHUB_ENV file is a special file that GitHub Actions monitors for environment variable assignments. The older ::set-env:: workflow command syntax has been deprecated for security reasons, and simple export commands only work within the current step.
5. ActionBranding Solutions is preparing to publish their custom GitHub Action to the marketplace and wants to ensure professional presentation and discoverability. What branding and metadata elements enhance action marketplace presentation?
AOnly name and description are sufficient for marketplace presentation without additional metadata
BExternal branding systems without GitHub marketplace native metadata support
CComprehensive branding including icon, color, description, author, and category information
DBasic functionality without presentation considerations for marketplace publishing
Explanation
GitHub Actions marketplace presentation uses comprehensive branding metadata in action.yml including icon (from Feather icon set), color (theme color), description (detailed explanation), author (creator information), and categories for discoverability. Additional elements include comprehensive README.md documentation with usage examples, proper semantic versioning, clear input/output documentation, and support information. Professional branding improves action adoption rates, helps users find appropriate actions, and establishes creator credibility in the GitHub Actions ecosystem.
More Microsoft Practice Exams
Microsoft Certified: Dynamics 365 Supply Chain Management Functional Consultant Associate (MB-330)
MB-330 · 920 questions
Microsoft 365 Certified: Endpoint Administrator Associate (MD-102)
MD-102 · 723 questions
Microsoft Certified: Fabric Data Engineer Associate (DP-700)
DP-700 · 819 questions
GitHub Administration (GH-100)
GH-100 · 447 questions
GitHub Advanced Security (GH-500)
GH-500 · 299 questions
GitHub Copilot (GH-300)
GH-300 · 352 questions
$17.99
One-time access to this exam
310 questions (6 practice exams' worth)
Unlimited timed exam simulations
Yours forever — no subscription
Detailed explanations
Free preview stays available