Question 1

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 2

A specific self-hosted runner seems to have issues with executing jobs. How do you enable debug logging for the runner?

Options :

A : Enable debug logging through the UI under Settings > Actions > Runners.

B : You need to open a shell to the runner and inspect the logs in the file system. They should already contain the relevant information.

C : Add the environment variable ACTIONS_DEBUG: true for the job in the workflow file.

D : Set the secret ACTIONS_RUNNER_DEBUG: true for the repository containing the workflow.

Answer: D

Question 3

What's the default label automatically assigned to all self-hosted runners?

Options :

A : managed

B : enterprise

C : github-enterprise

D : self-hosted

Answer: D

Question 4

How can you enforce the use of specific runners and prevent the use of public runners for GitHub Actions in your enterprise?

Options :

A : GitHub Actions only supports public runners; custom runners are not allowed.

B : Modify the repository settings to disable the use of public runners.

C : Use GitHub Enterprise Server to restrict runner usage to custom runners.

D : Create firewall rules to block access to public runner IP addresses.

Answer: C

Question 5

Upon inspection of a workflow, you notice that multiple steps set the bash shell. How can you unify the shell definition across multiple steps without having to redefine it per step individually?

Options :

A : There-s no way to define a common shell as part of a workflow.

B : You should run the command inside of a container if you need a specific shell.

C : Define the common shell with the defaults attribute.

D : The shell is always determined by the selected runner.

Answer: C