🔧 Creating Custom Actions - GH-ACTIONS Practice Questions

Create reusable actions: JavaScript actions, Docker actions, composite actions, and publishing to the Marketplace.

4Questions Available
1Exam Domains

Practice Custom Actions Questions Now

Start a timed practice session focusing on Creating Custom Actions topics from the GH-ACTIONS question bank.

Start GH-ACTIONS Practice Quiz →

GH-ACTIONS Custom Actions Question Bank (4 Questions)

Browse all 4 practice questions covering Creating Custom Actions for the GH-ACTIONS certification exam. Each question includes the full answer and a detailed explanation to help you understand the concepts.

  1. Question 1Author and Maintain Actions

    How do you publish a custom action to the GitHub Marketplace?

    AAutomatic publication
    BCreate action.yml with branding, tag a release, and publish through the repository's Marketplace tab✓
    CEmail GitHub
    DUpload to npm
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Publishing requires: action.yml with name/description/branding, a tagged release, and opting into Marketplace publication. The action appears in the Marketplace for discovery and use.

  2. Question 2Author and Maintain Actions

    What is the difference between JavaScript and Docker container actions?

    ASame type
    BJavaScript actions: run directly on runner (fast startup, cross-platform). Docker actions: run in container (any language/tools, Linux-only, slower startup due to image pull/build).✓
    CJS is Linux-only
    DDocker is cross-platform
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    JavaScript: runs on runner Node.js, fast start, works on all runner OSes (Linux, macOS, Windows). Use for: API calls, file operations, simple logic. Docker: any language, any dependencies, consistent environment, but Linux runners only and slower start (pull/build image). Use for: complex tools, specific language requirements, environment consistency. Both: inputs, outputs, and branding.

  3. Question 3Consume Workflows

    What are composite run steps in reusable workflows?

    ACannot combine
    BReusable workflows can contain multiple jobs with their own steps, and composite actions can combine run commands and action references into a single reusable unit✓
    COnly one step allowed
    DOnly shell commands
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Composite actions vs reusable workflows: Composite actions: combine steps (run + uses) into one action, referenced like any action (uses: ./my-action). Reusable workflows: full workflow with jobs, called via workflow_call (uses: org/repo/.github/workflows/ci.yml@main). Key differences: composite runs in caller's job, reusable runs as separate jobs. Choose composite for: step-level reuse. Choose reusable workflows for: job-level reuse with separate runners.

  4. Question 4Author and Maintain Actions

    What is the difference between Docker and JavaScript actions?

    ASame performance
    BDocker: run in container (any language, more dependencies, Linux-only runners, slower startup). JavaScript: run directly on runner (fast startup, cross-platform, Node.js only, lighter weight).✓
    COnly Docker works
    DOnly JavaScript works
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Docker actions: action.yml with runs: using: docker. Dockerfile defines environment. Benefits: any language, full dependency control, reproducible. Drawbacks: Linux runners only, slower (build/pull image), larger size. JavaScript actions: runs: using: node20. Benefits: fast startup, cross-platform (Linux/macOS/Windows), simpler. Drawbacks: Node.js only, dependency management (node_modules). Composite: combine run steps + action references, cross-platform, no container. Choose: Docker for complex environments, JS for speed, Composite for shell-based reuse.

Key Custom Actions Concepts for GH-ACTIONS

custom actionjavascriptdockercompositemarketplacereusable

GH-ACTIONS Custom Actions Exam Tips

Creating Custom Actions questions in GH-ACTIONS are typically scenario-based. Focus on service-level decision making aligned to official exam objectives. Priority concepts: custom action, javascript, docker, composite, marketplace, reusable.

What GH-ACTIONS Expects

  • Anchor your answer in select the most practical, secure, and scalable answer for the stated scenario.
  • Custom Actions scenarios for GH-ACTIONS are frequently mapped to Domain 3 (20%), so read the objective carefully before picking controls or architecture.
  • Expect multi-service scenarios where Custom Actions interacts with IAM, networking, storage, or observability patterns rather than appearing as an isolated service question.
  • When two options are both technically valid, prefer the choice that best aligns with the exam's operational scope (Intermediate) and managed-service best practices.

High-Value Custom Actions Concepts

  • Know the core Custom Actions building blocks cold: custom action, javascript, docker, composite.
  • Review the edge-case features and limits for marketplace, reusable; these details are commonly used to differentiate answer choices.
  • Practice service-integration reasoning: how Custom Actions pairs with Workflow Syntax, CI/CD in real deployment patterns.
  • For GH-ACTIONS, explain why the chosen Custom Actions design meets reliability, security, and cost expectations better than the alternatives.

Common GH-ACTIONS Traps

  • Watch for answers that partially solve the requirement but miss operational constraints.
  • Questions in Author and Maintain Actions often include distractors that look correct for Custom Actions but violate least-privilege, durability, or availability requirements.
  • Avoid picking options purely by feature name; validate data path, failure handling, and governance impact before answering.
  • If the prompt hints at automation or repeatability, eliminate manual-only operational answers first.

Fast Review Checklist

  • Can you compare at least two Custom Actions implementation paths and justify which one best fits the scenario?
  • Can you map the chosen answer back to Author and Maintain Actions (20%) outcomes for GH-ACTIONS?
  • Can you explain security and access boundaries for Custom Actions without relying on default-open assumptions?
  • Can you describe how Custom Actions integrates with Workflow Syntax and CI/CD during failure, scaling, and monitoring events?

Exam Domains Covering Custom Actions

Domain 3Author and Maintain Actions20%

Related Resources

🎯 Free GH-ACTIONS Mock Exam📝 Workflow Syntax Questions📝 CI/CD Questions

More GH-ACTIONS Study Resources

← GH-ACTIONS Study Hub30-Day Study PlanFull Practice Exam