A penetration tester is using Nessus to scan a large subnet and needs to avoid overwhelming older printers that are known to crash when too many simultaneous connections are made. The tester also wants to ensure the scan completes in a reasonable timeframe. Which Nessus scan policy setting should be adjusted to control the number of simultaneous hosts being scanned?
Max concurrent hosts determines how many hosts are scanned at the same time. By reducing this value, the tester limits the number of devices being probed simultaneously, which directly lowers the risk of overwhelming fragile printers. It also helps manage overall network load while still allowing the scan to proceed efficiently.
Why this answer
The Max concurrent hosts setting directly controls how many hosts are scanned at the same time. Lowering this value ensures that fewer devices are probed concurrently, reducing the chance of crashing sensitive equipment like older printers. It balances scan speed with safety, making it the appropriate adjustment for the scenario.
Exam trap
The trap here is confusing per-host concurrency limits with global host concurrency, leading to a setting that doesn't actually reduce the number of simultaneous targets.