(Mar-2026) Latest GH-200 Dumps for Success in Actual Microsoft Certified
Changing the Concept of GH-200 Exam Preparation 2026
NEW QUESTION # 12
A workflow that had been working now stalls in a waiting state until failing. The workflow file process-ml.yaml has not changed and contains jobs specifying runs-on: [gpu ]. Which of the following steps would troubleshoot the issue? (Each answer presents a complete solution.
Choose two.)
- A. Rotate the GITHUB_TOKEN secret for the appropriate runners.
- B. Update the org settings to enable GPU-based GitHub-hosted runners.
- C. Check the "Set up job" step for the logs of the last successful run to determine the runner.
- D. Increase the usage limits for the GitHub-hosted runners.
- E. Review the contents of the Runner_*.log files in the _diag folder.
Answer: B,E
Explanation:
Monitoring and troubleshooting self-hosted runners
You can monitor your self-hosted runners to view their activity and diagnose common issues.
[A] Reviewing the self-hosted runner application log files
You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the _diag directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with Runner_, and is followed by a UTC timestamp of when the application was started.
[D] You can choose one of the standard GitHub-hosted runner options or, if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU processor. These machines are referred to as "larger runner." Reference:
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/monitor-and- troubleshoot
https://docs.github.com/en/actions/concepts/runners/github-hosted-runners
NEW QUESTION # 13
Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)
- A. checking out source code with the actions/checkout@v3 action
- B. passing the GITHUB_TOKEN secret to an action that requires a token as an input
- C. assigning non-default permissions to the GITHUB_TOKEN
- D. making an authenticated GitHub API request
Answer: B,D
Explanation:
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 # 14
As a developer, you need to add the correct syntax to allow the following workflow file to be triggered by multiple types of events. Which two code blocks should you add starting at line 5?
(Each correct answer presents a complete solution. Choose two.)
- A. on: [push, commit]
- B. on:
schedule:
- cron: '*/15 * * * *'
initiate:
- 'main' - C. on:
branches:
- 'main'
- 'dev' - D. on: [push, pull_request]
- E. on:
push:
branches:
- main
release:
types:
- created - F. on:
env:
- 'prod'
- 'qa'
- 'test'
Answer: B
Explanation:
To automatically trigger a workflow, use on to define which events can cause the workflow to run.
You can define single or multiple events that can trigger a workflow, or set a time schedule. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes.
[A] push and pull_request are both events that can trigger a workflow.
Note: Using multiple events
You can specify a single event or multiple events. For example, a workflow with the following on value will run when a push is made to any branch in the repository or when someone forks the repository:
on: [push, fork]
If you specify multiple events, only one of those events needs to occur to trigger your workflow. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered.
[C] on.schedule
You can use on.schedule to define a time schedule for your workflows.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
NEW QUESTION # 15
Which default environment variable specifies the branch or tag that triggered a workflow?
- A. GITHUB_REF
- B. GITHUB_TAG
- C. ENV_BRANCH
- D. GITHUB_BRANCH
Answer: A
Explanation:
The GITHUB_REF environment variable specifies the branch or tag that triggered the workflow. It contains the full reference to the branch or tag, such as refs/heads/main for a branch or refs/tags/v1.0 for a tag.
NEW QUESTION # 16
How can a workflow deploy mitigate the risk of multiple workflow runs that are deploying to a single cloud environment simultaneously? (Each correct answer presents part of the solution.
Choose two.)
- A. Specify a concurrency scope in the workflow.
- B. Specify a target environment in the deploymentjob.
- C. Configure the mutex setting in the environment.
- D. Pass the mutex into the deployment job.
- E. Reference the mutex in the task performing the deployment.
- F. Set the concurrency in the deploymentjob to 1.
Answer: A,B
Explanation:
[D] GitHub Actions now supports a concurrency key at both the workflow and job level that will ensure that only a single run or job is in progress.
concurrency
Use concurrency to ensure that only a single job or workflow using the same concurrency group will run at a time.
Example: Using concurrency and the default behavior
The default behavior of GitHub Actions is to allow multiple jobs or workflow runs to run concurrently. The concurrency keyword allows you to control the concurrency of workflow runs.
Reference:
https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency/
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#concurrency
https://github.com/marketplace/actions/actions-mutex
NEW QUESTION # 17
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.)
- A. 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.
- B. 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.
- C. Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
- D. 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.
- E. 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.
Answer: A,D
Explanation:
[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 # 18
You have exactly one Windows x64 self-hosted runner, and it is configured with custom tools. Which syntax could you use in the workflow to target that runner?
- A. runs-on: [self-hosted, windows, x64]
- B. runs-on: windows-latest
- C. self-hosted: [windows-x64]
- D. self-hosted: [windows, x64]
Answer: A
Explanation:
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.
NEW QUESTION # 19
Which of the following is the best way for an enterprise to prevent certain marketplace actions from running?
- A. Create a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.
- B. Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.
- C. Create a list that is maintained as a . yml file in a . github repository specified in the enterprise. Only these actions can be run.
- D. It is not possible; if an action is in the marketplace, its use cannot be restricted.
Answer: B
Explanation:
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.
NEW QUESTION # 20
Which GitHub Actions event configuration triggers only for pull requests targeting the release branch and not for push events?
- A. on: push: branches: - release
- B. on: pull_request: branches: - release
- C. on: pull_request_target: branches: - release
- D. on: pull_request: types: - opened
Answer: B
Explanation:
The correct option is on: pull_request: branches: - release. This configuration runs only when a pull request targets the release branch and it does not run on push events.
The pull_request event triggers on pull request activity and the branches filter matches the base branch of the pull request. By specifying the release branch, this configuration limits runs to pull requests that target that branch. Because it listens only for the pull_request event, pushes will not trigger the workflow.
NEW QUESTION # 21
Which default GitHub environment variable indicates the owner and repository name?
- A. REPOSITORY_NAME
- B. ENV_REPOSITORY
- C. GITHUB_WORKFLOW_REPO
- D. GITHUB_REPOSITORY
Answer: D
Explanation:
Variables reference
Find information for supported variables, naming conventions, limits, and contexts in GitHub Actions workflows.
Variables include:
* GITHUB_REPOSITORY
The owner and repository name. For example, octocat/Hello-World
* Etc.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/variables
NEW QUESTION # 22
An organization's policies specify only local actions are allowed. How should actions be distributed for this organization?
- A. via the .github repository owned by the organization
- B. via a repository owned by a third party
- C. via the GitHub Marketplace
- D. via repositories owned by the organization
Answer: D
Explanation:
Local GitHub Actions refer to two concepts: custom actions developed within your own repository and the process of running any GitHub Action locally on your machine for faster testing and debugging.
1. Local Actions (within your repository)
Definition:
These are custom actions that you define and store directly in your repository under the .github/actions/ directory. They are not publicly shared, unlike actions from the GitHub Marketplace.
Purpose:
They are used for project-specific, repetitive tasks that you want to reuse within your workflows without publishing them globally.
How it works:
You can call these local actions in your workflow files as if they were standard published actions.
2. Running Actions Locally (on your development machine)
Note:
Pinned repositories
You can give users easy access to important or frequently used repositories, by choosing up to six repositories for public users and six repositories for members of the organization. Once you pin repositories to your organization profile, the "Pinned" section is shown above the
"Repositories" section of the profile page.
Reference:
https://dev.to/codenamegrant/supercharging-your-workflows-with-local-github-actions-2o23
https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing- your-organizations-profile
NEW QUESTION # 23
In which scenarios could the GITHUB_TOKEN be used? (Each correct answer presents a complete solution. Choose two.)
- A. to create a repository secret
- B. to add a member to an organization
- C. to read from the file system on the runner
- D. to leverage a self-hosted runner
- E. to publish to GitHub Packages
- F. to create issues in the repo
Answer: E,F
Explanation:
[D] To authenticate to a GitHub Packages registry within a GitHub Actions workflow, you can use:
*-> GITHUB_TOKEN to publish packages associated with the workflow repository.
* A personal access token (classic) with at least read:packages scope to install packages associated with other private repositories (GITHUB_TOKEN can be used if the repository is granted read access to the package.
[E] 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/packages/learn-github-packages/introduction-to-github-packages
https://docs.github.com/en/actions/tutorials/authenticate-with-github_token
NEW QUESTION # 24
Custom environment variables can be defined at multiple levels within a workflow file including:
(Each answer presents a complete solution. Choose three.)
- A. stage level.
- B. default level.
- C. job level.
- D. top level.
- E. runner level.
- F. step level.
Answer: C,D,F
Explanation:
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:
The entire workflow, by using env at the top level of the workflow file.
The contents of a job within a workflow, by using jobs.<job_id>.env.
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 # 25
Which action type should be used to bundle a series of run steps into a reusable custom action?
- A. Bash script action
- B. Composite action
- C. Docker container action
- D. JavaScript action
Answer: B
Explanation:
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.
NEW QUESTION # 26
As a developer, you are optimizing a GitHub workflow that uses and produces many different files. You need to determine when to use caching versus workflow artifacts. Which two statements are true? (Choose two.)
- A. Use caching to store cache entries for up to 30 days between accesses.
- B. Use artifacts when referencing files produced by a job after a workflow has ended.
- C. Use artifacts to access the GitHub Package Registry and download a package for a workflow
- D. Use caching when reusing files that change rarely between jobs or workflow runs.
Answer: B,D
Explanation:
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.
NEW QUESTION # 27
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.)
- A. Inform users to identify the runner based on the group.
- B. Configure the webhook and network to enable GitHub to trigger workflow.
- C. Inform users to identify the runner with the labels custom-software and linux.
- D. Add the label custom-software to the runner.
- E. Add the label linux to the runner.
- F. Create the group custom-software-on-linux and move the runner into the group.
Answer: C,D
Explanation:
[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 # 28
Which default GitHub environment variable indicates the owner and repository name?
- A. ENV REPOSITORY
- B. REPOSITORY NAME
- C. GITHUB REPOSITORY
- D. GITHUB WORKFLOW REPO
Answer: B
Explanation:
The GITHUB_REPOSITORY environment variable contains the owner and repository name in the format owner/repository. It is automatically provided by GitHub Actions and can be used to reference the repository in workflows.
NEW QUESTION # 29
What menu options in a repository do you need to select in order to use a starter workflow that is provided by your organization?
- A. Actions > Load workflow
- B. Workflow > Load workflow
- C. Workflow > New workflow
- D. Actions > New workflow
Answer: D
Explanation:
To use a starter workflow provided by your organization, you need to go to the Actions tab in the repository and select New workflow. This option allows you to either create a new workflow or select from a list of available workflow templates, including starter workflows provided by your organization.
NEW QUESTION # 30
......
Microsoft GH-200 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
GH-200 Exam Crack Test Engine Dumps Training With 97 Questions: https://www.suretorrent.com/GH-200-exam-guide-torrent.html
Getting GH-200 Certification Made Easy: https://drive.google.com/open?id=1ndufDnP7jmtGQP3GLvmfn8E_4EXtTdO9