VMware 6V0-21.25 - VMware vDefend Security for VCF 5.x Administrator

When configuring Layer 7 Context Profiles for FQDN filtering, it is critical to understand the syntax limitations to avoid configuration errors. vDefend FQDN filtering supports exact full domain names (Option A) and complete wildcard masks (Option C, such as *.vmware.com). It also supports leading string wildcards (like *eng.vmware.com).

However, it does NOT support advanced or "partial regular expressions" (Regex) natively within the basic FQDN attribute matching engine (e.g., you cannot use regex string limiters, character classes like [a-z], or complex partial regex logic at the beginning of the string). Therefore, the statement that it "supports partial regex at the beginning of the FQDN" is the false statement.

=========================

When creating Security Groups in vDefend, dynamic criteria (like VM Names, OS Names, or Security Tags—Options B, C, and D) are heavily preferred for internal workloads because vCenter and NSX have direct administrative control and visibility over those virtual machines.

However, External DNS servers reside outside of the vSphere/NSX compute boundary (they are often physical servers or managed by a separate network team). Because vDefend cannot assign a vSphere metadata tag or read the VM Name of an external physical server, dynamic grouping will fail. Therefore, the only technically viable and recommended method for grouping external infrastructure is to build an IP Set or Security Group and statically assign the IP addresses of those external resources.