Free GitHub Actions Exam Braindumps
GitHub Actions Questions 26–30 (page: 7)

Updated On: 10-Feb-2026

You installed specific software on a Linux self-hosted runner. You have users with workflows that need to be able to select the runner based on the identified custom software.
Which steps should you perform to prepare the runner and your users to run these workflows? (Choose two.)

  1. Create the group custom-software-on-linux and move the runner into the group.
  2. Inform users to identify the runner based on the group.
  3. Add the label custom-software to the runner.
  4. Configure the webhook and network to enable GitHub to trigger workflow.
  5. Add the label linux to the runner.

Answer(s): B,C

Explanation:

Once the runner is properly configured and labeled, users should be informed to select the specific runner by identifying the label or group name when defining the runner in their workflows.

Adding a custom label (like custom-software) to the runner makes it easier for users to select the runner in their workflows by using the runs-on key, which allows them to choose this specific runner based on its label.



Your organization needs to simplify reusing and maintaining automation in your GitHub Enterprise Cloud.
Which components can be directly reused across all repositories in an organization? (Choose three.)

  1. self-hosted runners
  2. actions stored m private repositories in the organization
  3. encrypted secrets
  4. custom Docker actions stored in GitHub Container Registry
  5. actions stored in an organizational partition in the GitHub Marketplace
  6. workflow templates

Answer(s): B,C,F

Explanation:

Actions stored in private repositories within the organization can be reused across all repositories by referencing them in workflows. This ensures a centralized way of maintaining custom actions. Encrypted secrets can be accessed across repositories in the same organization, making it easy to store sensitive data (like API keys or tokens) securely while allowing multiple workflows to access them.
Workflow templates allow you to create reusable templates for workflows that can be shared across repositories within the organization. This makes it easier to standardize processes and automate them across multiple projects.



In which locations can actions be referenced by workflows? (Choose three.)

  1. a separate public repository
  2. an .action extension file in the repository
  3. the same repository as the workflow
  4. a published Docker container image on Docker Hub
  5. the runs-on: keyword of a workflow file
  6. the repository's Secrets settings page
  7. a public NPM registry

Answer(s): A,C,D

Explanation:

Actions can be stored in a separate public repository and referenced in workflows by specifying the repository and action name.
Actions can also be stored in the same repository as the workflow and referenced directly by their path (e.g., ./.github/actions/my-action).
Actions can be packaged as Docker container images and published to Docker Hub. These can then be referenced in workflows by specifying the Docker image.



As a developer, what options should you recommend to implement standards for automation reuse? (Choose two.)

  1. Create workflow templates and store them in the organization's .github repository.
  2. Create reusable actions and workflows that can be called from other workflows.
  3. Create a marketplace partition to publish reusable automation for the company.
  4. Store shared corporate actions in subfolders in a defined and documented internally accessible repository.

Answer(s): A,B

Explanation:

Creating workflow templates in the organization's .github repository allows the organization to standardize workflows and make them easily reusable across multiple repositories. This ensures consistency and simplifies maintenance.
Creating reusable actions and workflows that can be called from other workflows helps modularize and standardize automation tasks. These reusable components can be maintained centrally and called from different workflows across repositories.



As a developer, you need to make sure that only actions from trusted sources are available for use in your GitHub Enterprise Cloud organization.
Which of the following statements are true? (Choose three.)

  1. Specific actions can individually be enabled for the organization, including version information.
  2. GitHub-verified actions can be collectively enabled for use in the enterprise.
  3. Actions can be restricted to only those available in the enterprise.
  4. Actions created by GitHub are automatically enabled and cannot be disabled.
  5. Individual third-party actions enabled with a specific tag will prevent updated versions of the action from introducing vulnerabilities.
  6. Actions can be published to an internal marketplace.

Answer(s): A,B,F

Explanation:

You can enable specific actions for the organization by identifying them and providing version control, ensuring only trusted versions are used in workflows. GitHub-verified actions can be enabled at the enterprise level, providing an extra layer of security by ensuring that only trusted actions are available to workflows. Actions can be published to an internal marketplace, allowing organizations to share reusable actions securely within their enterprise without exposing them to the public.



Viewing page 7 of 16
Viewing questions 31 - 35 out of 115 questions


Post your Comments and Discuss GitHub GitHub Actions exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!