Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 71:

  As a developer, you are authoring a workflow that will deploy to both DevCloud and TestCloud resources. Each cloud resource is accessed with a different deployment key. Which approach best allows you to use the same reusable workflow in separate jobs to target the different cloud resources?

  A. Populate a DEPLOY_KEY repository secret with a JSON object containing DevCloud and TestCloud properties. Then specify DEPLOY_KEY.DevCloud in the secrets sections of the reusable workflow.
  B. Use a marketplace action to conditionally parse the DEPLOY_KEY repository secret based on the cloud resource name.
  C. Store the different keys in a DEPLOY_KEY environment secret in the DevCloud and TestCloud environments. Specify DEPLOY_KEY in the secrets section of the reusable workflow.
  D. Create repository secrets named DevCloud.DEPLOY_KEY and TestCloud.DEPLOY_KEY so that the reusable workflow parses the secrets by resource name.
  C. Store the different keys in a DEPLOY_KEY environment secret in the DevCloud and TestCloud environments. Specify DEPLOY_KEY in the secrets section of the reusable workflow.

  ---

  Explanation

  Using inputs and secrets in a reusable workflow

  You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow.

  In the reusable workflow, use the inputs and secrets keywords to define inputs or secrets that will be passed from a caller workflow.

  on: workflow_call: inputs:

  config-path:

  required: true

  type: string

  secrets:

  personal_access_token:

  required: true

  https://docs.github.com/en/enterprise-cloud@latest/actions/how-tos/reuse-automations/reuse-workflows

• Question 72:

  As a developer, how can you identify a JavaScript action on GitHub?

  A. The action’s repository includes a js.yml file in the .github/workflows directory.
  B. The action’s repository name includes the keyword “JavaScript.”
  C. The action.yml metadata file has the runs.using value set to node16.
  D. The action.yml metadata file references a package.json file.
  D. The action.yml metadata file references a package.json file.

  ---

  Explanation

  Creating a JavaScript action, example

  Prerequisites

  Before you begin, you'll need to download Node.js and create a public GitHub repository.

  * steps omitted *

  From your terminal, initialize the directory with npm to generate a package.json file.

  npm init -y

  Adding actions toolkit packages The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.

  When you commit and push your code, your updated repository should look like this:

  hello-world-javascript-action/ ├── action.yml ├── dist/ │ └── index.js ├── package.json ├── package-lock.json ├── README.md ├── rollup.config.js └── src/

  └── index.js

  https://docs.github.com/en/actions/tutorials/create-actions/create-a-javascript-action#creating-an-action-metadata-file

• Question 73:

  You must share a secret across multiple repositories in your enterprise. What’s the correct scope for the secret?

  A. repository secret
  B. environment secret
  C. organization secret
  D. enterprise secret
  D. enterprise secret

  ---

  Explanation

  Enterprise secrets allow sharing sensitive credentials across all repositories within the enterprise, subject to policy configuration.

  Managing secrets at the enterprise level

• Question 74:

  As a developer, how can you identify a composite action on GitHub?

  A. The action’s repository name includes the keyword “composite.”
  B. The action’s repository includes an init.sh file in the root directory.
  C. The action’s repository includes Dockerfile and package.json files.
  D. The action.yml metadata file has the runs.using value set to composite.
  D. The action.yml metadata file has the runs.using value set to composite.

  ---

  Explanation

  runs.using for composite actions

  Required: You must set this value to 'composite'.

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

• Question 75:

  Which action type should be used to bundle a series of run steps into a reusable custom action?

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

  ---

  Explanation

  Reusable workflows versus composite actions Reusable workflows and composite actions both help you avoid duplicating workflow content. Whereas reusable workflows allow you to reuse an entire workflow, with multiple jobs and steps,

  composite actions combine multiple steps that you can then run within a job step, just like any other action.

  A composite action allows you to bundle multiple steps into a single reusable action within a workflow. It is composed of multiple run steps or other actions and can be reused across workflows, making it the perfect choice for bundling a series

  of steps.

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

