Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Microsoft
Exam Format
100 min
Not publicly disclosed
700
Intermediate
Registration
Pearson VUE or online proctoring
English, Spanish, Portuguese (Brazil), Korean +1 more
Validity
2 years
Pass the current version of the exam before expiration; Complete Microsoft Learn renewal assessment (available 6 months before expiration)
GH-200 Exam Topics and Domains
GH-200 is organized into 4 weighted domains. Expect to work with GitHub Actions, GitHub Enterprise, Docker, Environments, and more.
1
Author and maintain workflows
40%
Work with events that trigger workflows
Configure workflows for one or more eventsConfigure scheduled eventsConfigure manual eventsConfigure webhook eventsDemonstrate GitHub event triggers based on practical use cases
- Configure workflows for one or more events
- Configure scheduled events
- Configure manual events
- Configure webhook events (check_run, check_suite, deployment, etc.)
- Demonstrate GitHub event triggers based on practical use cases
Use the components of a workflow
Identify correct syntax for workflow jobsUse job steps for actions and shell commandsUse conditional keywords for stepsDescribe how actions, workflows, jobs, steps, runs, and marketplace work togetherIdentify scenarios for GitHub-hosted vs. self-hosted runnersImplement workflow commands in run stepsDemonstrate dependent jobs
- Identify correct syntax for workflow jobs (indentation, encapsulation)
- Use job steps for actions and shell commands
- Use conditional keywords for steps
- Describe how actions, workflows, jobs, steps, runs, and marketplace work together
- Identify scenarios for GitHub-hosted vs. self-hosted runners
- Implement workflow commands in run steps
- Demonstrate dependent jobs
Use encrypted secrets and environment variables
Use encrypted secrets for sensitive informationIdentify available default environment variablesSet custom environment variables in workflowsIdentify when to use GITHUB_TOKEN secretUse workflow commands to set environment variables
- Use encrypted secrets for sensitive information
- Identify available default environment variables
- Set custom environment variables in workflows
- Identify when to use GITHUB_TOKEN secret
- Use workflow commands to set environment variables
Create a workflow for a particular purpose
Add scripts to workflowsPublish to GitHub PackagesPublish to GitHub Container RegistryUse database and service containersUse labels to route workflows to specific runnersUse CodeQL as a workflow stepPublish components as GitHub releasesDeploy releases to cloud providers
- Add scripts to workflows
- Publish to GitHub Packages
- Publish to GitHub Container Registry
- Use database and service containers
- Use labels to route workflows to specific runners
- Use CodeQL as a workflow step
- Publish components as GitHub releases
- Deploy releases to cloud providers
2
Consume workflows
20%
Interpret the effects of a workflow
Identify triggering events from repository/issue/PR effectsDescribe workflow effects from configuration filesDiagnose failed workflow runs using history and logsAccess workflow logs via UI and REST APIEnable step debug loggingUse default environment variablesPass custom environment variables in workflow steps
- Identify triggering events from repository/issue/PR effects
- Describe workflow effects from configuration files
- Diagnose failed workflow runs using history and logs
- Access workflow logs via UI and REST API
- Enable step debug logging
- Use default environment variables
- Pass custom environment variables in workflow steps
Manage workflow runs
Configure caching of workflow dependenciesPass data between jobsRemove workflow artifactsAdd workflow status badgesAdd environment protectionsDefine job configuration matricesImplement workflow approval gates
- Configure caching of workflow dependencies
- Pass data between jobs
- Remove workflow artifacts
- Add workflow status badges
- Add environment protections
- Define job configuration matrices
- Implement workflow approval gates
Locate a workflow, its logs, and artifacts
Describe workflow location in repositoryExplain disabling vs. deleting workflowsDownload workflow artifacts from UIUse organization's templated workflows
- Describe workflow location in repository
- Explain disabling vs. deleting workflows
- Download workflow artifacts from UI
- Use organization's templated workflows
3
Author and maintain actions
25%
Use available action types
Identify action type required (JavaScript, Docker container, run step)Troubleshoot JavaScript actionsTroubleshoot Docker container actions
- Identify action type required (JavaScript, Docker container, run step)
- Troubleshoot JavaScript actions
- Troubleshoot Docker container actions
Describe the components of an action
Identify required files and directory structureIdentify metadata and syntax requirementsImplement workflow commands within actions (including exit codes)
- Identify required files and directory structure
- Identify metadata and syntax requirements
- Implement workflow commands within actions (including exit codes)
4
Manage GitHub Actions for the enterprise
15%
Distribute actions and workflows to the enterprise
Explain reuse templates for actions and workflowsDefine approach for managing reusable componentsDistribute actions for enterpriseControl access to actions within enterpriseConfigure organizational use policies
- Explain reuse templates for actions and workflows
- Define approach for managing reusable components (repos, naming conventions, maintenance)
- Distribute actions for enterprise
- Control access to actions within enterprise
- Configure organizational use policies
Manage runners for the enterprise
Describe effects of IP allow lists on runnersSelect appropriate runners for workloadsExplain GitHub-hosted vs. self-hosted runner differencesConfigure self-hosted runners (proxies, labels, networking)Manage self-hosted runners using groupsMonitor, troubleshoot, and update self-hosted runners
- Describe effects of IP allow lists on runners
- Select appropriate runners for workloads
- Explain GitHub-hosted vs. self-hosted runner differences
- Configure self-hosted runners (proxies, labels, networking)
- Manage self-hosted runners using groups
- Monitor, troubleshoot, and update self-hosted runners
Manage encrypted secrets in the enterprise
Identify scope of encrypted secretsAccess encrypted secrets within actions and workflowsManage organization-level encrypted secretsManage repository-level encrypted secrets
- Identify scope of encrypted secrets
- Access encrypted secrets within actions and workflows
- Manage organization-level encrypted secrets
- Manage repository-level encrypted secrets
How do I earn this certification?
Passing GH-200 earns the GitHub Actions certification. It sits in the DevOps / CI-CD Automation track.
Next Level Options
- GH-300 - GitHub Advanced SecurityAdvanced GitHub certification focusing on security features
- AZ-400 - Designing and Implementing Microsoft DevOps SolutionsComplementary Microsoft DevOps certification
Alternative Paths
- GH-300 - GitHub Advanced SecurityAdvanced security features and code scanning with GitHub
- AZ-400 - Designing and Implementing Microsoft DevOps SolutionsComprehensive DevOps practices with Azure and GitHub integration
- AWS Certified DevOps Engineer - AWS Certified DevOps Engineer - ProfessionalCloud-specific DevOps practices for AWS environments
- CKA - Certified Kubernetes AdministratorContainer orchestration skills complementing CI/CD workflows
Practice with Precision
The PlanetCert Simulator mirrors the real exam environment with authentic questions and timed pressure.
How to study for this exam?
The most effective way to prepare for GH-200 is by using the PlanetCert Simulator to practice questions and review detailed explanations.
What's changed on this exam?
Current Status
- ACTIVE
- Last content update: 2025-12-22
- Announcement date: 2023-06-01
Updates
- Reusable Workflows Enhanced nesting support Now supports up to 10 nested reusable workflows and 50 total workflows per run • Release date: 2025-11-01
- Immutable Actions GA pending Actions stored as packages in GitHub Container Registry for enhanced security • Release date: Q1 2026
- Actions Data Stream Preview Near real-time workflow and job event data for observability • Release date: Q1 2026
- Scheduled Jobs Timezone Support Planned Better control over scheduled workflow timing • Release date: Q1 2026
Who should take this exam?
- Intermediate-level experience with GitHub Actions
- Experience creating and maintaining workflows
- Understanding of CI/CD concepts
- Familiarity with YAML syntax
- Knowledge of version control with Git
- Experience with automation and scripting