Free Practice Questions for Microsoft GH-200 Exam

JavaScript action metadata supports the runs.pre property for specifying a script that executes before the action ' s main entry point. The optional runs.pre-if property controls whether that pre-script executes. Therefore, option B uses the correct metadata structure: pre identifies start.js, pre-if supplies the condition, and main identifies the principal action code. GitHub does not define start, start-if, before, or before-if metadata properties. Current GitHub documentation lists newer supported Node.js runtimes, such as Node.js 20 and Node.js 24, rather than the historical node16 shown in this exam item; however, the tested metadata structure remains pre, pre-if, and main. Thus, among the supplied options, B is structurally correct.

GitHub Actions uses the env key to define environment variables. The env mapping can be applied at the workflow, job, or individual step level. In option B, dbserver is defined directly beneath the step-level env key, making it available to that step ' s shell process. Because the example uses shell syntax appropriate to a Linux runner, $dbserver correctly references the environment variable from the run command. The variables and environment keys shown in options A and D are not valid substitutes for step-level env. Option C also uses an invalid list structure; env expects a mapping of variable names to values rather than name and value objects. Therefore, option B uses the supported GitHub Actions workflow syntax.

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

The action.yml file is the metadata file in a custom GitHub Action that defines the main entry point, including information such as the inputs, outputs, description, and the runs key that specifies the main entry point (e.g., a script or a Docker container).

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.

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.

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.

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

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.

The publish-npm job includes the JS-DevTools/npm-publish action, which is used to publish an npm package to an npm registry.

The publish-npm job has the needs: build directive, meaning it will only run after the build job successfully completes.

The simplest official GitHub Actions action type for running shell commands or shell scripts is a composite action. Composite actions allow an action author to combine one or more run steps and reusable workflow commands in an action.yml file without needing to package a Docker image or write a JavaScript action. Option B is correct because it directly supports shell-based automation. Option A is heavier because Docker container actions require a container image or Dockerfile. Option D is used when the action logic is written in JavaScript and executed with Node.js. Option C is incorrect because “Bash script action” is not an official GitHub Actions action type. This topic checks custom action types and reuse patterns.

When a workflow job targets an environment that has required reviewers, the job enters a waiting state until it is approved or rejected. GitHub Actions does not allow that waiting state to remain indefinitely. If the job is not approved within the allowed period, the workflow fails automatically. The correct duration is 30 days, making option C correct. Options A, B, and D do not match the GitHub Actions environment approval behavior. This is important for deployment governance because required reviewers can block access to protected environments and environment secrets, but pending approvals still have a maximum lifetime. This exam topic aligns with protected environments, deployment approvals, required reviewers, and workflow execution control.

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