[2026年01月09日] 最新GH-200試験問題集には高得点で一発合格 [Q34-Q51]

Share

[2026年01月09日] 最新GH-200試験問題集には高得点で一発合格

無料提供中GH-200ブレーン問題集とGH-200リアル試験問題


Microsoft GH-200 認定試験の出題範囲:

トピック出題範囲
トピック 1
  • アクションの作成と保守:このドメインでは、アクション開発者と自動化エンジニアが、JavaScript、Dockerコンテナ、実行ステップなど、適切な種類のGitHub Actionsを選択・作成する能力を評価します。アクションコードのトラブルシューティング、アクションのコンポーネントとファイル構造の理解、そしてアクション内でワークフローコマンドを使用してランナーと通信する能力(終了コードの管理を含む)に重点を置きます。
トピック 2
  • ワークフローの作成と管理:このセクションでは、DevOpsエンジニアと自動化スペシャリストのスキルを評価し、プッシュ、スケジュールされた時間、手動トリガー、Webhookなどのイベントによってトリガーされるワークフローの構築と管理を網羅します。ジョブ、ステップ、アクション、ランナーなどのワークフローコンポーネントの理解、構文の正確性、環境変数、シークレット管理、ジョブ間の依存関係などが含まれます。また、パッケージの公開、サービスコンテナの使用、ジョブのルーティング、クラウドプロバイダーへのリリースのデプロイなど、様々な目的のワークフローを作成するための実践的な能力も証明されます。
トピック 3
  • ワークフローの利用:このドメインはソフトウェア開発者と品質保証エンジニアを対象としており、ワークフローの実行とその結果の解釈に焦点を当てています。トリガーイベントの特定、ワークフロー構成の読み取り、ログ分析による障害のトラブルシューティング、デバッグログの有効化、環境変数の管理、依存関係のキャッシュ、ジョブ間のデータの受け渡しなどを網羅しています。また、ワークフローの実行、成果物、承認、ステータスバッジの管理、リポジトリ内でのワークフローの特定、組織でテンプレート化されたワークフローの活用についても学習します。
トピック 4
  • 企業におけるGitHub Actionsの管理:このセクションでは、企業管理者とプラットフォームエンジニアが組織レベルでGitHub Actionsとワークフローを配布および管理する専門知識を評価します。これには、テンプレートの再利用と共有、リポジトリと命名規則を介した再利用可能なコンポーネントの管理戦略、アクションへのアクセス制御、組織全体の使用ポリシーの設定、そしてGitHub Actionsを企業全体で効率的に展開するためのメンテナンス計画が含まれます。

 

質問 # 34
As a DevOps engineer, you need to execute a deployment to different environments like development and testing based on the labels added to a pull request. The deployment should use the releases branch and trigger only when there is a change in the files under 'apps' folder. Which code block should be used to define the deployment workflow trigger?

  • A. on:
    pull_request:
    types: [labeled]
    branches:
    - 'releases'
    paths:
    - 'apps/**'
  • B. on:
    pull_request:
    types: [labeled]
    branches:
    - 'releases/**'
    paths:
    - 'apps'
  • C. on:
    pull_request_review:
    types: [labeled]
    branches:
    - 'releases'
    paths:
    - 'apps/**'
  • D. on:
    pull_request_label:
    branches:
    - 'releases'
    paths:
    - 'apps/**'

正解:A

解説:
Incorrect:
[Not A] pull_request activitiy type labeled not specified.
pull_request_label is not a trigger.
[Not B] Specifies branches branches that has a name that starts with releases. We are only interested in the release branch.
branches:
- 'releases/**'
[Not C]
pull_request_review
Runs your workflow when a pull request review is submitted, edited, or dismissed. A pull request review is a group of pull request review comments in addition to a body comment and a state.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows


質問 # 35
As a developer, your Actions workflow often reuses the same outputs or downloaded dependencies from one run to another. To cache dependencies for a job, you are using the GitHub cache action. Which input parameters are required for this action? (Choose two.)

  • A. dependency: the name and version of a package to cache or restore
  • B. key: the key created when saving a cache and the key used to search for a cache
  • C. path: the file path on the runner to cache or restore
  • D. cache-hit: the copy action key used with restore parameter to restore the data from the cache
  • E. restore-keys: the copy action key used with cache parameter to cache the data
  • F. ref: the ref name of the branch to access and restore a cache created

正解:B、C

解説:
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.


質問 # 36
As a developer, what options should you recommend to implement standards for automation reuse? (Choose two.)

  • A. Store shared corporate actions in subfolders in a defined and documented internally accessible repository.
  • B. Create reusable actions and workflows that can be called from other workflows.
  • C. Create a marketplace partition to publish reusable automation for the company.
  • D. Create workflow templates and store them in the organization's .github repository.

