GitHub · Associate

GitHub Actions (GH-200)

Author, maintain, and consume GitHub Actions workflows and custom actions to automate CI/CD pipelines and developer workflows.

GH-200 exam at a glance

Exam codeGH-200
VendorGitHub
LevelAssociate
Domains5
Published practice questions133
Our mock exam60 questions in 120 minutes
Our practice pass target70%
Checked against the exam guideSeptember 22, 2026
Official exam pageGitHub — GH-200

The mock exam length, time limit and pass target are our practice settings, not official exam scores or a guarantee of passing. Check the official GH-200 exam page for the current format, price and scoring before you book.

GH-200 exam domains

Weights show our practice allocation, built from the official exam guide; official blueprints may give ranges. Each domain links to its free sample questions (with explanations) and study guide preview once they are published.

Author and Manage Workflows

25%

Write, debug, and maintain GitHub Actions workflows for CI/CD and automation.

  • Workflow YAML structure: name, on, jobs, steps
  • Event triggers: push, pull_request, schedule (cron), workflow_dispatch, repository_dispatch
  • Job dependencies: needs, if conditions, continue-on-error
  • Expressions and contexts: github, env, secrets, vars, steps, jobs, runner contexts
  • Environment variables: env at workflow/job/step level, $GITHUB_ENV
  • Secrets: creating org/repo secrets, using in steps, GITHUB_TOKEN
  • Variables (vars context): repo and org-level, non-sensitive configuration
  • Artifacts: upload-artifact, download-artifact, retention
  • Caching: actions/cache, cache keys, restore keys, cache hit/miss
  • Matrix strategy: strategy.matrix, include/exclude, max-parallel, fail-fast
  • Reusable workflows: workflow_call, inputs, outputs, secrets: inherit
  • Composite actions: action.yml, using: composite, inputs/outputs
  • Concurrency groups: cancel-in-progress, preventing duplicate runs
  • Job outputs: steps outputs, job outputs, passing between jobs
  • Timeout and retry: timeout-minutes, retry-on-error patterns
  • Debugging: ACTIONS_STEP_DEBUG, ACTIONS_RUNNER_DEBUG, enabling debug logging

Free Author and Manage Workflows practice questions →Author and Manage Workflows study guide →

Consume and Troubleshoot Workflows

17%

Use and configure existing workflows, understand triggers and status checks.

  • Manually triggering workflows: workflow_dispatch inputs, types
  • Required status checks: branch protection, bypass actors
  • Workflow run history: logs, annotations, summary
  • Re-running workflows and failed jobs
  • Skipping workflows: [skip ci], paths/branches filters
  • Calling reusable workflows: uses, with, secrets
  • Deployment environments: approval gates, wait timer, deployment branches
  • GitHub Environments: environment secrets vs repo secrets, protection rules
  • Workflow badges: status badges in README
  • Monitoring workflow usage: billing minutes, storage

Free Consume and Troubleshoot Workflows practice questions →Consume and Troubleshoot Workflows study guide →

Author and Maintain Actions

18%

Build Docker container actions, JavaScript actions, and composite actions.

  • Action types: Docker container, JavaScript, composite
  • action.yml metadata: name, description, inputs, outputs, runs
  • JavaScript actions: @actions/core, @actions/github, toolkit packages
  • Docker actions: Dockerfile, entrypoint, arg passing
  • Composite actions: steps, using other actions, passing inputs/outputs
  • Publishing to Marketplace: versioning with tags, release management
  • Action versioning: pinning by SHA vs tag, major version tags (v3)
  • Testing actions locally: act tool, local runner testing
  • Security: avoid script injection, use intermediate env vars, pin actions
  • OpenID Connect (OIDC): requesting JWT tokens, cloud provider trust

Free Author and Maintain Actions practice questions →Author and Maintain Actions study guide →

Manage GitHub Actions for the Enterprise

25%

Configure Actions policies, self-hosted runners, and enterprise governance.

  • Actions policies: allowed actions (all, local, selected), disabling at org level
  • Self-hosted runner groups: assigning runners to orgs/repos
  • Runner labels: custom labels, targeting with runs-on
  • Runner autoscaling: ephemeral runners, just-in-time tokens
  • Identifying preinstalled software/tool versions on GitHub-hosted runners and installing more at runtime
  • GitHub Actions billing: minutes per plan, storage, cost tracking
  • Encrypted secrets and variables at org, repo, and environment scope
  • Audit log for Actions: workflow runs, runner registrations
  • IP allowlists: GitHub-hosted runner IP ranges
  • Required workflows: enforcing workflows at org level
  • Actions cache across orgs: cache isolation, cross-repo cache

Free Manage GitHub Actions for the Enterprise practice questions →Manage GitHub Actions for the Enterprise study guide →

Secure and Optimize Automation

15%

Harden workflows against supply-chain and injection risks, and tune them for cost and performance.

  • Environment protections and approval gates
  • Identifying trustworthy actions from the Marketplace
  • Mitigating script injection: sanitizing inputs, least-privilege permissions, safe shell quoting
  • GITHUB_TOKEN lifecycle: ephemeral, scoped permissions vs a PAT
  • OIDC (id-token permission) for cloud provider federation, eliminating long-lived cloud secrets
  • Pinning third-party actions to full commit SHAs vs floating tags
  • Enforcing action usage policies: allow/deny lists, required reviewers for unverified actions
  • Artifact attestations and provenance (e.g. SLSA) for deployment verification
  • Caching and artifact retention for efficiency, including via REST API
  • Strategies for scaling and optimizing workflow performance and cost

Free Secure and Optimize Automation practice questions →Secure and Optimize Automation study guide →

GH-200 FAQ

How is the GitHub Actions (GH-200) practice assessment configured?

Our practice format targets 60 questions in 120 minutes. Availability depends on the published question bank and is shown on this course page. Official exam question counts and formats may differ.

What does the 70% practice target mean?

Check the provider's current exam guide for official scoring. A practice percentage is not an official scaled score. DataCertPrep uses 70% as an internal practice target, not a prediction or guarantee of passing.

How should I assess my progress in GitHub Actions (GH-200)?

Use practice accuracy to find weak topics. Repeating familiar questions can inflate your score. Check coverage of the current objectives, practise hands-on tasks, and assess yourself on unseen questions.

What is the best way to study GitHub Actions (GH-200)?

Read the available guides, work through practice explanations, use flashcards and complete practical exercises. Take a timed assessment when available. Check the provider's current exam guide before booking your exam.

Should I use GH-200 exam dumps?

No. "Dumps" are questions copied or recalled from the live exam. Certification exams are covered by a candidate agreement that prohibits sharing or using them, and breaking it can lead to a revoked certification or a ban from future exams. Dumps are also often wrong, and they go out of date when the exam blueprint changes. Memorising answers does not build the skills the exam tests. Study the official GitHub exam guide and practise with original questions that explain each answer, such as the free sample questions linked on this page.