An administrator at Meridian Electric Cooperative needs a static URL filter entry that matches an entire family of subdomains used by one vendor, not just a single exact address. What capability of the static URL filter list makes this possible?
Select an answer to reveal the explanation.
Short Explanation
You're not stuck typing one exact address per entry. The static URL filter list also accepts wildcard or pattern-based matches, so a single entry can sweep in a whole family of related subdomains instead of listing each one by hand.
Full Explanation
Static URL filter entries support more than a single literal string match — the administrator can configure an entry using a wildcard or regular expression pattern instead of an exact address, which lets one entry cover a range of related URLs, such as every subdomain under a vendor's primary domain. That flexibility is what makes the list practical for real vendor infrastructure, which often spans several subdomains rather than a single fixed address. The claim that only exact matching is available understates the feature and would force an administrator into an unmanageable number of individual entries for a single vendor. Automatic subdomain matching for every listed domain is also incorrect — pattern matching in this list is a deliberate configuration choice per entry, not an implicit default applied everywhere. Application control isn't the right comparison at all here, since it identifies applications by signature rather than matching URL strings, so it doesn't provide this kind of address-pattern coverage. A caveat: overly broad wildcard or regex patterns can unintentionally match unrelated sites, so patterns should be tested against real traffic before being trusted in production. Confirm a pattern entry is matching only the intended addresses by reviewing web filter log hits against that entry over a representative period.