GitHub / Associate / GH-200
GitHub Actions
Design reproducible workflows, debug execution, package actions and secure automation across an organization.
The January 2026 exam outline mentions YAML merge mappings (<<). The current GitHub reuse documentation explicitly documents anchors and aliases; this guide explains merge semantics separately and does not assume every YAML feature is accepted by every Actions runtime. Validate actual workflows against current platform support.
THE REVISION PATH
Your topics, in order.
Read. Recall. Explain the alternative.
Events, Inputs and Workflow Trust
The trigger chooses both the event and the trust boundary.
Jobs, Matrices and Evaluation Context
Jobs form the graph; steps share a job; contexts supply data.
Outputs, Artifacts, Caches and Summaries
Outputs carry small values; artifacts carry deliverables; caches save repeat work.
Debugging Runs and Controlling Cost
Read the first meaningful failure before rerunning everything.
Reusable Workflows, Templates and Enterprise Policy
Copy a starter; call a workflow; compose steps in an action.
Custom Actions, Metadata and Releases
The action is a product with an interface and a supply chain.
Hosted and Self-Hosted Runner Operations
A runner is a security boundary and an operating responsibility.
Secrets, OIDC and Artifact Trust
Give the job a narrow identity, then verify what it produced.
How this guide is organised
Original revision notes arranged around practical decisions. The current official study guide defines the mapped scope; GitHub technical documentation supports the explanations. Read, recall without looking, then explain why another option would fail.
- Official exam guide ↗ Scope authority
Revision material supports preparation; it does not guarantee every possible exam question. Check the exam version and official objectives before booking.