2025 New GH-200 Exam Questions Real Microsoft Dumps [Q51-Q66]

GH-200 Microsoft

admin • November 10, 2025

2025 New GH-200 Exam Questions Real Microsoft Dumps [Q51-Q66]

Rate this post

2025 New GH-200 Exam Questions Real Microsoft Dumps

Course 2025 GH-200 Test Prep Training Practice Exam Download

NEW QUESTION 51
In GitHub Actions, how is the success or failure of a step determined by its exit code?

Exit codes are ignored and a maintainer sets the result manually

Zero exit code means success and any nonzero means failure

Success is controlled by continue-on-error rather than the exit code

Every exit code is a failure

GitHub Actions evaluates each step by the exit status of the process it runs. The runner marks a step successful when the command finishes with an exit status of 0. If the command returns any other code then the step is marked as failed and the job may stop depending on your workflow configuration.

NEW QUESTION 52
As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Each correct answer presents a complete solution. Choose two.)

Store the token as a GitHub encrypted secret in the same repo as the code. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

Store the token as a GitHub encrypted secret in the same repo as the code. Create a reusable custom GitHub Action to access the token by the microservice at runtime.

Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.

[B] Using a corporate secret store like HashiCorp Vault provides a secure, centralized location for sensitive information. GitHub Actions can then retrieve and store the token securely during deployment by setting it as an environment variable, ensuring the token remains secure and accessible at runtime.
[C] Storing the token as an organizational-level encrypted secret in GitHub ensures it is accessible across multiple repositories, minimizing management overhead. GitHub Actions can then use this secret during deployment by setting it as an environment variable, allowing the microservice to access it securely at runtime.

NEW QUESTION 53
You installed specific software on a Linux self-hosted runner. You have users with workflows that need to be able to select the runner based on the identified custom software. Which steps should you perform to prepare the runner and your users to run these workflows? (Each correct answer presents part of the solution. Choose two.)

Configure the webhook and network to enable GitHub to trigger workflow.

Create the group custom-software-on-linux and move the runner into the group.

Inform users to identify the runner with the labels custom-software and linux.

Add the label linux to the runner.

Inform users to identify the runner based on the group.

Add the label custom-software to the runner.

[F] Add a label for the custom software as required.
Note: Using labels with self-hosted runners
You can use labels to organize your self-hosted runners based on their characteristics.
Creating a custom label
You can create custom labels for runners at the repository and organization levels.
[C, not D] Linux is a default label and does not have to be created to be used.
Reference:
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/apply-labels

NEW QUESTION 54
What is the right method to ensure users approve a workflow before the next step proceeds?

creating a branch protection rule and only allow certain users access

granting users workflow approval permissions

adding users as required reviewers for an environment

granting users repository approval permission

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.
Reference:
https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage- environments

NEW QUESTION 55
Which scopes are available to define custom environment variables within a workflow file?
(Choose three.)

the entire workflow, by using env at the top level of the workflow file

all jobs being run on a single Actions runner, by using runner.env at the top of the workflow file

the entire stage, by using env at the top of the defined build stage

within the run attribute of a job step

the contents of a job within a workflow, by using jobs.env

a specific step within a job, by using jobs..steps[*].env

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:
[A] The entire workflow, by using env at the top level of the workflow file.
[E] The contents of a job within a workflow, by using jobs.<job_id>.env.
[F] A specific step within a job, by using jobs.<job_id>.steps[*].env.
Reference:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use- variables

NEW QUESTION 56
Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

passing the GITHUB_TOKEN secret to an action that requires a token as an input

making an authenticated GitHub API request

checking out source code with the actions/checkout@v3 action

assigning non-default permissions to the 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:
Reference:
https://docs.github.com/en/actions/tutorials/authenticate-with-github_token

NEW QUESTION 57
What repository visibility is required for a GitHub Action to be listed on GitHub Marketplace?

Verified creator status

Metadata in a subfolder

Public repository

Use GitHub Container Registry

GitHub only lists actions from repositories that are visible to everyone. This is a firm requirement for publishing an action to the Marketplace and private or internal repositories cannot be listed.

NEW QUESTION 58
As a developer, you need to leverage Redis in your workflow. What is the best way to use Redis on a self-hosted Linux runner without affecting future workflow runs?

Install Redis on the hosted runner image and place it in a runner group. Specify label: in your job to target the runner group.

Set up Redis on a separate machine and reference that instance from your job.

Specify container: and services: in your job definition to leverage a Redis service container.

Add a run step to your workflow, which dynamically installs and configures Redis as part of your job.

