Question 1

How can you define workflow outputs that can be used as inputs in downstream workflows?

Options :

A : Manually pass outputs as environment variables in downstream workflows.

B : Workflow outputs cannot be used as inputs in other workflows.

C : Workflow outputs are automatically available in all workflows.

D : Use the jobs..outputs section to define outputs.

Answer: D

Question 2

Select all characteristics of a job output. (choose two)

Options :

A : You can define only one output per job.

B : An output is a file.

C : An output is a unicode string.

D : An output can be a maximum of 1 MB.

Answer: C,D

Question 3

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 4

Which of the following attributes are mandatory in an action.yml file?

Options :

A : name, description, type

B : name, description, runs

C : name, description, author, branding

D : name, inputs, outputs, runs

Answer: B

Question 5

A workflow contains the following step definition. How do you specify that the artifact can only be stored for 5 days? (choose two)1. - name: 'Upload Artifact'2. uses: actions/upload-artifact@v23. with:4. name: app-binary5. path: app.tar

Options :

A : By selecting Settings > Artifact Deletion for the repository and setting the value 5 in the form.

B : By setting the value 5 for the attribute rentention-days of the upload-artifact action.

C : By configuring the artifact retention settings for the GitHub organization.

D : You cannot configure the days for keeping artifacts. They can only be deleted after a configurable number of executed builds.

Answer: B,C