What is the effect of --min-rate and --max-rate on scan throughput, and why would you adjust them?

• A. They only affect output formatting.
• B. They set timing templates.
• C. They limit the number of hosts in a session.
• D. They constrain the probe rate; --min-rate enforces minimum packets/second, --max-rate caps the rate; adjust to balance speed, reliability, and stealth.

Answer: (D)

The main idea here is how you control scan throughput by limiting how fast probes are sent. The switches --min-rate and --max-rate actually bound the probe rate during a scan. The minimum rate sets a floor, ensuring Nmap keeps sending probes at or above a certain packets-per-second level, which can help keep progress steady in noisy or slow networks. The maximum rate sets a ceiling, preventing the scan from overwhelming the network, flooding targets, or triggering defensive systems, which improves reliability and stealth.

Because of that balance, you adjust them to trade speed for reliability and stealth. In a controlled, fast network you might push the max rate higher to finish quickly; in congested networks or when you want to be gentler on the target or less conspicuous, you lower the max rate. The min rate is useful to avoid scans that stall or become unreasonably slow in environments that drop or delay packets.

These options don’t affect how output is formatted, they don’t set timing templates, and they don’t limit how many hosts are included in a session. They are all about controlling how aggressively probes are sent to achieve a usable balance of speed, reliability, and stealth.