Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 51:

  GitHub-hosted runners support which capabilities? (Each correct answer presents a complete solution. Choose two.)

  A. support for Linux, Windows, and macOS
  B. support for a variety of Linux variations including CentOS, Fedora, and Debian
  C. requiring a payment mechanism (e.g., credit card) to use for private repositories
  D. automatic file-system caching between workflow runs
  E. automatic patching of both the runner and the underlying OS
  A. support for Linux, Windows, and macOS
  E. automatic patching of both the runner and the underlying OS

  ---

  Explanation

  [A, not B] Each GitHub-hosted runner is a new virtual machine (VM) hosted by GitHub with the runner application and other tools preinstalled, and is available with Ubuntu Linux, Windows, or macOS operating systems.

  [E] When you use a GitHub-hosted runner, machine maintenance and upgrades are taken care of for you.

  https://docs.github.com/en/[email protected]/actions/concepts/runners/github-hosted-runners

• Question 52:

  As a DevOps engineer, you need to execute a deployment to different environments like development and testing based on the labels added to a pull request. The deployment should use the releases branch and trigger only when there is a change in the files under ‘apps’ folder. Which code block should be used to define the deployment workflow trigger?

  A. on: pull_request_label: branches: -'releases' paths: -'apps/**'
  B. on: pull_request: types: [labeled] branches: -'releases/**' paths: -'apps'
  C. on: pull_request: types: [labeled] branches: -'releases' paths: -'apps/**'
  D. on: pull_request_review: types: [labeled] branches: -'releases' paths: -'apps/**'
  C. on: pull_request: types: [labeled] branches: -'releases' paths: -'apps/**'

  ---

  Explanation

  Incorrect:

  [Not A] pull_request activitiy type labeled not specified.

  pull_request_label is not a trigger.

  [Not B] Specifies branches branches that has a name that starts with releases. We are only interested in the release branch.

  branches:

  -'releases/**'

  [Not C]

  pull_request_review

  Runs your workflow when a pull request review is submitted, edited, or dismissed. A pull request review is a group of pull request review comments in addition to a body comment and a state.

  https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

• Question 53:

  Which workflow commands send information from the runner? (Each correct answer presents a complete solution. Choose two.)

  A. reading from environment variables
  B. setting a debug message
  C. populating variables in a Dockerfile
  D. setting output parameters
  B. setting a debug message

  ---

  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"

  https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands

• Question 54:

  Which files are required for a Docker container action in addition to the source code? (Each correct answer presents a partial solution. Choose two.)

  A. action.yml
  B. Actionfile
  C. metadata.yml
  D. Dockerfile
  A. action.yml
  D. Dockerfile

  ---

  Explanation

  Creating a Docker container action

  Create a dockerfile Dockerfile support for GitHub Actions When creating a Dockerfile for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action's metadata file.

  Creating an action metadata file Create a new action.yml file.

  https://docs.github.com/en/actions/tutorials/use-containerized-services/create-a-docker-container-action https://docs.github.com/en/actions/reference/workflows-and-actions/dockerfile-support

• Question 55:

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

  A. the entire workflow, by using env at the top level of the workflow file
  B. all jobs being run on a single Actions runner, by using runner.env at the top of the workflow file
  C. the entire stage, by using env at the top of the defined build stage
  D. within the run attribute of a job step
  E. the contents of a job within a workflow, by using jobs.env
  F. a specific step within a job, by using jobs..steps[*].env
  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.env
  F. a specific step within a job, by using jobs..steps[*].env

  ---

  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:

  [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..env.

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

  https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-variables

• Question 56:

  What can be used to set a failed status of an action from its code?

  A. JavaScript dist/ folder
  B. composite run step
  C. output variable
  D. a non-zero exit code
  E. Dockerfile CMD
  F. @actions/github toolkit
  D. a non-zero exit code

  ---

  Explanation

  Setting exit codes for actions

  You can use exit codes to set the status of an action. GitHub displays statuses to indicate passing or failing actions.

  About exit codes

  GitHub uses the exit code to set the action's check run status, which can be success or failure.

  *

  Exit status: 0

  Check run status: success

  The action completed successfully and other tasks that depend on it can begin.

  *

  Exit status: Nonzero value (any integer but 0)

  Check run status: failure

  Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a failure status.

  https://docs.github.com/en/actions/how-tos/create-and-publish-actions/set-exit-codes

• Question 57:

  What is the simplest action type to run a shell script?

  A. Bash script action
  B. Composite action
  C. JavaScript action
  D. Docker container action
  C. JavaScript action

  ---

  Explanation

  Types of actions

  Docker container actions. Docker containers package the environment with the GitHub Actions code. ...

  JavaScript actions. JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. ...

  Composite Actions.

  Note:

  JavaScript actions

  JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.

  https://docs.github.com/en/actions/concepts/workflows-and-actions/custom-actions

• Question 58:

  Which of the following is the most common way to target a specific major release version?

  A. steps: -uses: actions/checkout@v3
  B. steps: -uses: actions/checkout
  C. steps: -uses: actions/checkout@U1673995124
  D. steps: - uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c
  A. steps: -uses: actions/checkout@v3

  ---

  Explanation

  Example: Using versioned actions steps: # Reference a specific commit

  - uses: actions/checkout@8f4b7f84864484a7bf31766abe9204da3cbe65b3 *-> # Reference the major version of a release -uses: actions/checkout@v4 # Reference a specific version

  -uses: actions/[email protected] # Reference a branch

  -uses: actions/checkout@main

  https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax

• Question 59:

  As a developer, you need to integrate a GitHub Actions workflow with a third-party code quality provider that uses the Checks API. How should you trigger a follow-up workflow?

  A. Add the workflow_run webhook event as a trigger for the workflow for the code quality integration name
  B. Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed
  C. Add the pull_request webhook event as a trigger for the workflow when the code quality integration is synchronized
  D. Add the deployment webhook event as a trigger for the workflow when the code quality integration is completed
  B. Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed

  ---

  Explanation

  The check_run event is triggered when a check (such as a code quality check) completes, including when the status of a check changes. By adding this event as a trigger, you can initiate a follow-up workflow when the code quality integration finishes its checks.

  https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

• Question 60:

  Which two workflow triggers support custom payloads from external systems? (Choose two.)

  A. repository_dispatch
  B. workflow_run
  C. workflow_call
  D. schedule
  E. issue_comment
  A. repository_dispatch
  C. workflow_call

  ---

  Explanation

  repository_dispatch allows external systems to trigger workflows using the REST API.

  workflow_call enables one workflow to call another, optionally passing custom inputs or secrets.

  Events that trigger workflows