Interpret Workflow Behavior and Results GH-200 Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A workflow file has a job that uses a YAML merge key to combine two anchors: `base: &base` with `runs-on: ubuntu-latest` and `steps: [checkout]`, and `extra: &extra` with `runs-on: windows-latest`. The job uses `<<: [*base, *extra]`. What is the effective `runs-on` value for the job?

   • AThe job fails because of conflicting values.
   • BBoth values are used, and the job runs on both operating systems.
   • Cwindows-latest
   • Dubuntu-latest
   Reveal Solution Discussion Select an answer first
2. 12expert · medium

   A workflow run failed, and the developer is looking at the logs. The `Build` job shows a step `Run tests` that failed, but the error message is truncated. The developer needs to see the full error message. What is the best way to get the full error?

   • ARe-run the workflow and watch the step in real-time.
   • BLook at the workflow file to see what command the step runs.
   • CCheck the job summary to see if the error is listed there.
   • DDownload the raw logs for the failed step from the Actions UI.
   Reveal Solution Discussion Select an answer first
4. 13application · easy

   A workflow run failed, and the developer is looking at the run logs. They see multiple jobs listed, but they are not sure which job failed. What is the quickest way to identify the failing job?

   • ALook for the job with a red X icon in the job list.
   • BCheck the workflow file to see which job has the most steps.
   • CLook at the run summary page to see the overall status.
   • DOpen each job's logs and look for the word 'error'.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   A workflow run failed. In the run summary, the developer sees that the job `build` failed at step `Run tests`. What is the most direct way to find the root cause of the failure?

   • ARe-run the entire workflow to see if it fails again
   • BCheck the repository settings for workflow permissions
   • CLook at the workflow file to verify the trigger configuration
   • DOpen the `build` job log and scroll to the `Run tests` step to read the error output
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A developer pushes a commit to the `main` branch of a repository. The workflow file contains `on: push: branches: [main]` and also `on: schedule: - cron: '0 2 * * *'`. The developer checks the Actions tab and sees a workflow run that started at 2:00 AM, but no run for the push they just made. What is the most likely reason for this behavior?

   • AThe push was made to a branch that matches the `branches` filter, but the workflow run was delayed and the 2:00 AM run is the delayed push run.
   • BThe push trigger requires a `paths` filter to work, and since none is specified, the trigger is disabled.
   • CThe schedule trigger overrides the push trigger, so only scheduled runs are created and pushes are ignored.
   • DThe push was to a branch that does not match the `branches` filter, so the push trigger did not fire, and the 2:00 AM run is from the schedule trigger.
   Reveal Solution Discussion Select an answer first