Halloween Sale Special Limited Time 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = drift75

Home
Microsoft
GitHub Administrator
GH-200
GitHub Actions Exam Questions and Answers

Pass the Microsoft GitHub Administrator GH-200 Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam GH-200 Premium Access

View all detail and faqs for the GH-200 exam

Go to Exam

690 Students Passed

96% Average Score

94% Same Questions

Viewing page 5 out of 5 pages

Viewing questions 41-50 out of questions

Questions # 41:

What are the two types of environment protection rules you can configure? (Choose two.)

Options:

required reviewers

branch protections

wait timer

artifact storage

Answer

A, C

Explanation

Required reviewers is a protection rule where you can specify that certain individuals or teams must review and approve the workflow run before it can proceed. This is used to enforce approvals before certain steps or environments are accessed.

Wait timer is a protection rule that introduces a delay before a workflow can proceed to the next stage. This is useful for adding time-based constraints to the deployment process or ensuring that certain conditions are met before a workflow continues.

Questions # 42:

A development team has been using a Powershell script to compile and package their solution using existing tools on a Linux VM, which has been configured as a self-hosted runner. They would like to use the script as-is in an automated workflow. Which of the following should they do to invoke their script within a workflow step?

Options:

Configure a self-hosted runner on Windows with the requested tools.

Use the YAML powershell: step.

Run the pwsh2bash command to convert the script so it can be run on Linux.

Use the YAML shell: pwsh in a run step.

Use the actions/run-powershell action to invoke the script.

Answer

Explanation

Since the self-hosted runner is configured on a Linux VM and the script is written in PowerShell, you can invoke the script using the pwsh (PowerShell Core) shell in a run step in the workflow. This ensures that the script runs as-is on the Linux runner, as PowerShell Core (pwsh) is cross-platform and supports Linux.

Questions # 43:

As a developer, you need to create a custom action written in Python. Which action type should you choose?

Options:

JavaScript action

composite run step

Python action

Docker container action

Answer

Explanation

A Docker container action is ideal for custom actions that require specific environments or dependencies, such as Python. By creating a Docker container, you can define the environment with the necessary Python version and dependencies, and your Python code can run inside that container.

Questions # 44:

Which run: command will set a step's output?

Options:

run: echo "MY_OUTPUT=foo" >> $GITHUB_OUTPUT

run: export MY_OUTPUT=foo

run: echo ${{ $GITHUB_OUTPUT=foo }}

run: echo "::set-env name=MY OUTPUT::foo"

Answer

Explanation

The $GITHUB_OUTPUT file is used to pass data from one step to another in GitHub Actions. The echo command appends the key-value pair to this file, which sets the output variable (MY_OUTPUT) for the current step.

Questions # 45:

When creating and managing custom actions in an enterprise setting, which of the following is considered a best practice?

Options:

creating a separate repository for each action so that the version can be managed independently

creating a separate branch in application repositories that only contains the actions

creating a single repository for all custom actions so that the versions for each action are all the same

including custom actions that other teams need to reference in the same repository as application code

Answer

Explanation

Creating a separate repository for each custom action allows you to manage the versioning independently for each action. This approach provides flexibility, as each action can be updated, tested, and versioned separately, avoiding potential conflicts or dependencies between different actions.

Questions # 46:

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? (Choose two.)

Options:

Use caching when reusing files that change rarely between jobs or workflow runs.

Use artifacts when referencing files produced by a job after a workflow has ended.

Use caching to store cache entries for up to 30 days between accesses.

Use artifacts to access the GitHub Package Registry and download a package for a workflow

Answer

A, B

Explanation

Caching is ideal for files that change rarely, such as dependencies or build outputs, as it speeds up subsequent workflow runs by reusing previously cached files instead of re-downloading or rebuilding them.

Artifacts are used for persisting files produced during a job that need to be used in later jobs or after the workflow has ended, allowing them to be downloaded or referenced later.

Questions # 47:

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

Options:

Create a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.

It is not possible; if an action is in the marketplace, its use cannot be restricted.

Create a list that is maintained as a . yml file in a . github repository specified in the enterprise. Only these actions can be run.

Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.

Answer

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.

Questions # 48:

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?

Options:

POST /repos/:owner/:repo/actions/runs/:run_id

GET /repos/:owner/:repo/actions/artifacts/logs

GET /repos/:owner/:repo/actions/runs/:run_id/logs

POST /repos/:owner/:repo/actions/runs/:run_id/logs

Answer

Explanation

The GET /repos/:owner/:repo/actions/runs/:run_id/logs API endpoint is used to retrieve the logs of a specific workflow run identified by run_id. This is the correct method for downloading logs from a workflow run.

Questions # 49:

Which default environment variable specifies the branch or tag that triggered a workflow?

Options:

GITHUB_TAG

GITHUB_REF

ENV_BRANCH

GITHUB_BRANCH

Answer

Explanation

The GITHUB_REF environment variable specifies the branch or tag that triggered the workflow. It contains the full reference to the branch or tag, such as refs/heads/main for a branch or refs/tags/v1.0 for a tag.

Questions # 50:

Which workflow command would output the debug message "action successfully debugged"?

Options:

echo :debug::message=action successfully debugged"

echo "debug-action successfully debugged"

echo "::debug::action successfully debugged"

echo ":debug:action successfully debugged:"

Answer

Explanation

The ::debug:: syntax is used to output debug messages in GitHub Actions workflows. This command will print the message "action successfully debugged" in the debug logs when the workflow runs.

Viewing page 5 out of 5 pages

Viewing questions 41-50 out of questions