About the Exam

GH-200: GitHub Actions is an intermediate Microsoft certification exam for DevOps engineers, software developers, and IT professionals who work with GitHub Actions. It covers creating and maintaining workflows and actions, managing GitHub Actions at scale, and securing and optimizing automation for organizations and enterprises. Passing the exam demonstrates the ability to automate software development workflows with GitHub Actions and work with CI/CD, GitHub repositories, GitHub Packages, and third-party integrations.

Exam Topics

Author and manage workflows20–25%
Consume and troubleshoot workflows15–20%
Author and maintain actions15–20%
Manage GitHub Actions for the enterprise20–25%
Secure and optimize automation10–15%

How to Use This Practice Exam

Browse — Read each question, select your answer, and reveal the explanation.
Exam Mode — Simulate real exam conditions with a timed session and score report.
Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Get PDF

Learn More

Last updated April 17, 2026 at 7:11 PM

Topic filter

Retired questions

Question sort

QuestionQ1

Author and manage workflows

What is the output of the following event-trigger block in a workflow?

Question Image

A It throws a workflow syntax error, pointing to the types definition in issue_comment event.
B It runs the workflow when an issue or issue comment in the workflow's repository is created or modified.
C It runs the workflow when an issue is edited or when an issue comment created.
D It runs the workflow when an issue is created or edited, or when an issue or pull request comment is created.
E It throws a workflow syntax error, pointing to the types definition in issues event.

Explanation

GitHub Actions supports the issues event with the opened and edited activity types, and the issue_comment event with the created activity type. The issue_comment event applies to comments on both issues and pull requests. Consequently, the workflow runs when an issue is created (opened) or edited, or when a comment is created on an issue or pull request.

Learn more

GitHub Actions events that trigger workflows

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Author and manage workflows

You need to create a reusable GitHub Actions workflow template named ci.yml. The solution must ensure that ci.yml is shown in the GitHub Actions New workflow interface.

Where should ci.yml be stored?

A .github/workflow-templates
B .github/templates
C the root directory of each repository
D .github/workflows

Explanation

GitHub Actions workflow templates intended for the New workflow interface are placed in the workflow-templates directory of an organization’s .github repository. Standard executable workflow files instead use .github/workflows; template display also relies on an associated metadata file in the template directory.

Learn more

Creating workflow templates for your organization

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Consume and troubleshoot workflows

As a developer, you are using a Docker container action in your workflow. What must be in place for the action to run successfully?

A The job env must be set to a Linux environment.
B The action must be published to the GitHub Marketplace.
C The referenced action must be hosted on Docker Hub.
D The job runs-on must specify a Linux machine with Docker installed.

Explanation

Docker container actions must run on a Linux runner. For self-hosted runners, Docker must be installed; therefore, the job’s runs-on configuration must target a Linux machine with Docker available. GitHub’s workflow syntax documentation states that Docker container actions require a Linux runner and that self-hosted Linux runners require Docker to be installed.

Learn more

Workflow syntax for GitHub Actions

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

Author and maintain actions

When creating and managing custom actions in an enterprise environment, which of the following is a best practice?

A creating a separate repository for each action so that the version can be managed independently
B creating a separate branch in application repositories that only contains the actions
C creating a single repository for all custom actions so that the versions for each action are all the same
D including custom actions that other teams need to reference in the same repository as application code

Explanation

Custom actions intended for use by other teams should be kept in their own repositories. This decouples each action’s versioning, tracking, and release lifecycle from application code, allowing it to be managed independently.

Learn more

Managing custom actions — GitHub Enterprise Cloud Docs

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Consume and troubleshoot workflows

As a developer, you must integrate a GitHub Actions workflow with a third-party code-quality provider that uses the Checks API. How should you initiate a follow-up workflow?

A Add the workflow_run webhook event as a trigger for the workflow for the code quality integration name
B Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed
C Add the pull_request webhook event as a trigger for the workflow when the code quality integration is synchronized
D Add the deployment webhook event as a trigger for the workflow when the code quality integration is completed

Explanation

A third-party Checks API integration creates and updates a check run. GitHub Actions can trigger a workflow from the check_run event, including when the check run is completed, which provides the appropriate completion signal for the code-quality integration.

Learn more