200-901 Cisco Platforms and Development Practice Question

In DNA Center, which API endpoint is used to retrieve a list of current network issues?

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/issues

DNA Center's issues API is at /dna/intent/api/v1/issues.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✗
GET /dna/intent/api/v1/topology
Why it's wrong here
The topology endpoint returns physical and logical link relationships between devices, not a list of current network issues. It is tempting because topology data can hint at connectivity problems, but it describes network structure; issue retrieval requires the dedicated issues endpoint under /dna/intent/api/v1.
✗
POST /dna/system/api/v1/auth/token
Why it's wrong here
This endpoint issues an authentication token for subsequent API calls; it returns credentials, not issue data. It is tempting because every DNA Center API workflow begins with token retrieval, but that is authentication setup, whereas the issues endpoint under /dna/intent/api/v1 is queried for network problems.
✓
GET /dna/intent/api/v1/issues
Why this is correct
The /dna/intent/api/v1/issues endpoint is the Intent API resource dedicated to network issue retrieval, returning the current list of issues detected by DNA Center's assurance engine. It satisfies the stem's requirement for a list of current network issues rather than device or health data.
✗
GET /dna/intent/api/v1/network-device
Why it's wrong here
The network-device endpoint lists managed devices and their attributes, not active issues. It is tempting because device inventory is often checked when troubleshooting, but it returns device records; current issues come from the issues endpoint under /dna/intent/api/v1, which aggregates health and assurance data.

Go deeper