200-901 Understanding and Using APIs Practice Question
A developer is integrating with Cisco DNA Center's Intent API. They need to retrieve a list of all network devices and then filter for devices with a specific software version. The API returns a paginated response with a 'nextPage' field in the JSON body. Which approach should the developer use to efficiently process all devices?
⚠ Common exam trap
The trap here is assuming that a high limit parameter can bypass pagination, but the API enforces a maximum page size and requires following the nextPage token.
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
✓
Loop through pages using the 'nextPage' field from the JSON response, making subsequent GET requests to the URL provided in that field until it is null.
Cisco DNA Center's Intent API uses a 'nextPage' field in the JSON response for pagination. The developer should iterate by requesting the URL in 'nextPage' until it is null. This ensures all devices are retrieved. Other methods like ignoring pagination, using offset, or setting a high limit are not supported or reliable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the 'limit' and 'offset' query parameters, incrementing offset by the limit value until fewer results than the limit are returned.
Why it's wrong here
While some APIs support limit/offset, Cisco DNA Center's Intent API uses a 'nextPage' token for pagination. Using offset may not be supported or could lead to inconsistent results. The API documentation specifies the 'nextPage' field, so this approach is not correct.
- ✗
Make a single GET request to /dna/intent/api/v1/network-device and parse all devices from the response, ignoring pagination.
Why it's wrong here
Cisco DNA Center's Intent API paginates responses and may not return all devices in a single call. Ignoring pagination could result in missing devices, especially in large networks. The API typically limits the number of items per page, so this approach is unreliable for comprehensive data retrieval.
- ✓
Loop through pages using the 'nextPage' field from the JSON response, making subsequent GET requests to the URL provided in that field until it is null.
Why this is correct
The Intent API includes a 'nextPage' field in the response when more data is available. By following this field, the developer can retrieve all pages sequentially. This is the documented method for pagination in Cisco DNA Center, ensuring complete data retrieval without guessing parameters.
- ✗
Set the 'limit' query parameter to a very high number (e.g., 10000) to retrieve all devices in one request.
Why it's wrong here
Cisco DNA Center enforces a maximum limit on the number of items returned per request, typically much lower than 10000. Setting a high limit may be ignored or cause an error. The API is designed for pagination, so this method will not return all devices and may fail.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
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.