200-901 Cisco Platforms and Development Practice Question

Using the Cisco DNA Center API, which endpoint should be queried to retrieve the Layer 2 topology for a specific VLAN?

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/topology/l2/{vlanID}

Cisco DNA Center provides /dna/intent/api/v1/topology/l2/{vlanID} to retrieve Layer 2 topology information for a given VLAN.

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/issues
Why it's wrong here
The issues endpoint returns detected network problems and their details, not topology relationships. It is tempting because issues can reference affected devices and VLANs, but retrieving Layer 2 topology for a VLAN requires the topology endpoint with a layer2 topology type filter, not the issues API.
✓
GET /dna/intent/api/v1/topology/l2/{vlanID}
Why this is correct
The DNA Center intent API exposes Layer 2 topology through the topology/l2 path, and appending the VLAN identifier scopes results to that broadcast domain. Querying this endpoint with GET returns nodes and links for the specified VLAN, matching the requirement.
✗
GET /dna/intent/api/v1/network-device
Why it's wrong here
This returns the device inventory (hostname, management IP, software version), not topology links. It is tempting because network-device is the natural starting point for discovering fabric nodes, and it is correct when you need to enumerate devices before querying their interfaces or physical links.
✗
GET /dna/intent/api/v1/topology/physical-topology
Why it's wrong here
The physical-topology endpoint returns device and link relationships at Layer 1 and Layer 3, not VLAN-specific Layer 2 forwarding paths. It is tempting because it is the topology API, but retrieving Layer 2 topology for a specific VLAN requires the topology endpoint queried with layer2 topology type and VLAN number.

Visual reference

Go deeper