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

GitHub Marketplace is used to discover, share, and publish reusable automation, including GitHub Actions created by GitHub, vendors, and the community. Option C best describes this role. Marketplace does not exist only for billing, so option B is too narrow and incorrect. Option A is also wrong because Marketplace does not merely restrict third-party actions to public repositories; action usage is governed by repository, organization, or enterprise Actions policies. Option D is false because Marketplace does not bypass repository permissions or automatically deploy workflows into repositories. In exam terms, Marketplace is part of the automation reuse and action discovery domain: developers use it to find trusted or verified actions rather than building every integration manually. GitHub documents Marketplace as a place to publish and share actions with the community.

GitHub Actions supports the use of service containers, which allows you to spin up a PostgreSQL database (or any other service) in a Docker container during your workflow. You can pull a PostgreSQL image from Docker Hub, and the container will automatically be available to your workflow job. This method requires no additional infrastructure and is easy to configure and maintain, as you simply define the container in the workflow file.

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.

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

First, the dataset should be encrypted before being stored. This ensures that the data is protected when stored in a repository.

The encrypted dataset can be stored in a GitHub secret, ensuring it is securely kept and not exposed publicly.

The encryption key needed to decrypt the dataset should also be stored in a GitHub secret to maintain security during the workflow, allowing access only when needed.

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.

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

Creating workflow templates in the organization’s .github repository allows the organization to standardize workflows and make them easily reusable across multiple repositories. This ensures consistency and simplifies maintenance.

Creating reusable actions and workflows that can be called from other workflows helps modularize and standardize automation tasks. These reusable components can be maintained centrally and called from different workflows across repositories.

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.

Setting a debug message using ::debug:: command sends a message to the logs, helping with troubleshooting and providing insight into the workflow run.

Setting output parameters using ::set-output sends data from a job step to subsequent steps or jobs, which can be used later in the workflow.

The workflow_call event is used to trigger a reusable workflow from another workflow. This allows you to create workflows that can be reused in multiple places within your organization, enabling better modularity and reducing duplication.

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.