A city has NSX Manager but never deployed the NSX Intelligence appliance. Analysts open Manager expecting flow recommendations. What should the administrator conclude?
Select an answer to reveal the explanation.
Short Explanation
Intelligence is an extra appliance, not a hidden tab that magically appears on Manager. Until that box exists, there is no Intelligence recommendation engine. vRNI might already be in the rack if the city bought it.
Full Explanation
When a city has NSX Manager but never deployed the NSX Intelligence appliance and analysts open Manager expecting flow recommendations, the administrator should conclude that Intelligence cannot be used until its appliance or service is deployed; vRealize Network Insight may already be present. Intelligence is an add-on capability with its own deployment, not a free hidden tab on every Manager node. Until that appliance exists, there is no Intelligence recommendation engine for civic overlay flows, though vRNI might already cover broader visibility if previously purchased. Intelligence is built into every NSX Manager node and needs no appliance fails by concept because Intelligence requires its dedicated appliance or service deployment beyond base Manager. Disable NSX Manager and use Carbon Black Cloud as the overlay flow engine fails by concept because CBC is endpoint prevention and does not replace NSX Manager or overlay flow recommendation. Workspace ONE Access supplies overlay flow recommendations without Intelligence fails by concept because Access is identity federation and SSO, not NSX overlay flow analytics. Exam caveat: Manager presence alone does not imply Intelligence; verify the Intelligence appliance or service before promising DFW recommendations from Manager. Operational check: inventory whether the Intelligence appliance is deployed and reachable to Managers, if absent either deploy it per design or use existing vRNI for interim visibility, and update the city NSX architecture diagram so SOC expectations match the civic fabric.