Cisco DNA Spaces Connector Location Services Requirements
An engineer must enable location services using Cisco DNA Space through a DNA Space Connector on a client located in the US. Which two requirements are mandatory for a successful implementation? (Choose two.)
Community Votes
67% of anonymous learners picked answer AB. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests mandatory integration protocols (NMSP/SNMP) and cloud connectivity requirements for Cisco DNA Space Connector deployment.
Enabling location services via Cisco DNA Space requires the connector to communicate with wireless controllers using NMSP and SNMP, and to access the cloud platform for data processing.
Candidates often select CAPWAP or API access as mandatory, confusing general management access with specific location service signaling requirements.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The Cisco DNA Space Connector is a virtual appliance that bridges on-premises infrastructure with the cloud-based Cisco DNA Spaces analytics engine. For location services to function, the connector must collect radio frequency (RF) data from Wireless LAN Controllers (WLCs). This collection relies on two specific protocols: the Network Mobility Service Protocol (NMSP) over TCP port 16113 and Simple Network Management Protocol (SNMP) over UDP ports 161/162. These are the definitive technical mechanisms for pulling probe request and beacon data required for positioning. Additionally, because DNA Spaces is a SaaS solution hosted in the cloud, the connector must have outbound internet connectivity to reach the official Cisco endpoint at https://connector.dnaspaces.io to register, authenticate, and upload processed data.Why the Other Options Are Wrong
Option E suggests using CAPWAP ports 5246 and 5247; however, the connector does not join the WLC as an AP or controller via CAPWAP. It acts as a client/sensor collector using NMSP/SNMP. Option D mentions the WLC API; while REST APIs are used for configuration and monitoring in many scenarios, the real-time RF data feed for location services specifically mandates NMSP/SNMP, making 'API accessible' insufficient or secondary compared to the strict protocol requirement. Option C refers to 'CMX Connector,' which is a legacy component from the era before Cisco acquired Meraki and rebranded CMX into DNA Spaces; modern DNA Spaces deployments do not require enabling a separate CMX Connector feature on the WLC.Community Comment Notes
Community consensus strongly favors the combination of NMSP/SNMP communication and Cloud Connectivity. As user rrahim noted, the integration relies on "NMSP & SNMP Communication Between DNA Spaces Connector and WLC" alongside cloud reachability. Another user confirmed that "Both SNMP & NMSP are required," reinforcing that these protocols are non-negotiable for the data pipeline.Official Reference
Exam Strategy
When dealing with Cisco DNA Spaces or CMX integrations, always prioritize the specific data collection protocols (NMSP/SNMP) over generic network access methods like CAPWAP or API unless explicitly stated otherwise. Remember that cloud-based analytics platforms inherently require outbound HTTPS connectivity to their respective endpoints.
Frequently Asked Questions
Why is CAPWAP not used for DNA Spaces Connector?
CAPWAP is for AP-controller control/data planes. DNA Spaces uses NMSP/SNMP to pull RF data without joining the WLAN infrastructure.
Is the WLC API required for location services?
No. While APIs are useful for management, the real-time location data feed strictly depends on NMSP and SNMP protocols.