Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 41:

  When should you use the GITHUB_TOKEN in a workflow?

  A. when you want to make authenticated calls to the GitHub API
  B. when you want to connect to the runner via SSH
  C. when you want to access repository-level secrets
  D. when you want to call an action from the marketplace
  A. when you want to make authenticated calls to the GitHub API

  ---

  Explanation

  Use GITHUB_TOKEN for authentication in workflows

  At the start of each workflow job, GitHub automatically creates a unique GITHUB_TOKEN secret to use in your workflow. You can use the GITHUB_TOKEN to authenticate in the workflow job.

  https://docs.github.com/en/actions/tutorials/authenticate-with-github_token

• Question 42:

  As a DevOps engineer, you are developing workflows to build an application. You have a requirement to create the build targeting multiple node versions. Which code block should you use to define the workflow?

  A

  ---

  Explanation

  Use keywords strategy and matrix in that order.

  Last line should be node-version: ${{ matrix.node-ver}}

  Incorrect:

  [Not B]

  Use keywords matrix and strategy separately, not matrix-strategy.

  [Not C] Wrong order of keywords strategy and matrix.

  [Not D] Last line should be node-version: ${{ matrix.node-ver}} not ${{ strategy.node-ver}}

  Note: Running variations of jobs in a workflow

  Create a matrix to define variations for each job.

  A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based on the combinations

  Adding a matrix strategy to your workflow job

  Use jobs..strategy.matrix to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called version with the value

  [10, 12, 14] and a variable called os with the value [ubuntu-latest, windows-latest]:

  jobs: example_matrix: strategy:

  matrix:

  version: [10, 12, 14]

  os: [ubuntu-latest, windows-latest]

  Using contexts to create matrices

  To create matrices with information about workflow runs, variables, runner environments, jobs, and steps, access contexts using the ${{ }} expression syntax.

  {

  "event_type": "test",

  "client_payload": {

  "versions": [12, 14, 16]

  } } on:

  repository_dispatch:

  types:

  -test

  jobs:

  example_matrix:

  runs-on: ubuntu-latest

  strategy:

  matrix:

  version: ${{ github.event.client_payload.versions }}

  steps:

  -uses: actions/setup-node@v4

  with:

  node-version: ${{ matrix.version }}

  https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations

• Question 43:

  What is the best way to reuse the same step logic across multiple workflows within the same repo?

  A. Composite action
  B. Inline scripts
  C. Reusable workflow
  D. Repository secret
  A. Composite action

  ---

  Explanation

  Composite actions allow you to combine multiple steps into a single reusable unit stored in .github/actions/.

• Question 44:

  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, pull_request]
  B. on: branches: -'main' -'dev'
  C. on: schedule: -cron: '*/15 * * * *' initiate: -'main'
  D. on: [push, commit]
  E. on: push: branches: -main release: types: -created
  F. on: env: -'prod' -'qa' -'test'
  A. on: [push, pull_request]
  C. on: schedule: -cron: '*/15 * * * *' initiate: -'main'

  ---

  Explanation

  on 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.

  Example: on: schedule:

  -

  cron: '30 5 * * 1,3'

  -

  cron: '30 5,17 * * 2,4'

  [Not B] Incorrect syntax.

  Using filters

  Some events have filters that give you more control over when your workflow should run.

  For example, the push event has a branches filter that causes your workflow to run only when a push to a branch that matches the branches filter occurs, instead of when any push occurs.

  on: push: branches:

  -main

  Incorrect:

  -'releases/**'

  [Not D] commit is not an event that triggers a workflow.

  [Not F] Not the correct syntax.

  env

  A map of variables that are available to the steps of all jobs in the workflow. You can also set variables that are only available to the steps of a single job or to a single step.

  env:

  SERVER: production

  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

• Question 45:

  You need to create new workflows to deploy to an unfamiliar cloud provider. What is the fastest and safest way to begin?

  A. Create a custom action to wrap the cloud provider's CLI.
  B. Search GitHub Marketplace for verified actions published by the cloud provider.
  C. Use the actions/jenkins-plugin action to utilize an existing Jenkins plugin for the cloud provider.
  D. Search GitHub Marketplace for actions created by GitHub.
  E. Download the CLI for the cloud provider and review the associated documentation.
  B. Search GitHub Marketplace for verified actions published by the cloud provider.

  ---

  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.

  Note: About GitHub Marketplace for apps

  GitHub Marketplace where you can share your apps with everyone.

  GitHub Marketplace connects you to developers who want to extend and improve their GitHub workflows.

  You can list free and paid tools for developers to use in GitHub Marketplace. GitHub Marketplace offers developers two types of tools: GitHub Actions and Apps, and each tool requires different steps for adding it to GitHub Marketplace.

  GitHub Actions

  Anyone can publish an action in GitHub Marketplace. GitHub verifies some partner organizations and these are shown as verified creators.

  https://docs.github.com/en/enterprise-cloud@latest/apps/github-marketplace/github-marketplace-overview/about-github-marketplace-for-apps

