Security wants one scalable control that stops city-hall workstations and servers from resolving known-malicious domains no matter which browser or app makes the request. Which control best fits?
Select an answer to reveal the explanation.
Short Explanation
DNS filtering sits at the resolver and says "nope" to known-bad names—every city-hall app that looks up a name gets the protection. Memorizing lists or letting anyone use random public DNS throws that scale away.
Full Explanation
DNS filtering inspects or rewrites name-resolution requests at recursive resolvers (or equivalent services) to block domains associated with malware, phishing, or other abuse. Because most applications depend on DNS, it scales across municipal clients without per-app configuration. Uncontrolled public resolvers, purely manual lists, or disabling DNS are not practical enterprise controls.