200-901 Cisco Platforms and Development Practice Question

A developer wants to retrieve the list of network devices from Cisco DNA Center. Which API endpoint should be used?

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/network-device

The GET /dna/intent/api/v1/network-device endpoint returns a list of network devices managed by DNA Center.

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/site
Why it's wrong here
The site endpoint returns site hierarchy and location data, not device inventory, so the developer would receive no device list. It is tempting because site and device APIs are both under the intent path, and it would be correct when retrieving sites to which devices are assigned.
✗
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 device records. Device lists come from GET /network-device. Token authentication is correct as a prerequisite step before any DNA Center API request, not as the device-retrieval call itself.
✗
GET /dna/intent/api/v1/topology/l2/{vlanID}
Why it's wrong here
The topology/l2 endpoint returns Layer 2 link and VLAN topology data, not a device inventory. Device lists come from /network-device. Topology is correct when visualising how switches interconnect within a VLAN, not when enumerating managed devices.
✓
GET /dna/intent/api/v1/network-device
Why this is correct
GET /dna/intent/api/v1/network-device satisfies the requirement to retrieve the device inventory from Cisco DNA Center. The Intent API exposes network-device as a read-only collection, and issuing GET against it returns all managed devices with their details, matching the developer's need to list network devices.

Go deeper