An organization is integrating a new scanning solution that checks for software flaws across multiple subnets. Which approach provides the best coverage while balancing resource use and network performance?
Rely on manual checks by administrators whenever major changes occur
Set up a single checking node in one segment to probe internal hosts throughout the environment
Exclude lower priority hosts from scans to conserve resources
Distribute multiple instances across each segment, managed through a central console
Using a distributed approach, where multiple scanning points cover each segment, helps detect flaws throughout the environment and reduces excessive bandwidth usage that could occur with a single scanner. Manual checks after significant changes or skipping certain servers leads to incomplete insight. Having only one scanning node for the entire internal landscape can overload the network as it processes many connections, limiting scalability and coverage.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is a distributed scanning approach better than a single node setup?
Open an interactive chat with Bash
What is a central console, and how does it help in distributed scanning?
Open an interactive chat with Bash
How does skipping low-priority hosts affect vulnerability scanning?