• Question 46:

  Which of the following statements are true regarding the use of GitHub Actions on a GitHub Enterprise Server instance? (Each correct answer presents a complete solution. Choose three.)

  A. Actions created by GitHub are automatically available and cannot be disabled.
  B. Third-party actions can be used on GitHub Enterprise Server by configuring GitHub Connect.
  C. Most GitHub-authored actions are automatically bundled for use on GitHub Enterprise Server.
  D. Use of GitHub Actions on GitHub Enterprise Server requires a persistent internet connection.
  E. Actions must be defined in the .github repository.
  F. Third-party actions can be manually synchronized for use on GitHub Enterprise Server.
  B. Third-party actions can be used on GitHub Enterprise Server by configuring GitHub Connect.
  C. Most GitHub-authored actions are automatically bundled for use on GitHub Enterprise Server.
  F. Third-party actions can be manually synchronized for use on GitHub Enterprise Server.

  ---

  Explanation

  [B] If you want your GitHub Enterprise Server instance to use third-party custom actions, you need to enable GitHub Connect.

  [C] Most official GitHub-authored actions are automatically bundled with GitHub Enterprise Server, and are captured at a point in time from GitHub Marketplace.

  [F] Third-party actions can be manually synchronized to GitHub Enterprise Server (GHES) to be used in workflows without requiring an internet connection to GitHub.com. This is done using the actions-sync tool to download actions from

  GitHub.com and transfer them to the GHES instance. This manual method provides an alternative to using GitHub Connect, offering stricter control over which actions are available on the GHES instance.

  Incorrect:

  [Not D] There is no connection required between your GitHub Enterprise Server instance and GitHub.com

  to use these actions.

  https://docs.github.com/en/[email protected]/get-started/exploring-integrations/about-using-integrations https://docs.github.com/en/[email protected]/admin/managing-github-actions-for-your-enterprise/ managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise

• Question 47:

  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? (Each correct answer presents part of the solution. Choose two.)

  A. Use artifacts to access the GitHub Package Registry and download a package for a workflow.
  B. Use caching when reusing files that change rarely between jobs or workflow runs.
  C. Use caching to store cache entries for up to 30 days between accesses.
  D. Use artifacts when referencing files produced by a job after a workflow has ended.
  B. Use caching when reusing files that change rarely between jobs or workflow runs.
  D. Use artifacts when referencing files produced by a job after a workflow has ended.

  ---

  Explanation

  [B] Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system.

  [D] Use artifacts when you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs.

  https://docs.github.com/en/[email protected]/actions/tutorials/store-and-share-data

• Question 48:

  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. Configure the webhook and network to enable GitHub to trigger workflow.
  B. Create the group custom-software-on-linux and move the runner into the group.
  C. Inform users to identify the runner with the labels custom-software and linux.
  D. Add the label linux to the runner.
  E. Inform users to identify the runner based on the group.
  F. Add the label custom-software to the runner.
  C. Inform users to identify the runner with the labels custom-software and linux.
  F. Add the label custom-software to the runner.

  ---

  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.

  https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/apply-labels

• Question 49:

  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. actions stored in an organizational partition in the GitHub Marketplace
  B. custom Docker actions stored in GitHub Container Registry
  C. self-hosted runners
  D. encrypted secrets
  E. workflow templates
  F. actions stored in private repositories in the organization
  D. encrypted secrets
  E. workflow templates
  F. actions stored in private repositories in the organization

  ---

  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.

  https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows

• Question 50:

  When can you define default shell settings and working directories for steps in a workflow?

  A. Using defaults: at the job or workflow level
  B. Using runs: in every step
  C. Using actions/setup-env
  D. Using env: in each job
  A. Using defaults: at the job or workflow level

  ---

  Explanation

  defaults: lets you define run.shell and run.working-directory once, applied to all steps.