Microsoft GH-200 Online Practice Questions and Exam Preparation

Microsoft GH-200 Online Questions & Answers

• Question 1:

  As a developer, you are designing a workflow and need to communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks. Which of the following options should you use?

  A. composite run step
  B. enable debug logging
  C. self-hosted runners
  D. environment variables
  E. workflow commands
  E. workflow commands

  ---

  Explanation

  Workflow commands for GitHub Actions

  You can use workflow commands when running shell commands in a workflow or in an action's code.

  About workflow commands

  Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.

  Most workflow commands use the echo command in a specific format, while others are invoked by writing to a file.

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

• Question 2:

  Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

  A. passing the GITHUB_TOKEN secret to an action that requires a token as an input
  B. making an authenticated GitHub API request
  C. checking out source code with the actions/checkout@v3 action
  D. assigning non-default permissions to the GITHUB_TOKEN
  A. passing the GITHUB_TOKEN secret to an action that requires a token as an input
  B. making an authenticated GitHub API request

  ---

  Explanation

  [A] Some actions may require a GITHUB_TOKEN as an input to authenticate and perform specific tasks, such as creating issues, commenting on pull requests, or interacting with the GitHub API. In such cases, you would need to explicitly

  pass the token to the action.

  [B] When making an authenticated GitHub API request, the GITHUB_TOKEN is required to authenticate the request. This token is automatically provided by GitHub in the workflow, and it must be explicitly used when interacting with the

  GitHub API.

  Note: You can use the GITHUB_TOKEN to make authenticated API calls. This example workflow creates an issue using the GitHub REST API:

  name: Create issue on commit

  on: [ push ]

  jobs:

  create_issue:

  runs-on: ubuntu-latest

  permissions:

  issues: write

  steps:

  -name: Create issue using REST API

  run: |

  curl --request POST \

  --url https://api.github.com/repos/${{ github.repository }}/issues \

  --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \

  --header 'content-type: application/json' \

  --data '{

  "title": "Automated issue for commit: ${{ github.sha }}", "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_." }' \ --fail

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

• Question 3:

  Which of the following is a valid reusable workflow reference?

  A. uses: octo-org/another-repo/workflow.yml@v1
  B. uses: octo-org/another-repo/.github/workflows/workflow.yml@v1
  C. uses: another-repo/.github/workflows/workflow.yml@v1
  D. uses: another-repo/workflow.yml@v1
  B. uses: octo-org/another-repo/.github/workflows/workflow.yml@v1

  ---

  Explanation

  Calling a reusable workflow

  You call a reusable workflow by using the uses keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.

  jobs..uses

  You reference reusable workflow files using one of the following syntaxes:

  *-> {owner}/{repo}/.github/workflows/{filename}@{ref} for reusable workflows in public and private repositories.

  * ./.github/workflows/{filename} for reusable workflows in the same repository.

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

• Question 4:

  A workflow that had been working now stalls in a waiting state until failing. The workflow file process-ml.yaml has not changed and contains jobs specifying runs-on: [gpu ]. Which of the following steps would troubleshoot the issue? (Each answer presents a complete solution. Choose two.)

  A. Review the contents of the Runner_*.log files in the _diag folder.
  B. Increase the usage limits for the GitHub-hosted runners.
  C. Check the “Set up job” step for the logs of the last successful run to determine the runner.
  D. Update the org settings to enable GPU-based GitHub-hosted runners.
  E. Rotate the GITHUB_TOKEN secret for the appropriate runners.
  A. Review the contents of the Runner_*.log files in the _diag folder.
  D. Update the org settings to enable GPU-based GitHub-hosted runners.

  ---

  Explanation

  Monitoring and troubleshooting self-hosted runners

  You can monitor your self-hosted runners to view their activity and diagnose common issues.

  [A] Reviewing the self-hosted runner application log files You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the _diag directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with Runner_, and is followed by a UTC timestamp of when the application was started.

  [D] You can choose one of the standard GitHub-hosted runner options or, if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU processor. These machines are referred to as "larger runner."

  https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/monitor-and-troubleshoot https://docs.github.com/en/actions/concepts/runners/github-hosted-runners

• Question 5:

  As a developer, you need to make sure that only actions from trusted sources are available for use in your GitHub Enterprise Cloud organization. Which of the following statements are true? (Each correct answer presents a complete solution. Choose three.)

  A. Actions can be published to an internal marketplace.
  B. GitHub-verified actions can be collectively enabled for use in the enterprise.
  C. Specific actions can individually be enabled for the organization, including version information.
  D. Actions can be restricted to only those available in the enterprise.
  E. Individual third-party actions enabled with a specific tag will prevent updated versions of the action from introducing vulnerabilities.
  F. Actions created by GitHub are automatically enabled and cannot be disabled.
  A. Actions can be published to an internal marketplace.
  B. GitHub-verified actions can be collectively enabled for use in the enterprise.
  C. Specific actions can individually be enabled for the organization, including version information.

  ---

  Explanation

  [A] Internal Actions Marketplace The reason for having an internal actions marketplace is to have a central location for all the actions that can be used inside our production organization. This is to prevent any actions from the public marketplace from being used in our production organization, without being checked for security risks first.

  [B] Allow Marketplace actions by verified creators: You can allow all GitHub Marketplace actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the badge is displayed next to the action in GitHub Marketplace.

  [C] You can enable specific actions for the organization by identifying them and providing version control, ensuring only trusted versions are used in workflows. Incorrect:

  [Not F] Disabling or limiting GitHub Actions for your organization

  You can enable, disable, and limit GitHub Actions for an organization.

  https://devopsjournal.io/blog/2021/10/14/GitHub-Actions-Internal-Marketplace

  https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/

  disabling-or-limiting-github-actions-for-your-organization

