This object sets the maximum number of prefixes the consistency checker will examine during a single scan cycle. Because the object's own description notes a Management Station cannot set this to 0, an admin tuning it balances scan thoroughness against CPU load, where a low count does quick lightweight passes and a high count checks more of the table per cycle at greater processing cost. On a router with millions of FIB entries, an admin might lower this to limit each passive-checker pass to, say, 10,000 prefixes so consistency checking doesn't compete heavily with forwarding for CPU cycles.