Microsoft GH-200 Exam Dumps [2025] Practice Valid Exam Dumps Question
GH-200 Dumps - Grab Out For [NEW-2025] Microsoft Exam
NEW QUESTION # 13
As a developer, what options should you recommend to implement standards for automation reuse? (Choose two.)
- A. Create reusable actions and workflows that can be called from other workflows.
- B. Create workflow templates and store them in the organization's .github repository.
- C. Store shared corporate actions in subfolders in a defined and documented internally accessible repository.
- D. Create a marketplace partition to publish reusable automation for the company.
Answer: A,B
Explanation:
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.
NEW QUESTION # 14
When creating and managing custom actions in an enterprise setting, which of the following is considered a best practice?
- A. including custom actions that other teams need to reference in the same repository as application code
- B. creating a separate branch in application repositories that only contains the actions
- C. creating a single repository for all custom actions so that the versions for each action are all the same
- D. creating a separate repository for each action so that the version can be managed independently
Answer: D
Explanation:
Creating a separate repository for each custom action allows you to manage the versioning independently for each action. This approach provides flexibility, as each action can be updated, tested, and versioned separately, avoiding potential conflicts or dependencies between different actions.
NEW QUESTION # 15
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?
- A. via repositories owned by the organization
- B. via the .github repository owned by the organization
- C. via the GitHub Marketplace
- D. via a repository owned by a third party
Answer: A
Explanation:
To prevent reaching the storage limit for GitHub artifacts and packages, you should manage and clean up artifacts and packages stored in repositories owned by your organization. This includes deleting unnecessary artifacts and managing the lifecycle of packages, as they contribute directly to your organization's storage quota.
NEW QUESTION # 16
What can be used to set a failed status of an action from its code?
- A. @actions/github toolkit
- B. JavaScript dist/ folder
- C. composite run step
- D. Dockerfile CMD
- E. output variable
- F. a non-zero exit code
Answer: F
Explanation:
A non-zero exit code is used to set the status of an action to "failed" in GitHub Actions. When the action's script or code exits with a non-zero status, it indicates failure, and GitHub will mark the action as failed.
NEW QUESTION # 17
As a developer, one of your workflows will require XCode version 11.2 hosted on macOS Catalina (i.e., v10.15). You've already created and configured a self-hosted runner to conform to those requirements and registered it with your organization. What else should you do to ensure that the workflow accesses the correct runner instance? (Each answer presents a complete solution. Choose three.)
- A. Assign the custom labels to the self-hosted runner.
- B. Add your runner to the appropriate runner groups.
- C. Create custom runner labels for macos-10.15 and xcode-11.2.
- D. In the workflow, specify:
runs-on: [ ${{groups.macos-10.15}}, ${{groups.xcode-11.2}} ]. - E. Create runner groups named macos-10.15 and xcode-11.2.
- F. In the workflow, specify:
runs-on: [self-hosted, macos-10.15, xcode-11.2].
Answer: A,C,F
Explanation:
[C, F] Using custom labels to route jobs
You can create custom labels and assign them to your self-hosted runners at any time. Custom labels let you send jobs to particular types of self-hosted runners, based on how they're labeled.
[E] Using default labels to route jobs
A self-hosted runner automatically receives certain labels when it is added to GitHub Actions.
These are used to indicate its operating system and hardware platform:
self-hosted: Default label applied to self-hosted runners.
linux, windows, or macOS: Applied depending on operating system.
x64, ARM, or ARM64: Applied depending on hardware architecture.
You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job:
runs-on: [self-hosted, linux, ARM64]
self-hosted - Run this job on a self-hosted runner.
linux - Only use a Linux-based runner.
ARM64 - Only use a runner based on ARM64 hardware.
Reference:
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/use-in-a- workflow
NEW QUESTION # 18
In a workflow triggered by a pull request comment, which GitHub Actions context property contains the event payload used to access the comment text and the pull request number?
- A. github.job
- B. github.repository
- C. github.event
- D. github.event_path
Answer: C
Explanation:
In a workflow that runs on a pull request comment the event context contains the webhook payload. With github.event you can read the structured fields for the comment text and the pull request number. The comment text is available under the comment body field and the pull request number is available under the issue number for comment events or under the pull request number for pull request events. This makes github.event the direct and convenient source for these values.
NEW QUESTION # 19
By default, which workflows can use an action stored in internal repository? (Each answer presents a complete solution. Choose two.)
- A. selected public repositories outside of the enterprise
- B. public repositories owned by the same organization as the enterprise
- C. private repositories owned by an organization of the enterprise
- D. internal repositories owned by the same organization as the enterprise
Answer: C,D
Explanation:
Any actions or reusable workflows stored in the internal or private repository can be used in workflows defined in other internal or private repositories owned by the same organization, or by any organization owned by the enterprise.
Reference:
https://docs.github.com/actions/creating-actions/sharing-actions-and-workflows-with-your- enterprise
NEW QUESTION # 20
Custom environment variables can be defined at multiple levels within a workflow file including:
(Each answer presents a complete solution. Choose three.)
- A. runner level.
- B. job level.
- C. step level.
- D. top level.
- E. default level.
- F. stage level.
Answer: B,C,D
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 # 21
Which workflow commands send information from the runner? (Each correct answer presents a complete solution. Choose two.)
- A. populating variables in a Dockerfile
- B. setting output parameters
- C. reading from environment variables
- D. setting a debug message
Answer: B,D
Explanation:
[B] Setting a debug message
Prints a debug message to the log. You must create a secret named ACTIONS_STEP_DEBUG with the value true to see the debug messages set by this command in the log.
::debug::{message}
Example: Setting a debug message
echo "::debug::Set the Octocat variable"
[D] Setting an output parameter
Sets a step's output parameter. Note that the step will need an id to be defined to later retrieve the output value.
echo "{name}={value}" >> "$GITHUB_OUTPUT"
Example of setting an output parameter
This example demonstrates how to set the SELECTED_COLOR output parameter and later retrieve it:
- name: Set color
id: color-selector
run: echo "SELECTED_COLOR=green" >> "$GITHUB_OUTPUT"
- name: Get color
env:
SELECTED_COLOR: ${{ steps.color-selector.outputs.SELECTED_COLOR }}
run: echo "The selected color is $SELECTED_COLOR"
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands
NEW QUESTION # 22
As a developer, you want to review the step that caused a workflow failure and the failed step's build logs. First navigate to the main page of the repository on GitHub. Which section contains the step failure information?
- A. Actions
- B. Code
- C. Pull requests
- D. Issues
- E. Insights
Answer: A
Explanation:
The Actions tab on the main page of the repository is where you can find detailed information about the workflow runs, including step failures and build logs. You can review the status of each job and step within the workflow, see the failure messages, and access logs for debugging.
NEW QUESTION # 23
As a DevOps engineer, you need to define a deployment workflow that runs after the build workflow has successfully completed. Without modifying the build workflow, which trigger should you define in the deployment workflow?
- A. workflow_run
- B. workflow_dispatch
- C. repository_dispatch
- D. workflow_exec
Answer: A
Explanation:
A deployment workflow can be started after a build workflow has finished by using the workflow_run event in the deployment workflow's on trigger. You must specify the name of the build workflow you want to trigger on and use an if condition to ensure the deployment workflow only runs if the build workflow successfully completes.
Here's how to set it up:
In your deployment workflow file: (e.g., deploy.yml), define the on: trigger.
Use the workflow_run event: within the on: trigger.
Specify the build workflow: by its name.
Add a conditional if statement: to the workflow to check the conclusion of the workflow_run event, ensuring it equals 'success'.
Reference:
https://docs.github.com/actions/learn-github-actions/events-that-trigger-workflows
NEW QUESTION # 24
In GitHub Enterprise Cloud, where do you set the policy that allows only enterprise hosted actions and reusable workflows to run?
- A. Organization settings Policies then Actions
- B. Repository settings Actions general
- C. Enterprise account Actions policy
Answer: C
Explanation:
The enterprise Actions policy is the centralized place where enterprise owners enforce which actions and reusable workflows are permitted across all organizations in GitHub Enterprise Cloud. From this scope you can require that only actions and reusable workflows hosted within the enterprise are allowed to run, and this policy flows down to organizations and repositories to ensure consistent enforcement.
NEW QUESTION # 25
What are the mandatory requirements for publishing GitHub Actions to the GitHub Marketplace?
(Each correct answer presents part of the solution. Choose two.)
- A. The action's metadata file must be in the root directory of the repository.
- B. The name should match with one of the existing GitHub Marketplace categories.
- C. The action can be either in a public or private repository.
- D. Each repository can contain a collection of actions as long as they are under the same Marketplace category.
- E. The action's name cannot match a user or organization on GitHub unless the user or organization owner is publishing the action.
Answer: A
Explanation:
Publishing actions in GitHub Marketplace
You can publish actions in GitHub Marketplace and share actions you've created with the GitHub community.
Prerequisite include:
[B] Each repository must contain a single action metadata file (action.yml or action.yaml) at the root.
The name in the action's metadata file must be unique.
The name cannot match an existing action name published on GitHub Marketplace.
[C] The name cannot match a user or organization on GitHub, unless the user or organization owner is publishing the action. For example, only the GitHub organization can publish an action named github.
Reference:
https://docs.github.com/en/actions/how-tos/create-and-publish-actions/publish-in-github- marketplace
NEW QUESTION # 26
As a developer, what options should you recommend to implement standards for automation reuse? (Choose two.)
- A. Create reusable actions and workflows that can be called from other workflows.
- B. Create workflow templates and store them in the organization's .github repository.
- C. Store shared corporate actions in subfolders in a defined and documented internally accessible repository.
- D. Create a marketplace partition to publish reusable automation for the company.
Answer: A,B
Explanation:
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.
NEW QUESTION # 27
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. Workflow > Load workflow
- B. Workflow > New workflow
- C. Actions > New workflow
- D. Actions > Load workflow
Answer: C
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 # 28
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. self-hosted: [windows-x64]
- C. runs-on: windows-latest
- 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 # 29
......
GH-200 Exam Dumps PDF Guaranteed Success with Accurate & Updated Questions: https://www.dumpstests.com/GH-200-latest-test-dumps.html
Pass GH-200 Exam - Real Test Engine PDF with 97 Questions: https://drive.google.com/open?id=1NDzVHNMtcqF2qnZ6bFezyCdEtI8-iD-3