Microsoft GH-200 問題集

質問 1：
As a developer, what two options should you recommend to implement standards for automation reuse? Each correct answer presents a complete solution. NOTE: Each correct answer is worth one point.
A. Create a marketplace partition to publish reusable automation for the company.
B. Create workflow templates and store them in the organization's .github repository.
C. Store shared corporate actions in subfolders in a defined and documented internally accessible repository.
D. Create reusable actions and workflows that can be called from other workflows.
正解：C,D
解説: (Topexam メンバーにのみ表示されます)

質問 2：
Which scopes are available to define custom environment variables within a workflow file?
(Choose three.)
A. the entire workflow, by using env at the top level of the workflow file
B. the contents of a job within a workflow, by using jobs.env
C. all jobs being run on a single Actions runner, by using runner.env at the top of the workflow file
D. within the run attribute of a job step
E. the entire stage, by using env at the top of the defined build stage
F. a specific step within a job, by using jobs..steps[*].env
正解：A,B,F
解説: (Topexam メンバーにのみ表示されます)

質問 3：
As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Each correct answer presents a complete solution. Choose two.)
A. Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
B. Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
C. Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
D. Store the token as a GitHub encrypted secret in the same repo as the code. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
E. Store the token as a GitHub encrypted secret in the same repo as the code. Create a reusable custom GitHub Action to access the token by the microservice at runtime.
正解：B,C
解説: (Topexam メンバーにのみ表示されます)

質問 4：
By default, which workflows can use an action stored in internal repository? (Each answer presents a complete solution. Choose two.)
A. internal repositories owned by the same organization as the enterprise
B. selected public repositories outside of the enterprise
C. public repositories owned by the same organization as the enterprise
D. private repositories owned by an organization of the enterprise
正解：A,D
解説: (Topexam メンバーにのみ表示されます)

質問 5：
What is the proper syntax to reference the system-provided run number variable?
A. ${{var.GITHUB_RUN_NUMBER}}
B. $github.run_number
C. $GITHUB_RUN_NUMBER
D. ${{GITHUB_RUN_NUMBER}}
E. ${{env.GITHUB_RUN_NUMBER}}
正解：D
解説: (Topexam メンバーにのみ表示されます)

質問 6：
In GitHub Actions, which workflow key defines the events that trigger the workflow such as push or pull_request?
A. if:
B. env:
C. on:
D. jobs:
正解：C
解説: (Topexam メンバーにのみ表示されます)

質問 7：
In GitHub Actions, where should you declare custom environment variables so they are accessible across all jobs and steps in a single workflow run?
A. Environment secrets
B. Runner command line arguments
C. Repository variables
D. Set env in the workflow YAML
正解：D
解説: (Topexam メンバーにのみ表示されます)