Free GH-200 Exam Braindumps
GitHub Actions Questions 21–25 (page: 6)

Updated On: 16-Nov-2026

Which workflow event is used to manually trigger a workflow run?

  1. status
  2. workflow_dispatch
  3. workflow_run
  4. create

Answer(s): B

Explanation:

Manually running a workflow
When a workflow is configured to run on the workflow_dispatch event, you can run the workflow using the Actions tab on GitHub, GitHub CLI, or the REST API.
Configuring a workflow to run manually
To run a workflow manually, the workflow must be configured to run on the workflow_dispatch event.
To trigger the workflow_dispatch event, your workflow must be in the default branch.


Reference:

https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manually-run-a-workflow



Which choices represent best practices for publishing actions so that they can be consumed reliably? (Each correct answer presents a complete solution. Choose two.)

  1. default branch
  2. commit SHA
  3. repo name
  4. tag
  5. organization name

Answer(s): B,D

Explanation:

Security practices for writing workflows and using GitHub Actions features.
You can help mitigate this risk by following these good practices:
[B] Pin actions to a full-length commit SHA
Pinning an action to a full-length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[D] Pin actions to a tag only if you trust the creator
Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on GitHub Marketplace is a useful signal, as it indicates that the action was written by a team whose identity has been verified by GitHub. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.


Reference:

https://docs.github.com/en/actions/reference/security/secure-use



As a developer, you need to integrate a GitHub Actions workflow with a third-party code quality provider that uses the Checks API. How should you trigger a follow-up workflow?

  1. Add the workflow_run webhook event as a trigger for the workflow for the code quality integration name
  2. Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed
  3. Add the pull_request webhook event as a trigger for the workflow when the code quality integration is synchronized
  4. Add the deployment webhook event as a trigger for the workflow when the code quality integration is completed

Answer(s): B

Explanation:

The check_run event is triggered when a check (such as a code quality check) completes, including when the status of a check changes. By adding this event as a trigger, you can initiate a follow-up workflow when the code quality integration finishes its checks.


Reference:

https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows



Which statement accurately describes using labels to route GitHub Actions workflows to runners?

  1. A user can assign multiple labels to a self-hosted runner and use the labels in a runs-on to target only runners that match all the specified labels.
  2. Labels apply only to GitHub-hosted runners and are ignored by self-hosted runners.
  3. GitHub Actions automatically assigns the runner's IP address as a label, and the label must be used in a runs-on.
  4. To target a specific runner, the runs-on must match the runner's hostname rather than its labels.

Answer(s): A

Explanation:

GitHub Actions routes jobs to specific runners by matching the labels defined in the workflow's runs-on key with the labels assigned to available runners. For a job to be assigned to a runner, that runner must possess all of the labels specified in the workflow's routing array
Standard Label Matching Logic
When you write a job, you define a target list of labels using the runs-on keyword.
jobs:
build:
runs-on: [self-hosted, linux, gpu]
steps:
- run: echo "Running a GPU intensive task on Linux!"
For this job to clear the queue, GitHub searches for an active runner where:
It has the label self-hosted AND
It has the label linux AND
It has the label gpu
If a runner only has [self-hosted, linux], it will be ignored. The runner can possess extra labels not requested by the workflow, but it must strictly contain at least the exact subset you specified.


Reference:

https://docs.github.com/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-self-hosted-runn ers/using-self-hosted-runners-in-a-workflow



Which of the following is the lowest repository permission you need to have for downloading workflow artifacts?

  1. Triage
  2. Admin
  3. Maintain
  4. Write
  5. Read

Answer(s): E

Explanation:

Downloading workflow artifacts
You can download archived artifacts before they automatically expire.
Who can use this feature?
People who are signed into GitHub and have read access to a repository can download workflow artifacts.


Reference:

https://docs.github.com/en/actions/how-tos/manage-workflow-runs/download-workflow-artifacts



Viewing page 6 of 28
Viewing questions 26 - 30 out of 134 questions


Post your Comments and Discuss Microsoft GH-200 exam prep with other Community members:

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