• Question 6:

  What is the right method to ensure users approve a workflow before the next step proceeds?

  A. creating a branch protection rule and only allow certain users access
  B. granting users workflow approval permissions
  C. adding users as required reviewers for an environment
  D. granting users repository approval permission
  C. adding users as required reviewers for an environment

  ---

  Explanation

  GitHub Actions allows you to configure environment protection rules, where you can require specific users or teams to approve the deployment before the workflow proceeds to the next step. This ensures that the required reviewers approve

  the workflow before any sensitive actions (such as deployment) occur.

  Note: Managing environments for deployment

  You can create environments and secure those environments with deployment protection rules. A job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.

  Optionally, you can specify people or teams that must approve workflow jobs that use this environment.

  Select Required reviewers.

  Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.

  Optionally, to prevent users from approving workflows runs that they triggered, select Prevent self-review.

  Click Save protection rules.

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

• Question 7:

  Which of the following commands will set the $FOO environment variable within a script, so that it may be used in subsequent workflow job steps?

  A. run: echo "::set-env name=FOO::bar"
  B. run: echo "FOO=bar" >> $GITHUB_ENV
  C. run: echo ${{ $FOO=bar }}
  D. run: export FOO=bar
  B. run: echo "FOO=bar" >> $GITHUB_ENV

  ---

  Explanation

  The $GITHUB_ENV environment variable is used to set environment variables that persist across steps in a workflow job. By echoing FOO=bar into $GITHUB_ENV, the variable FOO will be available in subsequent steps within the same job.

  Variables set in GITHUB_ENV apply only to the current job.

  Example:

  echo "PR_NUMBER=$pr_number" >> $GITHUB_ENV

  https://github.com/orgs/community/discussions/56849

• Question 8:

  Which of the following is the best way for an enterprise to prevent certain marketplace actions from running?

  A. Create a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.
  B. It is not possible; if an action is in the marketplace, its use cannot be restricted.
  C. Create a list that is maintained as a . yml file in a . github repository specified in the enterprise. Only these actions can be run.
  D. Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.
  D. Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.

  ---

  Explanation

  The best way for an enterprise to control which GitHub Actions run is by creating a list of approved actions as an enterprise policy. This approach restricts workflows to only use the actions that are explicitly allowed, ensuring security and compliance within the organization.

  Note: To allow a specific list of actions at the GitHub Enterprise level, an administrator must navigate to Enterprise > Policies > Actions and select "Allow select actions". Then, from the dropdown menus, they choose "Allow selected actions and reusable workflows" and add the desired actions to the allowed list using the format OWNER/REPOSITORY@TAG-OR-SHA. These actions can also include local actions, actions from specific organizations, or specific tags or commit SHAs.

  https://docs.github.com/en/enterprise-cloud@latest/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise

• Question 9:

  You are designing a reusable workflow that other repositories will use. What’s required for others to access it?

  A. It must be stored in .github/workflows/ and the repo must be public or internal
  B. It must include an action.yml file
  C. It must be listed in GitHub Marketplace
  D. It must be stored in .github/actions/
  A. It must be stored in .github/workflows/ and the repo must be public or internal

  ---

  Explanation

  Reusable workflows must be defined in .github/workflows/ and accessible via public or internal visibility for external use.

• Question 10:

  You are a DevOps engineer working on deployment workflows. You need to execute the deploy job only if the current branch name is feature-branch. Which code snippet will help you to implement the conditional execution of the job?

  A. jobs: deploy: if: github.ref_name == 'feature-branch' runs-on: ubuntu-latest steps: -uses: actions/checkout@v3
  B. jobs: deploy: if: github.branch.name == 'feature-branch' runs-on: ubuntu-latest steps: -uses: actions/checkout@v3
  C. jobs: deploy: if: github.ref.name == 'feature-branch' runs-on: ubuntu-latest steps: -uses: actions/checkout@v3
  D. jobs: deploy: if: github.branch_name == 'feature-branch' runs-on: ubuntu-latest steps: -uses: actions/checkout@v3
  A. jobs: deploy: if: github.ref_name == 'feature-branch' runs-on: ubuntu-latest steps: -uses: actions/checkout@v3

  ---

  Explanation

  "ref_name" refers to the short name of a Git branch or tag, as seen on platforms like GitHub, and is often used in CI/CD workflows to specify which code to build or deploy. For example, when a workflow is triggered by a commit to the featurebranch-1 branch, the github.ref_name would be feature-branch-1.

  In GitHub Actions:

  Purpose:

  github.ref_name is a read-only context variable that contains the short name of the branch or tag that triggered the workflow.

  Examples:

  If a workflow is triggered by a commit to the main branch, github.ref_name would be main.

  If it's triggered by a new tag, such as v1.2.3, github.ref_name would be v1.2.3.

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