A junior civic operator needs the NSX REST API reference hosted on the appliance, not to write production REST. Where is that documentation or explorer?
Select an answer to reveal the explanation.
Short Explanation
The NSX API guidebook lives on the NSX Manager itself. Use the help link or appliance URL, not vSphere’s API explorer, Carbon Black Live Query, or the exam vendor’s tutorial.
Full Explanation
A junior civic operator who needs the on-appliance NSX REST API reference should open the NSX Manager API documentation or explorer from Manager help or the appliance URL—that is the hosted Policy/Manager REST catalog for municipal fabric work without writing production automation. Using the vSphere Automation API explorer is incorrect by product scope: that explorer documents compute and vCenter objects, not NSX Policy or Manager APIs. Running Carbon Black Live Query and treating sensor SQL as the NSX API confuses endpoint telemetry with the NSX management-plane interface. Opening the Pearson VUE exam tutorial as an API catalog confuses certification UI training with the live appliance reference. Exam caveat: VCTA-NV asks operators to identify where documentation lives; it does not require authoring REST clients or memorizing every URI. Operational check: from NSX Manager help or the documented appliance API path, open the explorer, locate a familiar Policy object (for example a segment), confirm the response schema matches what the civic team uses in runbooks, and bookmark that URL for junior staff. In municipal operations, record the chosen control and the rejected alternatives in the change ticket so future on-call staff understand which failure modes would affect city services. Re-validate after the next maintenance window that the same GUI path and realized state still hold under the current NSX build used by the civic platform team.