Which technique is explicitly suggested to speed up large scans?

• A. Move machines closer to the target network
• B. Use a tool like SCANRAND that separates the Send and Receive mechanisms
• C. Increase the per-packet timeout to speed up results
• D. Use a single-tool approach to avoid coordination

Answer: (B)

When scanning large ranges, the bottleneck often isn’t the probes themselves but how responses are handled. Separating the Send and Receive tasks lets probes be dispatched more aggressively while responses are processed independently, increasing overall throughput. A tool that explicitly splits these mechanisms can keep sending at a higher rate without being held up by response processing, and can distribute work across dedicated components to avoid resource contention. This is why using a tool like SCANRAND that decouples sending from receiving is the best approach for speeding up large scans.

Other options don’t fit as well because: physically moving machines closer doesn’t reliably boost large-scan throughput and isn’t practical in many setups; increasing the per-packet timeout slows progress by making the scanner wait longer for responses; and relying on a single tool to avoid coordination creates a single bottleneck rather than alleviating it.