An enterprise enables an IP allow list. Which two statements correctly describe common interactions with GitHub Apps and automation? (Choose two)
Select all correct answers, then click Submit.
Short Explanation and Infographic
IP allow lists fence who can hit your enterprise/org from the network path. Apps and automation still matter: some app traffic and user-to-server calls interact with allow lists differently, and admins get controls to keep legitimate apps working without opening the world. It is definitely not 'email only' and not 'all apps die forever.'
Full explanation below image
Full Explanation
The correct answers are that user-to-server access can still be subject to IP allow list enforcement depending on the access path, and that administrators configure allow list behavior with GitHub App access in mind. IP allow lists restrict access to enterprise/organization resources from non-allowed IPs for web, API, and Git paths as designed. Option B is false: Apps are not universally hard-disabled with zero configuration options; enterprises plan allow lists and app installation policies together. Option D is false: allow lists are access controls for product access, not merely email filters. Test CI egress IPs, third-party SaaS, and GitHub App architectures before enforcing, and maintain an emergency break-glass process.