A colleague says Catalyst Center replaced Cisco DNA Center and all health API paths changed. What is the accurate DEVCOR stance?
Select an answer to reveal the explanation.
Short Explanation
Same city hall, new sign out front—Catalyst Center is the DNA Center rename. The Intent /dna/ health retrieve you already learned still applies.
Full Explanation
Catalyst Center is the same controller after Cisco’s rename of DNA Center; Intent /dna/… health retrieve paths remain the documented constructed answer for wireless client health. DEVCOR does not require discarding DNA Center wording or inventing a wholly new health API family solely because marketing signs changed on the appliance.
Insisting candidates must pick Catalyst Center as a different product and discard DNA Center wording fails the continuity stance: rename ≠ new API contract for this task. Claiming all Intent paths moved under /catalyst/ only so /dna/client-health is obsolete fails against the documented Intent health retrieve still taught for this objective. Requiring an ENAUTO feature-catalog survey instead of Intent GET fails by swapping in an unrelated exam track’s activity for assurance retrieve.
Exam caveat: lab images and docs may say DNA Center or Catalyst Center interchangeably—judge by Intent path and auth/token behavior, not by which words appear on the login splash.
Operational check: against the city’s controller (whatever the GUI title), POST /dna/system/api/v1/auth/token and GET /dna/intent/api/v1/client-health; if those succeed, treat rename debates as non-blocking for the wireless-health script.