Parks on-premises DNS appliances fail. Workspace ONE Access connector sync, Carbon Black Cloud sensor name resolution, and NSX-T FQDN-based Distributed Firewall all break in the same window. Three product teams want to rebuild their stacks. What should the administrator restore first?
Select an answer to reveal the explanation.
Short Explanation
When DNS dies, every product that lives on names falls over together. That is one broken flashlight, not three separate product failures. Restore the physical resolvers first; do not rebuild Access, CBC, and NSX hoping the names come back.
Full Explanation
Workspace ONE Access, Carbon Black Cloud sensors, and NSX-T FQDN firewall all require working DNS. Failure of shared on-premises DNS appliances therefore presents as simultaneous multi-product outages. Identity firewall, Guest Introspection, and UEM compliance do not replace recursive DNS. Restore the DNS appliances or failover resolvers, verify name resolution from connectors, sensors, and overlay VMs, then recheck each security product.