Creating Redis service containers
You can use service containers to create a Redis client in your workflow. You can create a Redis service for jobs that run in containers or directly on the runner machine.
Configuring the runner job
The example uses the ubuntu-latest GitHub-hosted runner as the Docker host.
The workflow configures a service container with the label redis.
jobs:
# Label of the runner job
runner-job:
# You must use a Linux environment when using service containers or container jobs runs-on: ubuntu-latest
# Service containers to run with `runner-job`
services:
# Label used to access the service container
redis:
# Docker Hub image
image: redis
# Set health checks to wait until redis has started
options: >-
–health-cmd “redis-cli ping”
–health-interval 10s
–health-timeout 5s
–health-retries 5
ports:
# Maps port 6379 on service container to the host
– 6379:6379
Reference:
https://docs.github.com/en/actions/tutorials/use-containerized-services/create-redis-service- containers

NEW QUESTION 59
Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

passing the GITHUB_TOKEN secret to an action that requires a token as an input

making an authenticated GitHub API request

checking out source code with the actions/checkout@v3 action

assigning non-default permissions to the GITHUB_TOKEN

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.

NEW QUESTION 60
Which action type should be used to bundle a series of run steps into a reusable custom action?

Composite action

Bash script action

Docker container action

JavaScript action

Reusable workflows versus composite actions
Reusable workflows and composite actions both help you avoid duplicating workflow content.
Whereas reusable workflows allow you to reuse an entire workflow, with multiple jobs and steps, composite actions combine multiple steps that you can then run within a job step, just like any other action.
A composite action allows you to bundle multiple steps into a single reusable action within a workflow. It is composed of multiple run steps or other actions and can be reused across workflows, making it the perfect choice for bundling a series of steps.
Reference:
https://docs.github.com/en/actions/concepts/workflows-and-actions/reusable-workflows

NEW QUESTION 61
Which action type should be used to bundle a series of run steps into a reusable custom action?

Composite action

Docker container action

JavaScript action

Bash script action

NEW QUESTION 62
As a developer, you want to run a workflow from the Actions tab in GitHub. Which YAML snippet should you use to match the interface in this image?

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.

NEW QUESTION 63
Which of the following is the best way for an enterprise to prevent certain marketplace actions from running?

Create a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.

It is not possible; if an action is in the marketplace, its use cannot be restricted.

Create a list that is maintained as a . yml file in a . github repository specified in the enterprise.
Only these actions can be run.

Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.

The best way for an enterprise to control which GitHub Actions run is by creating a list of approved actions as an enterprise policy. This approach restricts workflows to only use the actions that are explicitly allowed, ensuring security and compliance within the organization.
Note: To allow a specific list of actions at the GitHub Enterprise level, an administrator must navigate to Enterprise > Policies > Actions and select “Allow select actions”. Then, from the dropdown menus, they choose “Allow selected actions and reusable workflows” and add the desired actions to the allowed list using the format OWNER/REPOSITORY@TAG-OR-SHA.
These actions can also include local actions, actions from specific organizations, or specific tags or commit SHAs.
Reference:
https://docs.github.com/en/enterprise-cloud@latest/admin/enforcing-policies/enforcing-policies- for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise

NEW QUESTION 64
As a developer, which of the following snippets will enable you to run the commands npm ci and npm run build as part of a workflow?

– run: |
npm ci
npm run build

– shell:
npm ci
npm run build

– run: |
npm ci
npm run build
shell: nodejs

– run:
npm ci
npm run build

– shell: |
npm ci
npm run build

Use the run: keyword only, not the shell keyword.
Use the special character |.
Note: There are two ways to run commands one after another on Github Actions.
Reference:
https://stackoverflow.com/questions/71047777/how-to-run-two-commands-on-github-actions- instance-one-after-another

NEW QUESTION 65
Which of the following scenarios would require the use of self-hosted runners instead of GitHub-hosted runners?

running more than the three concurrent workflows supported by GitHub-hosted runners

exceeding 50,000 monthly minutes of build time

using Docker containers as part of the workflow

using specialized hardware configurations required for workflows

performing builds on macOS

GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free-tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency.
Self-hosted runners allow you to configure specialized hardware or software setups that are necessary for certain workflows. GitHub-hosted runners may not have access to custom hardware configurations like GPUs or other specialized resources, so self-hosted runners are required in such cases.

NEW QUESTION 66
You need to trigger a workflow using the GitHub API for activity that happens outside of GitHub.
Which workflow event do you use?

workflow_run

deployment

check_suite

repository_dispatch

You can use the GitHub API to trigger a webhook event called repository_dispatch when you want to trigger a workflow for activity that happens outside of GitHub .
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

Loading …