正解:B、D

解説:
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.


質問 # 37
Which files are required for a Docker container action in addition to the source code? (Each correct answer presents a partial solution. Choose two.)

  • A. Dockerfile
  • B. Actionfile
  • C. action.yml
  • D. metadata.yml

正解:A、C

解説:
Creating a Docker container action
Create a dockerfile
Dockerfile support for GitHub Actions
When creating a Dockerfile for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action's metadata file.
Creating an action metadata file
Create a new action.yml file.
Reference:
https://docs.github.com/en/actions/tutorials/use-containerized-services/create-a-docker-container- action
https://docs.github.com/en/actions/reference/workflows-and-actions/dockerfile-support


質問 # 38
Scheduled workflows run on the:

  • A. latest commit on the default or base branch
  • B. latest commit and branch on which the workflow was triggered,
  • C. latest commit from the branch named schedule,
  • D. latest commit from the branch named main,
  • E. specified commit and branch from the workflow YAML file,

正解:B

解説:
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.


質問 # 39
In which scenarios could the GITHUB_TOKEN be used? (Choose two.)

  • A. to add a member to an organization
  • B. to publish to GitHub Packages
  • C. to leverage a self-hosted runner
  • D. to read from the file system on the runner
  • E. to create issues in the repo
  • F. to create a repository secret

正解:B、E

解説:
The GITHUB_TOKEN is automatically provided by GitHub in workflows and can be used to authenticate API requests to GitHub, including publishing packages to GitHub Packages.
The GITHUB_TOKEN is also used to authenticate API requests for actions like creating issues, commenting, or interacting with pull requests within the same repository.


質問 # 40
Which workflow command would output the debug message "action successfully debugged"?

  • A. echo ":debug:action successfully debugged:"
  • B. echo :debug::message=action successfully debugged"
  • C. echo "debug-action successfully debugged"
  • D. echo "::debug::action successfully debugged"

正解:D

解説:
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.


質問 # 41
In which locations can actions be referenced by workflows? (Choose three.)

  • A. the runs-on: keyword of a workflow file
  • B. an .action extension file in the repository
  • C. a public NPM registry
  • D. a separate public repository
  • E. the repository's Secrets settings page
  • F. the same repository as the workflow
  • G. a published Docker container image on Docker Hub

正解:D、F、G

解説:
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.


質問 # 42
Which of the following scenarios would require the use of self-hosted runners instead of GitHub-hosted runners?

  • A. running more than the three concurrent workflows supported by GitHub-hosted runners
  • B. performing builds on macOS
  • C. using Docker containers as part of the workflow
  • D. exceeding 50,000 monthly minutes of build time
  • E. using specialized hardware configurations required for workflows

正解:A、E

解説:
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.


質問 # 43
Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

  • A. checking out source code with the actions/checkout@v3 action
  • B. assigning non-default permissions to the GITHUB_TOKEN
  • C. making an authenticated GitHub API request
  • D. passing the GITHUB_TOKEN secret to an action that requires a token as an input

正解:C、D

解説:
Some actions may require a GITHUB_TOKEN as an input to authenticate and perform specific tasks, such as creating issues, commenting on pull requests, or interacting with the GitHub API. In such cases, you would need to explicitly pass the token to the action.
When making an authenticated GitHub API request, the GITHUB_TOKEN is required to authenticate the request. This token is automatically provided by GitHub in the workflow, and it must be explicitly used when interacting with the GitHub API.


質問 # 44
Which command can you include in your workflow file to set the output parameter for an action?

  • A. echo "::debug::action_color=purple"
  • B. echo "action_color=purple" >> $GITHUB_OUTPUT
  • C. echo "action_color=purple" >> $GITHUB_ENV
  • D. echo "::add-mask::$ACTI0N_C0L0R"

正解:B

解説:
Setting an output parameter
Sets a step's output parameter. Note that the step will need an id to be defined to later retrieve the output value. You can set multi-line output values with the same technique used in the Multiline strings section to define multi-line environment variables.
echo "{name}={value}" >> "$GITHUB_OUTPUT"
Example of setting an output parameter
This example demonstrates how to set the SELECTED_COLOR output parameter and later retrieve it:
- name: Set color
id: color-selector
run: echo "SELECTED_COLOR=green" >> "$GITHUB_OUTPUT"
- name: Get color
env:
SELECTED_COLOR: ${{ steps.color-selector.outputs.SELECTED_COLOR }}
run: echo "The selected color is $SELECTED_COLOR"
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands


質問 # 45
As a developer, you have configured an IP allow list on a GitHub organization. Which effects does the IP allow list have on GitHub Actions? (Each answer presents a complete solution.
Choose two.)

  • A. You can use GitHub-hosted larger runners since they can be configured with static IP addresses.
  • B. You must allow GitHub Actions's IP address ranges in order to use marketplace actions.
  • C. You can use standard GitHub-hosted runners since their IP addresses are automatically allowed.
  • D. You can use self-hosted runners with known IP addresses.

