Transit wants nested Active Directory groups as Identity Firewall sources for fare-system VDI. A technician suggests flattening the same groups in Carbon Black Cloud instead. What should the administrator verify?
Select an answer to reveal the explanation.
Short Explanation
Identity Firewall reads the city's AD nesting, not a Carbon Black sensor roster. Confirm NSX syncs those nested groups, then use them as rule sources. Flattening in Carbon Black does not feed DFW user mapping.
Full Explanation
NSX-T Identity Firewall sources are directory groups synchronized from the connected user directory, including nested AD groups when the product supports that nesting and sync. Carbon Black Cloud sensor groups are a different membership model and are not IDFW sources. vSphere tags on Edge nodes and Workspace ONE Access nested groups do not replace the NSX Manager directory connection for user-based firewall.