Microsoft GH-200 - GitHub Actions Exam

The appropriate way to test a JavaScript action is to invoke that action from a GitHub Actions workflow and verify its behavior on an actual runner. GitHub ' s JavaScript-action documentation specifically demonstrates testing a newly created action by creating a workflow that references and executes it. This exercises the action ' s metadata, inputs, JavaScript entry point, runner behavior, outputs, and failure handling in the same environment where consumers will use it. @vercel/ncc or another bundler can package JavaScript and its dependencies into a distributable file, but bundling is not itself a functional test. A JavaScript action also does not need to be converted into a Docker container. Finally, actions/debug-javascript is not the documented mechanism for testing JavaScript actions. Therefore, option B provides the correct testing approach.

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

The provided event trigger block specifies two types of events:

For issues: the workflow triggers on opened or edited issues.

For issue_comment: the workflow triggers when an issue comment is created.

This configuration ensures the workflow will run when either an issue is opened or edited, or an issue comment is created.

You can enable specific actions for the organization by identifying them and providing version control, ensuring only trusted versions are used in workflows.

GitHub-verified actions can be enabled at the enterprise level, providing an extra layer of security by ensuring that only trusted actions are available to workflows.

Actions can be published to an internal marketplace, allowing organizations to share reusable actions securely within their enterprise without exposing them to the public.

GitHub provides the ACTIONS_STEP_DEBUG setting specifically for increasing the verbosity of workflow step logs. To enable it, create a repository secret or repository variable named ACTIONS_STEP_DEBUG and assign the value true. GitHub states that if both a secret and a variable with this name exist, the secret takes precedence. After the setting is enabled, newly triggered or re-run workflows display additional debugging events in their step logs. Simply defining ACTIONS_STEP_DEBUG under the workflow ' s env or defaults section does not activate GitHub ' s step-debugging mechanism. There is also no supported --actions-step-debug workflow invocation flag. For deeper runner-level diagnostics, GitHub provides the separate ACTIONS_RUNNER_DEBUG setting. Therefore, option C is the documented method for step debug logging.

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

Environment secrets are scoped to GitHub Actions environments and can be protected by environment protection rules. If an environment requires reviewers, a job that references that environment cannot access its environment secrets until the required approval is granted. This makes option A correct. Option B is incorrect because environment secrets are made available to jobs that reference the protected environment, not selectively to only one specific step by default. Option C is not the purpose of environment secrets; they are not specifically for connecting to GitHub Enterprise Server. Option D is also incorrect because GitHub environment secrets do not automatically pull from Azure Key Vault without additional integration or custom workflow logic. This topic covers environment protection, secrets, and deployment governance.

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

The correct trigger must use the pull_request event because the workflow is based on activity on a pull request. The specific activity is a label being added, so types: [labeled] is required. The deployment must target the releases branch, so the branch filter must be branches: - ' releases ' . The workflow must also run only when files under the apps folder change, so paths: - ' apps/** ' is the correct recursive path filter. Option A is invalid because pull_request_label is not a GitHub Actions event. Option B uses the wrong event, pull_request_review. Option C uses an incorrect branch/path combination. GitHub workflow syntax supports event activity types, branch filters, and path filters together.

The correct GitHub Actions context property for the short branch or tag name that triggered the workflow is github.ref_name. A job-level if: condition can use this context to control whether the job runs. Therefore, if: github.ref_name == ' feature-branch ' correctly limits the deploy job to the feature-branch branch. The other options use invalid context paths such as github.ref.name, github.branch_name, and github.branch.name; these are not recognized GitHub Actions properties. In exam terms, this question validates knowledge of workflow expressions, GitHub context variables, and conditional job execution. The important distinction is that github.ref contains the full ref path, while github.ref_name provides the branch or tag name directly.

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

A reusable workflow stored in another repository must be referenced using the repository owner, repository name, required .github/workflows/ directory, workflow filename, and a ref. GitHub documents the syntax as {owner}/{repo}/.github/workflows/{filename}@{ref}. Option B exactly follows this structure: octo-org identifies the owner, another-repo identifies the repository, the workflow resides under .github/workflows, and v1 supplies the branch, tag, or other valid ref. Options A and C omit the required .github/workflows path. Option D includes that directory but omits the repository owner, so it is not a valid cross-repository reference. Reusable workflows are invoked with jobs. < job_id > .uses, rather than through an ordinary step-level action reference. Therefore, option B is the only correctly formed external reusable workflow reference.

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

The first image shows a workflow trigger with an option for the test suite, and the chosen YAML configuration matches this interface. Specifically, the test suite input is defined with type: choice and includes the option value: functional, which aligns with the visible UI elements in the first image.

GitHub Actions supports the use of service containers, which allows you to spin up a PostgreSQL database (or any other service) in a Docker container during your workflow. You can pull a PostgreSQL image from Docker Hub, and the container will automatically be available to your workflow job. This method requires no additional infrastructure and is easy to configure and maintain, as you simply define the container in the workflow file.