正解:A、D

解説:
Using GitHub Actions with an IP allow list. If you use an IP allow list and would also like to use GitHub Actions, you must use self-hosted runners or GitHub-hosted larger runners with static IP address ranges To allow your self-hosted or larger hosted runners to communicate with GitHub, add the IP address or IP address range of your runners to the IP allow list that you have configured for your enterprise.
Reference:
https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization- secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for- your-organization


質問 # 46
Which of the following commands will set the $FOO environment variable within a script, so that it may be used in subsequent workflow job steps?

  • A. run: export FOO=bar
  • B. run: echo "::set-env name=FOO::bar"
  • C. run: echo ${{ $FOO=bar }}
  • D. run: echo "FOO=bar" >> $GITHUB_ENV

正解:D

解説:
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.


質問 # 47
Your organization is managing secrets using GitHub encrypted secrets, including a secret named SuperSecret. As a developer, you need to create a version of that secret that contains a different value for use in a workflow that is scoped to a specific repository named MyRepo. How should you store the secret to access your specific version within your workflow?

  • A. Create and access SuperSecret from the secrets store in MyRepo.
  • B. Create a file with the SuperSecret information in the .github/secrets folder in MyRepo.
  • C. Create a duplicate entry for SuperSecret in the encrypted secret store and specify MyRepo as the scope.
  • D. Create MyRepo_SuperSecret in GitHub encrypted secrets to specify the scope to MyRepo.

正解:C


質問 # 48
As a developer, how can you identify a JavaScript action on GitHub?

  • A. The action.yml metadata file references a package.json file.
  • B. The action's repository name includes the keyword "JavaScript."
  • C. The action.yml metadata file has the runs.using value set to node16.
  • D. The action's repository includes a js.yml file in the .github/workflows directory.

正解:A

解説:
Creating a JavaScript action, example
Prerequisites
Before you begin, you'll need to download Node.js and create a public GitHub repository.
* steps omitted *
From your terminal, initialize the directory with npm to generate a package.json file.
npm init -y
Adding actions toolkit packages
The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
When you commit and push your code, your updated repository should look like this:
hello-world-javascript-action/
─ action.yml
─ dist/
─ index.js
─ package.json
─ package-lock.json
─ README.md
─ rollup.config.js
─ src/
─ index.js
Reference:
https://docs.github.com/en/actions/tutorials/create-actions/create-a-javascript-action#creating-an- action-metadata-file


質問 # 49
Scheduled workflows run on the:

  • A. specified commit and branch from the workflow YAML file.
  • B. latest commit on the default or base branch.
  • C. latest commit from the branch named main.
  • D. latest commit from the branch named schedule.
  • E. latest commit and branch on which the workflow was triggered.

正解:B

解説:
Scheduled workflows run on the latest commit on the default branch.
Note: The default branch is also the initial branch that Git checks out locally when someone clones the repository. Unless you specify a different branch, the default branch in a repository is the base branch for new pull requests and code commits.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
https://docs.github.com/articles/about-branches


質問 # 50
How can a workflow deploy mitigate the risk of multiple workflow runs that are deploying to a single cloud environment simultaneously? (Each correct answer presents part of the solution.
Choose two.)

  • A. Specify a concurrency scope in the workflow.
  • B. Configure the mutex setting in the environment.
  • C. Reference the mutex in the task performing the deployment.
  • D. Specify a target environment in the deploymentjob.
  • E. Set the concurrency in the deploymentjob to 1.
  • F. Pass the mutex into the deployment job.

正解:A、D

解説:
[D] GitHub Actions now supports a concurrency key at both the workflow and job level that will ensure that only a single run or job is in progress.
concurrency
Use concurrency to ensure that only a single job or workflow using the same concurrency group will run at a time.
Example: Using concurrency and the default behavior
The default behavior of GitHub Actions is to allow multiple jobs or workflow runs to run concurrently. The concurrency keyword allows you to control the concurrency of workflow runs.
Reference:
https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency/
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#concurrency
https://github.com/marketplace/actions/actions-mutex


質問 # 51
......

GH-200合格させる問題集でMicrosoft24時間で試験合格できます:https://jp.fast2test.com/GH-200-premium-file.html

Microsoft GH-200実際の問題とブレーン問題集:https://drive.google.com/open?id=1AiI4dlNVxp6ToK_hO5D-TKbipr6QGbke


弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

我々の働いている時間: ( GMT 0:00-15:00 )
月曜日から土曜日まで

サポート: 現在連絡 

English Deutsch 繁体中文 한국어