Free GH-200 Exam Dumps Preview

[A, not B] Each GitHub-hosted runner is a new virtual machine (VM) hosted by GitHub with the runner application and other tools preinstalled, and is available with Ubuntu Linux, Windows, or macOS operating systems.

[E] When you use a GitHub-hosted runner, machine maintenance and upgrades are taken care of for you.

References:
https://docs.github.com/en/[email protected]/actions/concepts/runners/github-hosted-runners

[D] GitHub Actions now supports a concurrency key at both the workflow and job level that will ensure that only a single run or job is in progress. concurrency Use concurrency to ensure that only a single job or workflow using the same concurrency group will run at a time.
Example: Using concurrency and the default behavior.
The default behavior of GitHub Actions is to allow multiple jobs or workflow runs to run concurrently. The concurrency keyword allows you to control the concurrency of workflow runs.
For example, you can use the concurrency keyword immediately after where trigger conditions are defined to limit the concurrency of entire workflow runs for a specific branch: on: push: branches:
-main concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true
Incorrect:
[Not A, not E, Not F] actions-mutex
A GitHub Action for exclusive control.

FEATURE avoid running multiple jobs concurrently across workflows

OFFICIAL CONCURRENCY SUPPORT ON GITHUB ACTIONS
The action is no longer maintained.

On April 19, 2021, GitHub launched support for limiting concurrency in the workflow files

References:
https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency/
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#concurrency
https://github.com/marketplace/actions/actions-mutex

Using GitHub Actions with an IP allow list. If you use an IP allow list and would also like to use GitHub

Actions, you must use self-hosted runners or GitHub-hosted larger runners with static IP address ranges
To allow your self-hosted or larger hosted runners to communicate with GitHub, add the IP address or IP address range of your runners to the IP allow list that you have configured for your enterprise.
References:
https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization

Use GITHUB_TOKEN for authentication in workflows

At the start of each workflow job, GitHub automatically creates a unique GITHUB_TOKEN secret to use in your workflow. You can use the GITHUB_TOKEN to authenticate in the workflow job.

References:
https://docs.github.com/en/actions/tutorials/authenticate-with-github_token

[A] Some actions may require a GITHUB_TOKEN as an input to authenticate and perform specific tasks, such as creating issues, commenting on pull requests, or interacting with the GitHub API. In such cases, you would need to explicitly pass the token to the action.
[B] When making an authenticated GitHub API request, the GITHUB_TOKEN is required to authenticate the request. This token is automatically provided by GitHub in the workflow, and it must be explicitly used when interacting with the GitHub API.
Note: You can use the GITHUB_TOKEN to make authenticated API calls. This example workflow creates an issue using the GitHub REST API: name: Create issue on commit on: [ push ] jobs: create_issue: runs-on: ubuntu-latest permissions:

issues: write
steps:

-name: Create issue using REST API
run: |
curl --request POST \
--url
https://api.github.com/repos/${{
github.repository }}/issues \
--header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
--header 'content-type: application/json' \
--data '{

"title": "Automated issue for commit: ${{ github.sha }}", "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_." }' \ --fail
References:
https://docs.github.com/en/actions/tutorials/authenticate-with-github_token

Input parameters for the cache action

[C] key: Required.
The key created when saving a cache and the key used to search for a cache. It can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.
[A] path: Required.
The path(s) on the runner to cache or restore.
Incorrect: restore-keys: Optional
enableCrossOsArchive: Optional
References:
https://docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching

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.

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

GitHub Actions allows you to configure environment protection rules, where you can require specific users or teams to approve the deployment before the workflow proceeds to the next step. This ensures that the required reviewers approve the workflow before any sensitive actions (such as deployment) occur.

Note: Managing environments for deployment
You can create environments and secure those environments with deployment protection rules. A job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.

Optionally, you can specify people or teams that must approve workflow jobs that use this environment.

Select Required reviewers.
Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
Optionally, to prevent users from approving workflows runs that they triggered, select Prevent self-review.
Click Save protection rules.

References:
https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments

Monitoring and troubleshooting self-hosted runners
You can monitor your self-hosted runners to view their activity and diagnose common issues.

[A] Reviewing the self-hosted runner application log files You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the_diag directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with Runner_, and is followed by a UTC timestamp of when the application was started.
[D] You can choose one of the standard GitHub-hosted runner options or, if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU processor. These machines are referred to as "larger runner."

References:
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/monitor-and-troubleshoot
https://docs.github.com/en/actions/concepts/runners/github-hosted-runners

Scheduled workflows run on the latest commit on the default branch.

Note: The default branch is also the initial branch that Git checks out locally when someone clones the repository. Unless you specify a different branch, the default branch in a repository is the base branch for new pull requests and code commits.

References:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
https://docs.github.com/articles/about-branches

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.
References:
https://docs.github.com/en/actions/reference/security/secure-use

Variables reference
Find information for supported variables, naming conventions, limits, and contexts in GitHub Actions workflows.

Variables include:*GITHUB_REPOSITORY The owner and repository name. For example, octocat/Hello-
World*
Etc.
References:
https://docs.github.com/en/actions/reference/workflows-and-actions/variables

Defining environment variables for a single workflow To set a custom environment variable for a single workflow, you can define it using the env key in the workflow file. The scope of a custom variable set by this method is limited to the element in which it is defined. You can define variables that are scoped for: The entire workflow, by using env at the top level of the workflow file. The contents of a job within a workflow, by using jobs.<job_id>.env. A specific step within a job, by using jobs.<job_id>.steps[*].env.
References:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-variables

Matrix jobs multiply combinations of defined variables.
Example:

matrix:
node: [14, 16, 18]
os: [ubuntu-latest, windows-latest]

--->3 x 2 = 6 total runs.

To set an error message in a GitHub Actions runner's output, you should use the command echo
"::error::Your error message" in your workflow's run step. This workflow command creates an error annotation that will appear in the logs, and you can optionally include file and line number information,
such as echo "::error file=app.js,line=5::Error message".

Example Simple Error.

steps:
-name: My Step
run: echo "::error::Something went wrong in this step."

Error with File and Line Information. steps:
-name: My Step
run: echo "::error file=src/main.py,line=25::Invalid syntax detected."

References:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands