GH-200 無料問題集「Microsoft GitHub Actions」

（A）Create workflow templates and store them in the organization's .github 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）Store shared corporate actions in subfolders in a defined and documented internally accessible repository.

（A）Use the YAML powershell: step.

（B）Use the actions/run-powershell action to invoke the script.

（C）Use the YAML shell: pwsh in a run step.

（D）Run the pwsh2bash command to convert the script so it can be run on Linux.

（E）Configure a self-hosted runner on Windows with the requested tools.

（A）echo :debug::message=action successfully debugged"

（B）echo "debug-action successfully debugged"

（C）echo ":debug:action successfully debugged:"

（D）echo "::debug::action successfully debugged"

（A）run: echo "::set-env name=FOO::bar"

（B）run: echo "FOO=bar" >> $GITHUB_ENV

（C）run: echo ${{ $FOO=bar }}

（D）run: export FOO=bar

（A）a published Docker container image on Docker Hub

（B）a public NPM registry

（C）the same repository as the workflow

（D）the repository's Secrets settings page

（E）a separate public repository

（F）the runs-on: keyword of a workflow file

（G）an .action extension file in the repository

（A）granting users repository approval permissions

（B）creating a branch protection rule and only allow certain users access

（C）adding users as required reviewers for an environment

（D）granting users workflow approval permissions

（A）setting a debug message

（B）setting output parameters

（C）reading from environment variables

（D）populating variables in a Dockerfile

（A）The Encrypt Secret setting was not configured for the secret.

（B）The Codespace secret doesn't match the expected value.

（C）There is a different value specified at the enterprise level.

（D）There is a different value specified at the workflow level.

（E）There is a different value specified at the rego level.