Your organization enabled a larger GitHub-hosted runner pool exposed through a runner group. Which runs-on form targets that pool using the group selector (when configured that way)?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Larger hosted runners and organized pools are selected via runs-on group/label configuration your org enables. Not docker:// URLs as runs-on, not secrets-as-labels magic, and permissions never skip runs-on.
Full explanation below image
![Portrait infographic: runs-on group: larger-runners labels: [ubuntu-latest] → powerful VM; cost meter. 1536x2048.](/media/github/gh-200/GH-200-q275-infographic.webp)
Full Explanation
GitHub documents runs-on variants for GitHub-hosted standard labels (ubuntu-latest), self-hosted label arrays, and group-based selection used with larger runners or runner groups. Administrators enable the pool and grant repository access; workflows then target it explicitly. Using a container image URI as runs-on is invalid. Secrets should not be used as a substitute for runs-on structure. OIDC permissions do not choose hardware. Always document which workflows may consume expensive larger runners to control cost, and monitor queue times when pools are capacity-constrained.