GH-200 Exam Dumps - Microsoft GitHub Administrator Questions and Answers

GitHub Actions provides the debug workflow command for writing debug-level messages to the workflow log. The command syntax is ::debug::{message}, so option B correctly sends the message to the runner through standard output. To make these debug messages visible in workflow logs, step debug logging must also be enabled using ACTIONS_STEP_DEBUG=true. Option A refers to a nonexistent $DEBUG_MESSAGE environment file. Option C uses add-mask, which instructs GitHub to redact a value from logs rather than print diagnostic information. Option D writes a value to GITHUB_OUTPUT, which creates a step output instead of a debug message. GitHub documents the Bash syntax with echo " ::debug::message " , making option B the supported workflow-command format.

================

The workflow_run event is designed to trigger one workflow based on the execution or completion of another workflow. The deployment workflow can therefore specify the build workflow under on.workflow_run.workflows and use the completed activity type without changing the original build workflow. One important detail is that workflow_run fires when the specified workflow completes regardless of whether it succeeded or failed. If deployment must occur only after a successful build, the deployment job should additionally use a condition such as github.event.workflow_run.conclusion == ' success ' . workflow_dispatch is a manual trigger, repository_dispatch is normally used for externally generated custom events through the GitHub API, and workflow_exec is not a GitHub Actions workflow event. Therefore, workflow_run is the correct trigger.

================

A job using runs-on: [gpu] depends on an available runner matching that label. If the workflow previously succeeded but now remains waiting, the runner ' s availability, registration, connectivity, or label assignment should be investigated. GitHub stores self-hosted runner application diagnostic logs in the runner installation ' s _diag directory; Runner_ log files provide details about runner startup, connectivity, registration, and update activity, making option A useful. Checking the Set up job information from a previous successful run can also identify which runner previously accepted the job, providing a concrete target for investigation. Rotating GITHUB_TOKEN does not repair runner scheduling because job assignment does not depend on manually rotating that workflow token. GitHub-hosted usage limits are similarly unrelated to a custom gpu runner label. Therefore, A and C are appropriate troubleshooting actions.

================

GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free-tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency.

Self-hosted runners allow you to configure specialized hardware or software setups that are necessary for certain workflows. GitHub-hosted runners may not have access to custom hardware configurations like GPUs or other specialized resources, so self-hosted runners are required in such cases.

A composite action is identified by its action metadata file. In action.yml or action.yaml, the runs section must define using: " composite " . This tells GitHub Actions that the action is a composite action made from one or more reusable workflow steps. Option A is incorrect because Dockerfile and package.json files do not identify a composite action; they are usually associated with Docker or JavaScript-based projects. Option C is wrong because repository naming has no technical meaning in action classification. Option D is also wrong because an init.sh file is merely a script and does not define the action type. GitHub’s metadata syntax states that composite actions require runs.using to be set to composite.

When a workflow job targets an environment that has required reviewers, the job enters a waiting state until it is approved or rejected. GitHub Actions does not allow that waiting state to remain indefinitely. If the job is not approved within the allowed period, the workflow fails automatically. The correct duration is 30 days, making option C correct. Options A, B, and D do not match the GitHub Actions environment approval behavior. This is important for deployment governance because required reviewers can block access to protected environments and environment secrets, but pending approvals still have a maximum lifetime. This exam topic aligns with protected environments, deployment approvals, required reviewers, and workflow execution control.

================

When troubleshooting a self-hosted runner, you can access the _diag folder located in the self-hosted runner ' s installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.

A. Use the actions/setup-docker action

B. Authenticate to the GitHub Container Registry.

C. Build the container image.

D. Push the image to the GitHub Container Registry

E. Pull the image from the GitHub Container Registry.

GitHub-hosted runners automatically handle patching, meaning they will be kept up to date with the latest security updates and software patches for both the runner environment and the underlying operating system.

GitHub-hosted runners support Linux, Windows, and macOS, giving you flexibility to run workflows on different operating systems without needing to manage your own self-hosted runners.

GitHub Actions supports the env key at three workflow syntax scopes: the workflow ' s top level, an individual job, and an individual step. A top-level env value is available to steps across all jobs in the workflow. jobs. < job_id > .env limits variables to the steps of one job, while jobs. < job_id > .steps[*].env limits them to a particular step. When the same variable name is defined at several levels, the most specific definition takes precedence while that scope executes. GitHub Actions does not define a generic stage scope, and defaults is used for default settings such as the shell or working directory rather than as another env scope. Likewise, runner level is not a workflow-file env scope. Therefore, step, top, and job levels are correct.

================