Free Practice Questions for Microsoft GH-200 Exam

Using a tag is a best practice because tags are immutable and represent a fixed version of your action. By referencing tags, consumers of your action can be assured they are using a stable and specific version of the action, which helps in avoiding issues with breaking changes.

The commit SHA is another reliable way to specify a particular version of an action. By referencing a specific commit SHA, consumers can ensure they are using exactly the code that was written at that moment, avoiding the potential for changes in the future.

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

GitHub-verified actions can be enabled at the enterprise level, providing an extra layer of security by ensuring that only trusted actions are available to workflows.

Actions can be published to an internal marketplace, allowing organizations to share reusable actions securely within their enterprise without exposing them to the public.

Environment secrets are scoped to GitHub Actions environments and can be protected by environment protection rules. If an environment requires reviewers, a job that references that environment cannot access its environment secrets until the required approval is granted. This makes option A correct. Option B is incorrect because environment secrets are made available to jobs that reference the protected environment, not selectively to only one specific step by default. Option C is not the purpose of environment secrets; they are not specifically for connecting to GitHub Enterprise Server. Option D is also incorrect because GitHub environment secrets do not automatically pull from Azure Key Vault without additional integration or custom workflow logic. This topic covers environment protection, secrets, and deployment governance.

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

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.

GitHub automatically creates a GITHUB_TOKEN for workflow jobs so the workflow can authenticate to GitHub without requiring a separately maintained personal access token for many repository-scoped operations. A common use is making authenticated REST API, GraphQL API, or GitHub CLI requests against resources that the token has permission to access. The token ' s capabilities are governed by the workflow ' s permissions configuration and the repository or organization policy. It is not an SSH credential for connecting to a runner, and it is not required merely to read encrypted repository secrets that GitHub makes available through the secrets context. Likewise, simply invoking a public Marketplace action does not inherently require explicitly passing GITHUB_TOKEN. Therefore, making authenticated GitHub API calls is the correct use described by option A.

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

The best design is to use environment-scoped secrets with the same secret name, such as DEPLOY_KEY, in separate environments such as DevCloud and TestCloud. This lets the same reusable deployment logic reference one consistent secret name while the selected environment supplies the correct value. Option A is invalid because GitHub secret names should not be designed around dotted property access, and reusable workflows should not parse secret names dynamically. Option C introduces unnecessary marketplace dependency and weak secret handling. Option D is also wrong because GitHub secrets are opaque strings; ${{ secrets.DEPLOY_KEY.DevCloud }} is not valid secret property access. Reusable workflows can define and receive named secrets through the secrets mapping.

GitHub provides the ACTIONS_STEP_DEBUG setting specifically for increasing the verbosity of workflow step logs. To enable it, create a repository secret or repository variable named ACTIONS_STEP_DEBUG and assign the value true. GitHub states that if both a secret and a variable with this name exist, the secret takes precedence. After the setting is enabled, newly triggered or re-run workflows display additional debugging events in their step logs. Simply defining ACTIONS_STEP_DEBUG under the workflow ' s env or defaults section does not activate GitHub ' s step-debugging mechanism. There is also no supported --actions-step-debug workflow invocation flag. For deeper runner-level diagnostics, GitHub provides the separate ACTIONS_RUNNER_DEBUG setting. Therefore, option C is the documented method for step debug logging.

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

For GitHub Marketplace publishing, the action must meet Marketplace metadata and naming requirements. Option D is correct because the repository must contain a single action metadata file, action.yml or action.yaml, at the repository root for Marketplace listing. Option B is also correct because the action name must be unique and cannot match a GitHub user or organization unless that owner is publishing the action. Option A is false because Marketplace actions must be in public repositories. Option C is incorrect because a repository is expected to contain one marketplace-listed metadata file at the root, not a collection of marketplace actions. Option E is wrong because the name must not match an existing Marketplace category. GitHub documents these Marketplace prerequisites directly.

GITHUB_RUN_NUMBER is one of the default environment variables automatically created by GitHub for every workflow run. It contains a unique sequential number for each run of a particular workflow in a repository. When referenced from a shell command on a Linux runner, the correct environment-variable syntax is $GITHUB_RUN_NUMBER, making option A correct. GitHub also explains that default environment variables are not members of the env context, so ${{ env.GITHUB_RUN_NUMBER }} is not the appropriate workflow expression. The equivalent GitHub context property is ${{ github.run_number }}, but that exact expression is not one of the answer choices. The vars context is intended for configuration variables explicitly created by users or administrators. Therefore, among the supplied choices, $GITHUB_RUN_NUMBER is the documented valid reference.

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

The key is required because it uniquely identifies the cache. It is used to store and retrieve cached data. When creating or restoring a cache, you need to define a key that will be used to identify the cache.

The path is the file path on the runner that you want to cache. This is where the cached files or dependencies are located and should be specified to tell GitHub where to store or retrieve the cache from.