Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 31:

  What are the most significant advantages of adding documentation while distributing custom actions? (Each answer presents a complete solution. Choose two.)

  A. It generates auto completion when using the action in a workflow.
  B. It shares the description of the action to the users.
  C. It provides an example of the action.
  D. It creates a readme.md for the consuming workflow.
  B. It shares the description of the action to the users.
  D. It creates a readme.md for the consuming workflow.

  ---

  Explanation

• Question 32:

  As a developer, you created a JavaScript action. What is the best way to test your JavaScript action?

  A. Create a workflow that only executes your specific JavaScript action.
  B. Package your JavaScript action inside a docker container image and run it.
  C. Use a tool called @vercel/ncc to compile your code.
  D. Create a workflow that includes the actions/debug-javascript action.
  A. Create a workflow that only executes your specific JavaScript action.

  ---

  Explanation

  Testing out your JavaScript action in a workflow You can test your action out in a workflow.

  Public actions can be used by workflows in any repository. When an action is in a private repository, the repository settings dictate whether the action is available only within the same repository or also to other repositories owned by the same user or organization.

  https://docs.github.com/en/actions/tutorials/create-actions/create-a-javascript-action

• Question 33:

  You want to prevent a deployment workflow from running if the “build” workflow failed. How can you implement this?

  A. Use needs: build with if: success()
  B. Use workflow_run with types: [failed]
  C. Add continue-on-error: false to build job
  D. Add if: always() to deployment job
  A. Use needs: build with if: success()

  ---

  Explanation

  A job depending on another should specify needs: and if: success() to ensure execution only when the dependency passes.

• Question 34:

  Which default GitHub environment variable indicates the name of the person or app that initiated a workflow?

  A. GITHUB_ACTOR
  B. GITHUB USER
  C. ENV_ACTOR
  D. GITHUB_WORKFLOW_ACTOR
  A. GITHUB_ACTOR

  ---

  Explanation

  GITHUB_ACTOR : The name of the person or app that initiated the workflow.

  https://graphite.dev/guides/github-actions-variables

• Question 35:

  As a developer, which of the following snippets will enable you to run the commands npm ci and npm run build as part of a workflow?

  A. - run: | npm ci npm run build
  B. - shell: npm ci npm run build
  C. - run: | npm ci npm run build shell: nodejs
  D. - run: npm ci npm run build
  E. - shell: | npm ci npm run build
  A. - run: | npm ci npm run build

  ---

  Explanation

  Use the run: keyword only, not the shell keyword.

  Use the special character |.

  Note: There are two ways to run commands one after another on Github Actions.

  On the same step:

  steps:

  -name: Run both python files

  run: |

  python manage.py runserver

  python abc.py

  On different steps (that will run in sequence):

  steps:

  -

  name: Run first python file

  run: python manage.py runserver

  -

  name: Run second python file

  run: python abc.py

  Incorrect:

  [Not B, Not E] Use run not shell.

  [Not C] Use run only, not the shell command.

  [Not D] Need to use the | character.

  https://stackoverflow.com/questions/71047777/how-to-run-two-commands-on-github-actions-instance-one-after-another

• Question 36:

  In which locations can actions be referenced by workflows? (Each correct answer presents a complete solution. Choose three.)

  A. an .action extension file in the repository
  B. a published Docker container image on Docker Hub
  C. a public NPM registry
  D. the runs-on: keyword of a workflow file
  E. the repository’s Secrets settings page
  F. a separate public repository
  G. the same repository as the workflow
  B. a published Docker container image on Docker Hub
  C. a public NPM registry
  F. a separate public repository

  ---

  Explanation

  Adding an action to your workflow

  You can add an action to your workflow by referencing the action in your workflow file. The actions you use in your workflow can be defined in:

  [F] The same repository as your workflow file

  [C] Any public repository

  [B] A published Docker container image on Docker Hub

  Note: Adding an action from the same repository [F]

  If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the {owner}/{repo}@{ref} or ./path/to/dir syntax in your workflow file.

  https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/find-and-customize-actions

• Question 37:

  What are the two ways to pass data between jobs? (Each correct answer presents part of the solution. Choose two.)

  A. Use data storage.
  B. Use the copy action with cache parameter to cache the data.
  C. Use the copy action with restore parameter to restore the data from the cache.
  D. Use artifact storage.
  E. Use job outputs.
  F. Use the copy action to save the data that should be passed in the artifacts folder.
  D. Use artifact storage.
  E. Use job outputs.

  ---

  Explanation

  Passing information between jobs

  [D] Store and share data with workflow artifacts Use artifacts to share data between jobs in a workflow and store data once that workflow has completed.

  [E] You can define outputs to pass information from one job to another.

  Defining and using job outputs

  1.Open the workflow file containing the job you want to get outputs from.

  2.Use the jobs..outputs syntax to define the outputs for the job. For example, the following job defines the output1 and output2 outputs, which are mapped to the results of step1 and step2 respectively:

  jobs:

  job1:

  runs-on: ubuntu-latest

  outputs:

  output1: ${{ steps.step1.outputs.test }}

  output2: ${{ steps.step2.outputs.test }}

  steps:

  -

  id: step1

  run: echo "test=hello" >> "$GITHUB_OUTPUT"

  -id: step2 run: echo "test=world" >> "$GITHUB_OUTPUT"

  3.Etc.

  https://docs.github.com/en/actions/tutorials/store-and-share-data https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/pass-job-outputs

• Question 38:

  You need to trigger a workflow using the GitHub API for activity that happens outside of GitHub. Which workflow event do you use?

  A. workflow_run
  B. deployment
  C. check_suite
  D. repository_dispatch
  D. repository_dispatch

  ---

  Explanation

  You can use the GitHub API to trigger a webhook event called repository_dispatch when you want to trigger a workflow for activity that happens outside of GitHub .

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

• Question 39:

  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. Add your runner to the appropriate runner groups.
  B. In the workflow, specify: runs-on: [ ${{groups.macos-10.15}}, ${{groups.xcode-11.2}} ].
  C. Create custom runner labels for macos-10.15 and xcode-11.2.
  D. Create runner groups named macos-10.15 and xcode-11.2.
  E. In the workflow, specify: runs-on: [self-hosted, macos-10.15, xcode-11.2].
  F. Assign the custom labels to the self-hosted runner.
  C. Create custom runner labels for macos-10.15 and xcode-11.2.
  E. In the workflow, specify: runs-on: [self-hosted, macos-10.15, xcode-11.2].
  F. Assign the custom labels to the self-hosted runner.

  ---

  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.

  https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/use-in-a-workflow

• Question 40:

  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]
  A. runs-on: [self-hosted, windows, x64]

  ---

  Explanation

  Using self-hosted runners in a workflow

  To use self-hosted runners in a workflow, you can use labels or groups to specify the runner for a job.

  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.

  https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/use-in-a-workflow