Which two statements correctly contrast GitHub-hosted and self-hosted runners? (Choose two.)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Hosted runners are managed and ephemeral; self-hosted reach private nets but shift security and ops burden to you—including fork PR risk.
Full explanation below image
Full Explanation
GitHub-hosted runners trade control for convenience: standard images, auto updates, per-job VMs. Self-hosted runners suit private package feeds, hardware devices, or fixed IPs, but you own OS patching, secret exposure risk, and capacity. They can run dangerous workflows if repository settings allow—there is no magical immunity to fork PR abuse. There is no runs-on san: mount feature for datacenter SANs on hosted runners. Prefer ephemeral self-hosted (autoscaled) patterns when possible to reduce persistence attacks.