Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 91:

  Where should workflow files be stored to be triggered by events in a repository?

  A. anywhere
  B. Nowhere; they must be attached to an action in the GitHub user interface.
  C. .github/workflows/
  D. .workflows/
  E. .github/actions/
  B. Nowhere; they must be attached to an action in the GitHub user interface.

  ---

  Explanation

  You must store workflow files in the .github/workflows directory of your repository.

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

• Question 92:

  While awaiting approval, how many days can a workflow be in the “Waiting” state before it automatically fails?

  A. 30 days
  B. 60 days
  C. 14 days
  D. 7 days
  A. 30 days

  ---

  Explanation

  Using required reviews in workflows Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30

  days, it will automatically fail.

  https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/control-deployments

• Question 93:

  What is the most suitable action type for a custom action written in TypeScript?

  A. Docker container action
  B. Bash script action
  C. composite run step
  D. JavaScript action
  D. JavaScript action

  ---

  Explanation

  Example: Build your custom GitHub Action

  To build your action, run npm run bundle. This will compile the TypeScript code in the src/ directory and output the JavaScript code in the dist/ directory. The exact command for bundle is defined in the package.json file.

  Note: About custom actions

  Actions are individual tasks that you can combine to create jobs and customize your workflow.

  Types of action

  You can build Docker container, JavaScript, and composite actions.

  https://victoronsoftware.com/posts/typescript-github-action/

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

• Question 94:

  Custom environment variables can be defined at multiple levels within a workflow file including: (Each answer presents a complete solution. Choose three.)

  A. top level.
  B. step level.
  C. default level.
  D. runner level.
  E. job level.
  F. stage level.
  A. top level.
  B. step level.
  E. job level.

  ---

  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..env. 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 95:

  Which workflow event is used to manually trigger a workflow run?

  A. status
  B. workflow_dispatch
  C. workflow_run
  D. create
  B. workflow_dispatch

  ---

  Explanation

  Manually running a workflow

  When a workflow is configured to run on the workflow_dispatch event, you can run the workflow using the Actions tab on GitHub, GitHub CLI, or the REST API.

  Configuring a workflow to run manually

  To run a workflow manually, the workflow must be configured to run on the workflow_dispatch event.

  To trigger the workflow_dispatch event, your workflow must be in the default branch.

  https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manually-run-a-workflow

• Question 96:

  As a developer, you need to leverage Redis in your workflow. What is the best way to use Redis on a self-hosted Linux runner without affecting future workflow runs?

  A. Install Redis on the hosted runner image and place it in a runner group. Specify label: in your job to target the runner group.
  B. Set up Redis on a separate machine and reference that instance from your job.
  C. Specify container: and services: in your job definition to leverage a Redis service container.
  D. Add a run step to your workflow, which dynamically installs and configures Redis as part of your job.
  C. Specify container: and services: in your job definition to leverage a Redis service container.

  ---

  Explanation

  Creating Redis service containers

  You can use service containers to create a Redis client in your workflow. You can create a Redis service for jobs that run in containers or directly on the runner machine.

  Configuring the runner job

  The example uses the ubuntu-latest GitHub-hosted runner as the Docker host.

  The workflow configures a service container with the label redis.

  jobs:

  # Label of the runner job

  runner-job:

  # You must use a Linux environment when using service containers or container jobs

  runs-on: ubuntu-latest

  # Service containers to run with `runner-job`

  services:

  # Label used to access the service container

  redis:

  # Docker Hub image

  image: redis

  # Set health checks to wait until redis has started

  options: >--health-cmd "redis-cli ping"

  --health-interval 10s

  --health-timeout 5s

  --health-retries 5

  ports:

  # Maps port 6379 on service container to the host

  -6379:6379

  https://docs.github.com/en/actions/tutorials/use-containerized-services/create-redis-service-containers

• Question 97:

  Which statement is true regarding the ability to delete a workflow run?

  A. Admin access is required to delete a workflow run.
  B. Pending workflow runs may be deleted.
  C. Completed workflow runs may be deleted.
  D. Workflow runs must be older than 30 days to be deleted.
  C. Completed workflow runs may be deleted.

  ---

  Explanation

  Deleting a workflow run

  You can delete a workflow run that has been completed, or is more than two weeks old.

  https://docs.github.com/en/enterprise-cloud@latest/actions/how-tos/manage-workflow-runs/delete-a-workflow-run

• Question 98:

  What is the smallest scope for an environment variable?

  A. the workflow settings
  B. the workflow env mapping
  C. a job
  D. a step
  D. a step

  ---

  Explanation

  In GitHub Actions, environment variables can be defined at three different scopes: workflow, job, and step. Each scope determines the visibility and lifetime of the environment variable across the workflow execution.

  Variables defined at the workflow scope are available to all jobs and steps within the workflow.

  Variables defined at the job scope are available to all steps within a specific job.

  Variables defined at the step scope are only available to the step in which they are defined. They are declared within a step and are not visible outside of that step.

  https://medium.com/@leroyleowdev/github-actions-ways-to-share-data-between-jobs-4267ff9ac2ce