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

A matrix strategy allows you to define different versions of a programming language (or any other environment setting) and run tests on each version simultaneously. This is particularly useful for testing code compatibility across different versions of a language.

A matrix strategy can also be used to test code on multiple operating systems (e.g., Windows, macOS, Linux) by defining these operating systems as matrix variables. This enables cross-platform testing within the same workflow.

Scheduled GitHub Actions workflows use the schedule event beneath the workflow ' s on key. Each schedule is represented by a cron entry, which makes option A the valid structure. GitHub scheduled workflows use POSIX-style five-field cron syntax, and scheduled execution is interpreted in UTC by default. In the expression 45 7 * * 3,6, 45 represents minute 45, 7 represents 07:00 UTC, the two asterisks allow every day of the month and every month, and 3,6 specifies Wednesday and Saturday. Consequently, the workflow is scheduled for 07:45 UTC on both requested weekdays. Options B and D incorrectly place cron directly beneath on, while option C does not use the required schedule list containing a cron entry.

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

GITHUB_WORKSPACE is a default environment variable in GitHub Actions that points to the directory on the runner where your repository is checked out. This variable allows you to access files within your repository during the workflow.

Scheduled workflows in GitHub Actions are triggered at specified times, and they run on the latest commit of the branch that triggers the workflow. This means the workflow will run on the most recent commit on the branch that was active at the time the scheduled event occurs.

A TypeScript-based GitHub Action is implemented as a JavaScript action because TypeScript is compiled or bundled into JavaScript before execution by the GitHub Actions runner. JavaScript actions use an action.yml metadata file whose runs.using value specifies a supported Node.js runtime and whose runs.main property identifies the generated JavaScript entry point, commonly a file under dist. This approach allows the action to run directly on supported Linux, Windows, and macOS runners without requiring a separate Docker container. A composite action is intended primarily to combine reusable workflow steps, while a Bash script action is not a distinct metadata action type. Docker container actions are appropriate when a packaged container environment is specifically required. Therefore, a custom action authored in TypeScript should be packaged and distributed as a JavaScript action.

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

For a run step in a composite action, GitHub Actions supports the working-directory property to specify the directory in which the command executes. The property belongs to the individual step, alongside properties such as run and shell. The generic keyword directory is not part of GitHub Actions metadata syntax. Composite actions declare runs.using: composite, after which runs.steps defines the reusable sequence of commands or actions. An input such as inputs.dir can therefore be referenced through an expression and assigned to working-directory. GitHub ' s action metadata reference explicitly defines runs.steps[*].working-directory as the supported property for controlling the execution directory of a composite-action command. Therefore, option B is the valid implementation.

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

GitHub Actions routes jobs to self-hosted runners by using runner labels. Custom labels representing required capabilities, such as the operating-system version and Xcode version, can be created and assigned to the appropriate runner. The workflow then specifies those labels in runs-on. When multiple labels are supplied, GitHub requires an eligible runner to match all specified labels, so runs-on: [self-hosted, macos-10.15, xcode-11.2] targets the intended runner configuration. Runner groups are primarily an access-control and organizational mechanism and are not represented by the ${{ groups.* }} expression shown in option B. The Xcode/macOS versions in this exam scenario are historical, but the runner-label routing principle remains current. GitHub documentation confirms custom labels and cumulative runs-on label matching.

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

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.

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

Actions can be stored in a separate public repository and referenced in workflows by specifying the repository and action name.

Actions can also be stored in the same repository as the workflow and referenced directly by their path (e.g., ./.github/actions/my-action).

Actions can be packaged as Docker container images and published to Docker Hub. These can then be referenced in workflows by specifying the Docker image.

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.