[Jul-2026 Newly Released] GH-200 Dumps for GitHub Administrator Certified
Updated Verified GH-200 dumps Q&As - 100% Pass
Microsoft GH-200 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 20
Your organization needs to simplify reusing and maintaining automation in your GitHub Enterprise Cloud. Which components can be directly reused across all repositories in an organization?
(Each correct answer presents a complete solution. Choose three.)
- A. encrypted secrets
- B. actions stored in an organizational partition in the GitHub Marketplace
- C. actions stored in private repositories in the organization
- D. custom Docker actions stored in GitHub Container Registry
- E. self-hosted runners
- F. workflow templates
Answer: A,C,F
NEW QUESTION # 21
What will the output be for the following event trigger block in a workflow?
- A. It runs the workflow when an issue is edited or when an issue comment created.
- B. It runs the workflow when an issue is created or edited, or when an issue or pull request comment is created.
- C. It throws a workflow syntax error, pointing to the types definition in issue_comment event.
- D. It runs the workflow when an issue or issue comment in the workflow's repository is created or modified.
- E. It throws a workflow syntax error, pointing to the types definition in issues event.
Answer: A
Explanation:
Based on your configuration, the workflow will trigger in these three specific scenarios:
Issue Opened: When a brand-new issue is created.
Issue Edited: When the title or body of an existing issue is changed.
Comment Created: When someone adds a new comment to an issue or pull request.
Reference:
https://forgejo.org/docs/next/user/actions/reference
NEW QUESTION # 22
You need to pass values from a runner to other parts of a GitHub Actions workflow.
Which two actions should you perform? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
- A. Configure the output parameters.
- B. Create environment variables by writing to the GITHUB_ENV file.
- C. Read from the environment variables.
- D. Set a debug message.
Answer: B,C
Explanation:
To pass a value between steps within the same job, you write to the $GITHUB_ENV file.
[D] 1. Write the value
Use a shell command to echo the variable name and value into the environment file:
- name: Set the value
run: echo "MY_VARIABLE=hello-world" >> $GITHUB_ENV
[B] 2. Read the value
In any subsequent step within that same job, you can access it like a standard environment variable or via the env context:
- name: Use the value
run: echo "The value is ${{ env.MY_VARIABLE }}"
Note: Environment variables set this way are only available to subsequent steps in the same job.
If you need to pass a value to a different job, you must use outputs instead.
Reference:
https://docs.github.com/actions/learn-github-actions/variables
NEW QUESTION # 23
What is a role of GitHub Marketplace when using GitHub Actions?
- A. GitHub Marketplace allows a user to deploy GitHub Actions workflows to any repository automatically without requiring permissions.
- B. GitHub Marketplace provides a centralized location to discover, share, and publish reusable GitHub Actions workflows created by the community or vendors.
- C. GitHub Marketplace restricts the use of third-party actions to only public repositories.
- D. GitHub Marketplace serves only as a billing dashboard for tracking paid actions.
Answer: B
Explanation:
GitHub Marketplace is used to discover, share, and publish reusable automation, including GitHub Actions created by GitHub, vendors, and the community. Option C best describes this role.
Marketplace does not exist only for billing, so option B is too narrow and incorrect. Option A is also wrong because Marketplace does not merely restrict third-party actions to public repositories; action usage is governed by repository, organization, or enterprise Actions policies. Option D is false because Marketplace does not bypass repository permissions or automatically deploy workflows into repositories. In exam terms, Marketplace is part of the automation reuse and action discovery domain:
developers use it to find trusted or verified actions rather than building every integration manually.
GitHub documents Marketplace as a place to publish and share actions with the community.
NEW QUESTION # 24
You need to perform a task that requires running a custom script in a GitHub Actions workflow. The script must run within the workflow environment without requiring an external container or prebuilt image.
What should you use?
- A. a composite action
- B. a Docker container action
- C. a JavaScript action
- D. a run step
Answer: D
Explanation:
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.
NEW QUESTION # 25
What are the two types of environment protection rules you can configure? (Choose two.)
- A. artifact storage
- B. branch protections
- C. required reviewers
- D. wait timer
Answer: C,D
Explanation:
Required reviewers is a protection rule where you can specify that certain individuals or teams must review and approve the workflow run before it can proceed. This is used to enforce approvals before certain steps or environments are accessed.
Wait timer is a protection rule that introduces a delay before a workflow can proceed to the next stage. This is useful for adding time-based constraints to the deployment process or ensuring that certain conditions are met before a workflow continues.
NEW QUESTION # 26
Your organization needs to simplify reusing and maintaining automation in your GitHub Enterprise Cloud. Which components can be directly reused across all repositories in an organization?
(Each correct answer presents a complete solution. Choose three.)
- A. encrypted secrets
- B. actions stored in an organizational partition in the GitHub Marketplace
- C. actions stored in private repositories in the organization
- D. custom Docker actions stored in GitHub Container Registry
- E. self-hosted runners
- F. workflow templates
Answer: A,C,F
Explanation:
[D] Encrypted secrets can be accessed across repositories in the same organization, making it easy to store sensitive data (like API keys or tokens) securely while allowing multiple workflows to access them.
[E] Workflow templates allow you to create reusable templates for workflows that can be shared across repositories within the organization. This makes it easier to standardize processes and automate them across multiple projects.
[F] Actions stored in private repositories within the organization can be reused across all repositories by referencing them in workflows. This ensures a centralized way of maintaining custom actions.
Reference:
https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows
NEW QUESTION # 27
Your organization is managing secrets using GitHub encrypted secrets, including a secret named SuperSecret. As a developer, you need to create a version of that secret that contains a different value for use in a workflow that is scoped to a specific repository named MyRepo. How should you store the secret to access your specific version within your workflow?
- A. Create and access SuperSecret from the secrets store in MyRepo.
- B. Create a file with the SuperSecret information in the .github/secrets folder in MyRepo.
- C. Create a duplicate entry for SuperSecret in the encrypted secret store and specify MyRepo as the scope.
- D. Create MyRepo_SuperSecret in GitHub encrypted secrets to specify the scope to MyRepo.
Answer: C
NEW QUESTION # 28
You need to create a reusable GitHub Actions workflow template named ci.yml. The solution must ensure that ci.yml appears on the New workflow interface of GitHub Actions. Where should you store ci.yml?
- A. .github/templates
- B. the root directory of each repository
- C. .github/workflows
- D. .github/workflow-templates
Answer: D
Explanation:
To ensure your reusable GitHub Actions workflow template appears in the New workflow interface (also known as the starter workflow picker), it must be stored in a specific directory within a special repository in your organization.
Required Storage Location
Repository Name: .github (This must be a public repository at the root of your organization).
Directory Path: workflow-templates.
Note:
Essential Files to Include
For the template to be correctly indexed and displayed in the interface, you must include two files in the workflow-templates directory:
The Workflow File: A standard YAML file (e.g., ci-template.yml) containing the workflow definition.
The Metadata File: A JSON file that must have the same name as the workflow file but with a .properties.json extension (e.g., ci-template.properties.json).
Reference:
https://docs.github.com/en/[email protected]/actions/using-workflows/creating-starter- workflows-for-your-organization
NEW QUESTION # 29
You are reaching your organization's storage limit for GitHub artifacts and packages. What should you do to prevent the storage limit from being reached? (Choose two.)
- A. Disable branch protections in the repository.
- B. Delete artifacts from the repositories manually
- C. Use self-hosted runners for all workflow runs.
- D. Configure the repo to use Git Large File Storage.
- E. Configure the artifact and log retention period.
Answer: B,E
Explanation:
Deleting artifacts from repositories manually will free up storage space. Artifacts are typically stored for a limited time by default, but manual cleanup can help manage space.
Configuring the artifact and log retention period allows you to control how long artifacts and logs are retained in your repository. By shortening the retention period, you can prevent unnecessary accumulation of data and manage storage more effectively.
NEW QUESTION # 30
When reviewing an action for use, what file defines its available inputs and outputs?
- A. action.yml
- B. config.json
- C. workflow.yml
- D. defaults.json
- E. inputs.yml
Answer: A
Explanation:
The action.yml file defines the inputs and outputs for a GitHub Action. This file contains metadata about the action, including the required inputs and outputs, as well as other configurations like the action's description, runs, and environment setup.
NEW QUESTION # 31
As a developer, what is the safest way to reference an action to prevent modification of the underlying code?
- A. Use a patch release tag.
- B. Use a major release tag.
- C. Use a commit hash.
- D. Use a branch name.
Answer: C
Explanation:
Using a commit hash is the safest method because it references a specific point in time in the repository's history. This ensures that the action is locked to that exact version and will not be affected by any future changes or modifications to the codebase. Even if the action is updated later, your workflow will continue using the specific commit you referenced.
NEW QUESTION # 32
As a developer, how can you identify a Docker container action on GitHub?
- A. The action's repository includes @actions/core in the root directory.
- B. The action's repository name includes the keyword "Docker."
- C. The action.yml metadata file has the runs.using value set to Docker.
- D. The action.yml metadata file references a Dockerfile file.
Answer: C
Explanation:
In a Docker container action, the action.yml file includes the runs.using field, which is set to docker to specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.
NEW QUESTION # 33
You need to create new workflows to deploy to an unfamiliar cloud provider. What is the fastest and safest way to begin?
- A. Search GitHub Marketplace for actions created by GitHub.
- B. Use the actions/jenkins-plugin action to utilize an existing Jenkins plugin for the cloud provider.
- C. Create a custom action to wrap the cloud provider's CLI.
- D. Download the CLI for the cloud provider and review the associated documentation.
- E. Search GitHub Marketplace for verified actions published by the cloud provider.
Answer: E
Explanation:
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.
NEW QUESTION # 34
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 when reusing files that change rarely between jobs or workflow runs.
- B. Use caching to store cache entries for up to 30 days between accesses.
- C. Use artifacts when referencing files produced by a job after a workflow has ended.
- D. Use artifacts to access the GitHub Package Registry and download a package for a workflow
Answer: A,C
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 # 35
A development team has been using a Powershell script to compile and package their solution using existing tools on a Linux VM, which has been configured as a self-hosted runner. They would like to use the script as-is in an automated workflow. Which of the following should they do to invoke their script within a workflow step?
- A. Use the actions/run-powershell action to invoke the script.
- B. Use the YAML shell: pwsh in a run step.
- C. Run the pwsh2bash command to convert the script so it can be run on Linux.
- D. Use the YAML powershell: step.
- E. Configure a self-hosted runner on Windows with the requested tools.
Answer: B
Explanation:
Since the self-hosted runner is configured on a Linux VM and the script is written in PowerShell, you can invoke the script using the pwsh (PowerShell Core) shell in a run step in the workflow. This ensures that the script runs as-is on the Linux runner, as PowerShell Core (pwsh) is cross-platform and supports Linux.
NEW QUESTION # 36
......
Latest GH-200 Exam Dumps Microsoft Exam from Training: https://www.actualvce.com/Microsoft/GH-200-valid-vce-dumps.html
New 2026 Latest Questions GH-200 Dumps - Use Updated Microsoft Exam: https://drive.google.com/open?id=1cHyb_yj2ObjYUjzyWbQMGDSSZts0K5JA