GH-200 Exam Dumps - GitHub Actions Exam

The runs-on keyword allows you to specify the operating system and other labels for the runner. By specifying self-hosted, windows, and x64, you are targeting a self-hosted Windows runner that matches these criteria, which aligns with the custom configuration of your self-hosted runner.

GitHub environments provide deployment protection controls such as required reviewers. First, the Production environment should be created in the repository ' s Settings > Environments configuration, where the VMOps team can be configured as required reviewers. This makes option C correct; the environment is not created as an organization-level environment as described by option B. Second, the deployment job must reference the Production environment. GitHub applies the environment ' s protection rules to jobs that reference that environment, so the deployment remains in a waiting state until an authorized reviewer approves it. GitHub environments are logical deployment-control resources; individual VMs do not need to be added to an environment, nor is an environment “owned” by a team. Therefore, options A and C together implement the required production approval gate.

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

GitHub automatically creates a GITHUB_TOKEN for workflow jobs so the workflow can authenticate to GitHub without requiring a separately maintained personal access token for many repository-scoped operations. A common use is making authenticated REST API, GraphQL API, or GitHub CLI requests against resources that the token has permission to access. The token ' s capabilities are governed by the workflow ' s permissions configuration and the repository or organization policy. It is not an SSH credential for connecting to a runner, and it is not required merely to read encrypted repository secrets that GitHub makes available through the secrets context. Likewise, simply invoking a public Marketplace action does not inherently require explicitly passing GITHUB_TOKEN. Therefore, making authenticated GitHub API calls is the correct use described by option A.

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

The simplest correct choice is a run step. A run step executes shell commands or scripts directly on the runner inside the current workflow job environment. It does not require packaging a JavaScript action, building a Docker container, publishing an image, or creating reusable action metadata. A JavaScript action is appropriate when you are building a reusable Node.js-based action. A Docker container action is useful when the execution environment must be packaged with dependencies, but it adds container overhead. A composite action is useful for reusable sequences of steps, but the question asks only for running a custom script inside the workflow environment. GitHub workflow syntax shows run steps as the native way to execute commands inside a job.

Searching the GitHub Marketplace for verified actions published by the cloud provider is the quickest and safest approach. Many cloud providers offer verified GitHub Actions that are maintained and optimized to interact with their services. These actions typically come with the correct configurations and best practices, allowing you to get started quickly without reinventing the wheel.

Caching is ideal for files that change rarely, such as dependencies or build outputs, as it speeds up subsequent workflow runs by reusing previously cached files instead of re-downloading or rebuilding them.

Artifacts are used for persisting files produced during a job that need to be used in later jobs or after the workflow has ended, allowing them to be downloaded or referenced later.

The GITHUB_ACTOR environment variable indicates the name of the person or app that initiated the workflow. This variable is automatically provided by GitHub in the workflow and can be used to identify the user or application triggering the workflow.

GitHub Actions provides the concurrency mechanism for preventing overlapping workflow runs or jobs that share the same concurrency group. A workflow can define a concurrency group associated with a deployment target so that only one matching deployment is running at a time. The deployment job should also reference the target GitHub environment, such as production, so GitHub can associate the job with that deployment environment and apply its deployment controls. GitHub ' s documentation specifically describes using concurrency to ensure that an environment has a maximum of one deployment in progress at a time. GitHub does not provide the mutex configuration described in options A, B, and F, and concurrency is not configured simply by assigning the numeric value 1. Therefore, specifying the concurrency scope together with the target environment is the appropriate solution.

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