Manage Workflow Execution and Outputs GH-200 Practice Questions (Page 3)

Questions 11–15

1. 11expert · medium

   An organization has a repository with a workflow that uploads build artifacts. The compliance team requires that artifacts be retained for exactly 90 days, but the current repository setting is 30 days. The workflow is triggered by both pushes and scheduled runs. What is the most reliable way to enforce the 90-day retention for all artifacts?

   • AUse the `actions/upload-artifact` action's `retention-days` input set to 90.
   • BCreate a scheduled workflow that re-uploads all artifacts with a 90-day retention.
   • CSet the repository's artifact retention period to 90 days in Settings.
   • DAdd a step in the workflow that calls the REST API to update the retention period for each artifact after upload.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A workflow uploads a test report artifact and also generates a job summary. The team wants the artifact to be available for 14 days, but the repository default is 30 days. What is the correct way to set the artifact retention to 14 days?

   • AChange the repository's artifact retention setting to 14 days.
   • BUse the REST API to update the artifact's retention after upload.
   • CWrite the retention period to `GITHUB_ENV` and reference it in the upload step.
   • DSet the `retention-days` input on the `actions/upload-artifact` step to 14.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which REST API endpoint can be used to set the retention period for a specific artifact in a repository?

   • APUT /repos/{owner}/{repo}/actions/artifacts/{artifact_id}
   • BPOST /repos/{owner}/{repo}/actions/artifacts/{artifact_id}/retention
   • CDELETE /repos/{owner}/{repo}/actions/artifacts/{artifact_id}
   • DPATCH /repos/{owner}/{repo}/actions/artifacts/{artifact_id}
   Reveal Solution Discussion Select an answer first
5. 14expert · medium

   A workflow has a `build` job that produces a large binary artifact and a `deploy` job that needs both the binary and a small configuration value (the target environment name). The team wants to minimize complexity and avoid re-downloading the artifact if the config value changes. What is the best approach?

   • AEmbed the environment name in the artifact and have the deploy job extract it.
   • BUse a reusable workflow that returns the environment name as an output and also uploads the artifact.
   • CPass the environment name via a job output and upload the binary as an artifact.
   • DWrite the environment name to `GITHUB_ENV` in the build job and use it directly in the deploy job.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A test workflow runs on every push and produces a JUnit XML report. The team wants the workflow run page to show a formatted summary of test counts (passed, failed, skipped) with a link to the uploaded report artifact. What is the most efficient way to achieve this?

   • AUse a step that parses the JUnit XML and appends a Markdown table to `GITHUB_STEP_SUMMARY`, then upload the XML as an artifact.
   • BUpload the JUnit XML as an artifact and rely on the artifact page to show the summary.
   • CCommit the JUnit XML to the repository and link to it from the README.
   • DWrite the test counts to `GITHUB_OUTPUT` and display them in the job log.
   Reveal Solution Discussion Select an answer first