• Question 76:

  As a developer, your Actions workflow often reuses the same outputs or downloaded dependencies from one run to another. To cache dependencies for a job, you are using the GitHub cache action. Which input parameters are required for this action? (Each correct answer presents part of the solution. Choose two.)

  A. path: the file path on the runner to cache or restore
  B. dependency: the name and version of a package to cache or restore
  C. key: the key created when saving a cache and the key used to search for a cache
  D. restore-keys: the copy action key used with cache parameter to cache the data
  E. cache-hit: the copy action key used with restore parameter to restore the data from the cache
  F. ref: the ref name of the branch to access and restore a cache created
  A. path: the file path on the runner to cache or restore
  C. key: the key created when saving a cache and the key used to search for a cache

  ---

  Explanation

  Input parameters for the cache action

  [C] key: Required The key created when saving a cache and the key used to search for a cache. It can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.

  [A] path: Required The path(s) on the runner to cache or restore. Incorrect: restore-keys: Optional enableCrossOsArchive: Optional

  https://docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching

• Question 77:

  You need to make a script to retrieve workflow run logs via the API. Which is the correct API to download a workflow run log?

  A. POST /repos/:owner/:repo/actions/runs/:run_id/logs
  B. GET /repos/:owner/:repo/actions/runs/:run_id/logs
  C. POST /repos/:owner/:repo/actions/runs/:run_id
  D. GET /repos/:owner/:repo/actions/artifacts/logs
  B. GET /repos/:owner/:repo/actions/runs/:run_id/logs

  ---

  Explanation

  REST API endpoints for workflow jobs

  You can use the REST API to view logs and workflow jobs in GitHub Actions.

  Download job logs for a workflow run

  Gets a redirect URL to download a plain text file of logs for a workflow job.

  Code samples for "Download job logs for a workflow run"

  Request example

  Get /repos/{owner}/{repo}/actions/jobs/{job_id}/logs

  https://docs.github.com/en/rest/actions/workflow-jobs

• Question 78:

  A single secret must be accessed by workflows in specific repositories. What is the best way to create the secret?

  A. Create an environment secret at the organization level and leverage that environment in each of the specified repositories.
  B. Create an organization secret, specify Selected repositories as the Repository access, and select the required repositories.
  C. Create the secret in one of the repositories, check the Share secret option, and select the required repositories.
  D. Store the secret in a supported external key vault. Configure OpenID Connect (OIDC) to allow access to the external vault and link the secret from the external key vault in each of the specific repositories.
  B. Create an organization secret, specify Selected repositories as the Repository access, and select the required repositories.

  ---

  Explanation

  Creating secrets for an organization

  When creating a secret or variable in an organization, you can use a policy to limit access by repository.

  For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.

  To specify that the secret should be available to selected repositories within the organization, use the --repos or -r flag.

  gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2

  Note: REST API endpoints for GitHub Actions Secrets

  Use the REST API to interact with secrets in GitHub Actions.

  * Set selected repositories for an organization secret Replaces all repositories for an organization secret when the visibility for repository access is set to selected. The visibility is set when you Create or update an organization secret. Request example Put /orgs/{org}/actions/secrets/{secret_name}/repositories

  https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets https://docs.github.com/en/rest/actions/secrets?apiVersion=2022-11-28#set-selected-repositories-for-an-organization-secret

• Question 79:

  What is the proper syntax to reference the system-provided run number variable?

  A. ${{var.GITHUB_RUN_NUMBER}}
  B. ${{env.GITHUB_RUN_NUMBER}}
  C. $GITHUB_RUN_NUMBER
  D. ${{GITHUB_RUN_NUMBER}}
  E. $github.run_number
  D. ${{GITHUB_RUN_NUMBER}}

  ---

  Explanation

  Default environment variables

  The default environment variables that GitHub sets are available to every step in a workflow.

  Because default environment variables are set by GitHub and not defined in a workflow, they are not accessible through the env context [Not B]. However, most of the default variables have a corresponding, and similarly named, context

  property. For example, the value of the GITHUB_REF variable can be read during workflow processing using the ${{ github.ref }} context property.

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

• Question 80:

  Which of the following is the proper syntax to specify a custom environment variable named MY_VARIABLE with the value my-value?

  A. var: MY_VARIABLE = my-value
  B. environment: MY_VARIABLE = my-value
  C. var: MY_VARIABLE: my-value
  D. env: MY_VARIABLE = my-value
  E. environment: MY_VARIABLE: my-value
  F. env: MY_VARIABLE: my-value
  F. env: MY_VARIABLE: my-value

  ---

  Explanation

  To set a custom environment variable for a single workflow, you can define it using the env key in the workflow file.

  Example:

  env:

  DAY_OF_WEEK: Monday

  Note: 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