After opening a specific workflow run in the GitHub UI, how do you view the logs for an individual job?

Navigate to the 'Security' tab of the repository

Click the job name in the run summary

Use the 'Raw' button on the workflow file

Download the entire repository as a ZIP

A developer is writing a script to automate the collection of logs from the latest failed run of a specific workflow. They want to use the GitHub REST API. What is the correct sequence of API calls to achieve this?

1. List runs for the workflow, 2. Find the latest failed run, 3. Download the logs for that run.

1. List all runs in the repository, 2. Download the logs for the first run in the list.

1. Download the logs for the workflow, 2. Find the failed run in the log file.

1. Get the workflow's jobs, 2. Find the failed job, 3. Download the logs for that job.

Which of the following is a valid way to manage the lifecycle of a workflow artifact?

Move an artifact to a different repository

Edit the artifact's contents after upload

Set a custom retention period in the workflow file

Increase the retention period beyond 400 days

A user is looking at the Actions tab and sees a list of workflow runs. They want to find a specific run that was triggered by a `pull_request` event from a fork. The run's status is 'completed' and it has an artifact. How can they most quickly identify this run in the UI?

Look for the run with a 'fork' icon next to it.

Use the 'Event' filter and select 'pull_request'.

Use the 'Branch' filter and select the fork's branch name.

Click on each run to see if it was from a fork.

A workflow run produces an artifact that is needed by a subsequent workflow run. The team wants to ensure the artifact is available for the next run. What is the most reliable way to pass the artifact between runs?

Commit the artifact to the repository and have the next workflow pull it.

Store the artifact in an external storage service and use a custom script to download it.

Re-run the first workflow to regenerate the artifact before the second workflow runs.

Use the `actions/download-artifact` action in the subsequent workflow, specifying the artifact name.

GitHubActions Certification

Domain 2Objective 2

Access Workflow Artifacts and Logs GH-200 Practice Questions (Page 3)

Part of the Consume and troubleshoot workflows domain, which accounts for 15-20% of the GH-200 exam.

20questions here

4free pages

6concepts

15-20%of the exam

Questions 11–15

11foundation · easy
After opening a specific workflow run in the GitHub UI, how do you view the logs for an individual job?
Select an answer first
12expert · hard
A developer is writing a script to automate the collection of logs from the latest failed run of a specific workflow. They want to use the GitHub REST API. What is the correct sequence of API calls to achieve this?
Select an answer first
13foundation · easy
Which of the following is a valid way to manage the lifecycle of a workflow artifact?
Select an answer first
14expert · medium
A user is looking at the Actions tab and sees a list of workflow runs. They want to find a specific run that was triggered by a `pull_request` event from a fork. The run's status is 'completed' and it has an artifact. How can they most quickly identify this run in the UI?
Select an answer first
15application · medium
A workflow run produces an artifact that is needed by a subsequent workflow run. The team wants to ensure the artifact is available for the next run. What is the most reliable way to pass the artifact between runs?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GH-200

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitHub. “GH-200” is a trademark of its owner, used for identification only.