What can repository or organization administrators configure regarding Actions artifacts?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Artifacts pile up and cost storage. Set retention so yesterday's 2GB build logs do not live forever unless compliance says so. You still get artifacts when you upload them; admins just control how long they stick around and who can access them under normal repo permissions.
Full explanation below image
Full Explanation
The correct answer is configuring retention periods so artifacts expire. This controls storage growth and reduces lingering sensitive build outputs. Option B is false. Option C is insecure and incorrect as a default goal. Option D is false. Align retention with compliance needs, purge sensitive artifacts sooner, and prefer attestations/packages for release artifacts that must persist.