Which Cisco DNA Center Intent path retrieves overall client health including wireless for a municipal assurance script?
Select an answer to reveal the explanation.
Short Explanation
Wireless client health for this task lives on Intent client-health—like checking the city’s rider wellness board, not the subway map or a Meraki guest list.
Full Explanation
Overall client health including wireless for a municipal assurance script is retrieved with GET /dna/intent/api/v1/client-health on Cisco DNA Center. That Intent path returns the scoreDetail structure scripts walk for wired/wireless categories and is the documented retrieve for this DEVCOR wireless-health story.
Using site-health as a full substitute fails because site-health answers a different assurance question; it is not the client-health payload with wireless scoreDetail the task focuses on. Scraping fabric-interconnect CLI show ap summary over SSH fails by platform and method: FI CLI AP lists are not DNA Center Intent client-health. Relabeling Meraki /networks/{id}/clients as DNA wireless health fails by product confusion—Meraki client lists are not DNA Center assurance scores.
Exam caveat: URL prefixes and Intent versions matter; a wrong base path can 404 while credentials are fine—confirm /dna/intent/api/v1/client-health against the controller the city actually runs.
Operational check: after auth, GET client-health, assert HTTP 200 and presence of scoreDetail entries, and verify a wireless category exists before the dashboard claims “wireless health retrieved” for the municipal NOC.