GH-200 · Question #4
You are reaching your organization's storage limit for GitHub artifacts and packages. What should you do to prevent the storage limit from being reached? (Each correct answer presents a complete…
To prevent hitting GitHub artifact and package storage limits, you can manually remove unneeded artifacts or configure automatic retention policies to expire them.
Question
You are reaching your organization’s storage limit for GitHub artifacts and packages. What should you do to prevent the storage limit from being reached? (Each correct answer presents a complete solution. Choose two.)
Options
- AUse self-hosted runners for all workflow runs.
- BDelete artifacts from the repositories manually.
- CConfigure the artifact and log retention period.
- DDisable branch protections in the repository.
- EConfigure the repo to use Git Large File Storage.
Why each option
To prevent hitting GitHub artifact and package storage limits, you can manually remove unneeded artifacts or configure automatic retention policies to expire them.
Self-hosted runners handle compute execution but have no effect on where or how long artifacts and packages are retained in GitHub's storage backend.
Branch protections govern merge rules and code review requirements and have no relationship to artifact or package storage consumption.
Git Large File Storage manages large binary files tracked in source control, not GitHub Actions artifacts or packages, so it does not address Actions storage limits.
Concept tested: Managing GitHub Actions artifact and log retention policies
Source: https://docs.github.com/en/actions/administering-github-actions/managing-artifacts-in-github-actions
Topics
Community Discussion
No community discussion yet for this question.