GH-200 Exam Dumps - GitHub Actions Exam

If a workflow depends on an external service that is down, disabling the workflow temporarily will prevent it from running and sending requests to the service, thus avoiding failed requests or unnecessary retries.

If a workflow is causing a negative impact on external services by generating too many requests or incorrect data due to a bug, temporarily disabling the workflow will stop this behavior while the issue is fixed.

GitHub Actions defines custom environment variables with the YAML env mapping. YAML mappings use a colon between each key and value, so MY_VARIABLE: my-value beneath env: is the correct syntax. The env key can appear at workflow, job, or step scope depending on how broadly the variable should be available. Options A, B, E, and F either use an unsupported key or the wrong assignment syntax. environment is associated with deployment environments when used in GitHub Actions workflow syntax; it is not the key for declaring ordinary environment variables. The vars context is used for configuration variables created through repository, organization, or environment settings, but var: is not the workflow syntax shown here. Therefore, option C correctly defines the requested custom environment variable.

================

When troubleshooting a self-hosted runner, you can access the _diag folder located in the self-hosted runner ' s installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.

GitHub permits deletion of a workflow run after the run has completed. GitHub ' s current documentation also states that a workflow run may be deleted when it is more than two weeks old. Therefore, option A is a correct general statement and option C is incorrect because GitHub does not impose a 30-day minimum. Deleting a workflow run also does not require repository administrator access; GitHub specifies that write access to the repository is sufficient, which eliminates option D. Option B is too broad because an actively pending or queued workflow run is not generally treated the same as a completed run for immediate deletion. Removing a workflow run also removes its associated logs, which is relevant when managing workflow history or sensitive output. Therefore, option A is the correct selection.

================

The most common way to target a major release version of a GitHub Action is to reference a version tag such as @v3. This allows the workflow to use updates within that major version while avoiding automatic jumps to a newer major version that might introduce breaking changes. Option A references a commit SHA, which is the safest and most immutable method, but it is not the most common way to target a major release version. Option B is not a standard action version reference. Option D omits a version entirely, which is unsafe and not recommended because the action reference is incomplete. This topic maps to action versioning, marketplace action consumption, and reliable workflow maintenance.

================