hardMultiple Choice
200-901 Practice Question: Uses Cisco DNA Center and wants to use its Intent…
An organization uses Cisco DNA Center and wants to use its Intent API to retrieve the health score of all wireless clients. Which API endpoint and method should be used?
⚠ Common exam trap
Cisco often tests the distinction between Intent API endpoints and the correct HTTP verb for read operations, trapping candidates who confuse the client-health endpoint with the client-detail endpoint or who incorrectly assume that POST or PUT can be used for data retrieval.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
GET /dna/intent/api/v1/client-health
The Intent API for retrieving client health scores uses the GET HTTP method on the `/dna/intent/api/v1/client-health` endpoint. This endpoint returns the aggregated health data for all wireless clients, aligning with the read-only nature of the operation and the Intent API's resource-oriented design.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
PUT /dna/intent/api/v1/client-health
Why it's wrong here
PUT is a write method; the Intent API exposes client health as a read-only resource, so PUT against client-health is rejected. It is tempting because the path itself is the correct client-health endpoint, and PUT is used elsewhere in DNA Center for updates, but retrieving a health score requires GET.
- ✗
GET /api/v1/health
Why it's wrong here
The path omits the required /dna/intent/api prefix and the client-health resource, so it does not resolve to the DNA Center Intent API. It is tempting because a short health endpoint looks plausible, but the correct call is GET /dna/intent/api/v1/client-health with query filters.
- ✓
GET /dna/intent/api/v1/client-health
Why this is correct
The client-health endpoint aggregates health scores across wired and wireless clients, and GET retrieves them without modifying state. Cisco DNA Center's Intent API exposes this at /dna/intent/api/v1/client-health, satisfying the requirement to obtain wireless client health scores.
- ✗
POST /dna/intent/api/v1/client-detail
Why it's wrong here
POST to client-detail returns per-client detail rather than an aggregate health score, and POST is not the retrieval method for client health. It is tempting because client-detail sounds health-related, but the health score comes from GET /dna/intent/api/v1/client-health, not a detail lookup.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.