Skip to content

GitHub Actions Study Strategy

Study Approach

Phase 1: Workflow Authoring (Weeks 1-2)

  1. Workflow Fundamentals
  2. YAML syntax and workflow file structure
  3. Event triggers (push, pull_request, schedule, workflow_dispatch)
  4. Trigger filters (branches, paths, tags)
  5. Jobs, steps, and runner selection

  6. GITHUB_TOKEN and permissions

  7. Expressions and Conditionals

  8. Expression syntax ${{ }}
  9. Contexts: github, env, secrets, inputs, steps, needs, matrix
  10. Status functions: success(), failure(), always(), cancelled()

  11. Conditional execution with if on jobs and steps

  12. Advanced Workflow Features

  13. Matrix strategies (combinations, include/exclude, fail-fast)
  14. Artifacts (upload/download between jobs)
  15. Caching dependencies
  16. Concurrency controls
  17. Reusable workflows (workflow_call)
  18. Job outputs and dependencies (needs)
  19. Environment variables and secrets

Phase 2: Actions Development (Weeks 2-3)

  1. Consuming Actions
  2. Finding actions on the Marketplace
  3. Pinning actions (SHA vs tag vs branch)
  4. Understanding action inputs and outputs

  5. Starter workflows and templates

  6. Creating Custom Actions

  7. JavaScript actions (Node.js, @actions/core toolkit)
  8. Docker container actions
  9. Composite actions (combining steps)
  10. action.yml metadata file
  11. Inputs, outputs, and environment files
  12. Publishing to the Marketplace
  13. Versioning with tags and releases

Phase 3: Enterprise and Exam Prep (Weeks 3-4)

  1. Enterprise Administration
  2. Self-hosted runners (setup, security, scaling)
  3. Runner groups and access control
  4. Organization and enterprise policies
  5. Allowed actions configuration
  6. Secrets at org and enterprise level
  7. OIDC for cloud deployments

  8. Audit logging and billing

  9. Practice Exams

  10. Take practice tests and review wrong answers
  11. Focus on workflow YAML syntax (40%)
  12. Review all event trigger types and filters

Study Resources

Primary Resources

Supplementary Resources

Community

  • GitHub Community Discussions - Q&A and tips
  • r/github - Reddit community
  • GitHub Blog - New features and announcements

Exam Tactics

Time Management (120 minutes, 65 questions)

  • Average ~1.8 minutes per question
  • Answer confident questions first
  • Flag uncertain questions for review
  • Reserve 15-20 minutes for flagged questions

Domain Prioritization

  • Author and Maintain Workflows (40%) - Primary focus
  • Author and Maintain Actions (25%) - Second priority
  • Consume Workflows (20%) - Know marketplace, pinning, templates
  • Manage for Enterprise (15%) - Self-hosted runners, policies, OIDC

Common Pitfalls

Study Mistakes

  • Not building real workflows - Theory alone is insufficient. Create workflows in a test repo
  • Ignoring enterprise features - 15% of the exam covers enterprise management
  • Not reading the docs - GitHub docs are excellent and exam questions reference them

Content Mistakes

  • Confusing pull_request vs pull_request_target security context
  • Not knowing that workflow_dispatch supports typed inputs
  • Confusing composite actions with reusable workflows
  • Not understanding job dependencies and data passing
  • Forgetting that Docker actions are Linux-only

Progress Tracking

Readiness Indicators

  • You can write workflow YAML from memory (triggers, jobs, steps, expressions)
  • You understand all event trigger types and their filter options
  • You can create all three action types (JS, Docker, composite)
  • You understand self-hosted runners and enterprise policies
  • You score 75%+ consistently on practice exams