GH-200 · Question #29
As a developer, you have configured an IP allow list on a GitHub organization. Which effects does the IP allow list have on GitHub Actions? (Each answer presents a complete solution. Choose two.)
The correct answer is B. You can use self-hosted runners with known IP addresses. D. You can use GitHub-hosted larger runners since they can be configured with static IP addresses. When an IP allow list is configured on a GitHub organization, only traffic from explicitly listed IP addresses is permitted. Standard GitHub-hosted runners use dynamic, unpredictable IP addresses that cannot be pre-listed, so option A is incorrect. Self-hosted runners run on…
Question
As a developer, you have configured an IP allow list on a GitHub organization. Which effects does the IP allow list have on GitHub Actions? (Each answer presents a complete solution. Choose two.)
Options
- AYou can use standard GitHub-hosted runners since their IP addresses are automatically allowed.
- BYou can use self-hosted runners with known IP addresses.
- CYou must allow GitHub Actions's IP address ranges in order to use marketplace actions.
- DYou can use GitHub-hosted larger runners since they can be configured with static IP addresses.
How the community answered
(43 responses)- A19% (8)
- B74% (32)
- C7% (3)
Explanation
When an IP allow list is configured on a GitHub organization, only traffic from explicitly listed IP addresses is permitted. Standard GitHub-hosted runners use dynamic, unpredictable IP addresses that cannot be pre-listed, so option A is incorrect. Self-hosted runners run on your own infrastructure with known, static IPs that you can add to the allow list (option B, correct). GitHub-hosted larger runners support static IP address assignment, allowing those IPs to be added to the allow list (option D, correct). Option C is incorrect because marketplace action downloads don't require org-level IP allow list exceptions.
Topics
Community Discussion
No community discussion yet for this question.