How can an enterprise limit which repositories may use expensive larger runners?
Select an answer to reveal the explanation.
Short Explanation
Runner groups are the ACL for shared runners — especially the pricey larger ones. Put big iron in a locked group, allow only payment-approved repos, and keep open-source forks off that hardware. Branch renames and maintenance mode are not your cost control.
Full Explanation
The correct answer is restricting runner groups to selected organizations/repositories. This is the standard enterprise control for self-hosted and larger hosted runners. Option B is nonsense. Option C is nonsense. Option D confuses GHES maintenance with cloud runner governance. Combine group restrictions with workflow permissions that require explicit runs-on labels so random workflows cannot select privileged runners.