최신 GitHub-Actions 무료덤프 - GitHub Actions Certificate

A. A runner needs to have diagnostic logging enabled.

B. A workflow error produces too many, or wrong, requests, impacting external services negatively.

C. A workflow needs to be changed from running on a schedule to a manual trigger

D. A workflow is configured to run on self-hosted runners

E. A workflow sends requests to a service that is down.

A. Download the CLI for the cloud provider and review the associated documentation.

B. Search GitHub Marketplace for verified actions published by the cloud provider.

C. Search GitHub Marketplace for actions created by GitHub.

D. Use the actions/jenkins-plugin action to utilize an existing Jenkins plugin for the cloud provider.

E. Create a custom action to wrap the cloud provider's CLI.

A. Python action

B. Docker container action

C. composite run step

D. JavaScript action

A. to leverage a self-hosted runner

B. to publish to GitHub Packages

C. to create issues in the repo

D. to create a repository secret

E. to add a member to an organization

F. to read from the file system on the runner

A. Use the secrets context within the conditional statement, e.g. ${{ secrets.MySuperSecret }}.

B. Set the encrypted secret as a job-level environment variable and then reference the environment variable within the conditional statement.

C. Create a job dependency that exposes the encrypted secret as a job output, which can then be leveraged in a subsequent dependent job.

D. Use a workflow command to expose the encrypted secret via a step's output parameter and then use the step output in the job's if: conditional.

A. The environment variables can be set in the defaults: sections of the workflow

B. The GITHUB_WORKSPACE environment variable should be used to access files from within the runner.

C. The environment variables can be read in workflows using the ENV: variable_name syntax.

D. The environment variables created should be prefixed with GITHUB_ to ensure they can be accessed in workflows

A. run: echo "::set-env name=MY OUTPUT::foo"

B. run: export MY_OUTPUT=foo

C. run: echo "MY_OUTPUT=foo" >> $GITHUB_OUTPUT

D. run: echo ${{ $GITHUB_OUTPUT=foo }}