Free Microsoft GH-100 Actual Exam Questions - Question 4 Discussion
team requires that these runners use IP address ranges that would not be shared with other
companies. Which of the following approaches would meet their requirements?
D imo, static IPs would solve the exclusivity issue, but I don’t think GitHub-hosted runners actually support static IPs yet. So even if it sounds right, it probably won’t work in practice.
Not B, because those IPs are public and shared across many users, so they won’t meet strict security needs for exclusive IP ranges. The others try to limit exposure more.
B seems off since those IPs are shared among many users and can’t guarantee exclusivity. C is similar, just a different set of IPs but still shared and not dedicated. D sounds good in theory but GitHub-hosted runners don’t support static IPs officially, so that’s probably a no-go. A is basically the only real way to get private, exclusive networking on GitHub-hosted runners, even if it might be in preview, it aligns best with the security requirement for unique IP ranges.
A. The key here is isolating the IP addresses so they’re not shared with others. Using Azure private networking with larger GitHub-hosted runners lets you have a private subnet, which means the IPs won’t be from a shared pool like in B or C. D sounds good on paper, but GitHub-hosted runners don’t officially offer static IPs, so you can’t guarantee exclusivity there. A is the only option that fits the security requirement for dedicated IP ranges.
A. Using Azure private networking with larger GitHub-hosted runners isolates the network, so it prevents IP sharing. The others rely on shared IP pools, which the security team won’t accept.
Makes sense to rule out B and C since those IPs are shared across many users, so they wouldn’t meet the security team’s needs. D sounds ideal with static IPs, but I don’t think GitHub-hosted runners actually offer static IPs officially. So A looks like the only solid option where you get private networking, which means isolated IP ranges that aren’t shared with other companies.
The security team wants IP ranges not shared with other companies, but GitHub-hosted runners use shared IP pools. Option A with Azure private networking isolates the runners, so that fits better. That's A.
D. Static IPs make sense here to avoid sharing addresses with others.