Question 1

How can GitHub Actions encrypted secrets be used in if: conditionals within a workflow job?

Options :

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

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

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

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.

Answer: C

Question 2

True or false? A secret can be created and made available to all repositories of an organization?

Options :

A : True

B : False

Answer: A

Question 3

What's the recommended approach for implementing a Docker custom action?

Options :

A : You cannot execute a custom action in a Docker container.

B : By providing the instructions in a Dockerfile.

C : By pointing to a prebuilt Docker container.

D : By using a shell command instead.

E : By building the Docker container on-the-fly.

Answer: C

Question 4

How can you enable logging and provide helpful messages from within your custom action's JavaScript code?

Options :

A : Logging is automatically enabled for all custom actions.

B : Use the console.log() function to print messages.

C : Modify the workflow YAML to include log messages.

D : Use the stdout.log() and stderr.log() functions.

Answer: B

Question 5

Where should workflow files be stored to be triggered by events in a repository?

Options :

A : .github/workflows/

B : .github/actions/

C : Nowhere; they must be attached to an act on in the GitHub user interface

D : anywhere

E : workflows/

Answer: A