200-901 Understanding and Using APIs Practice Question
A developer calls a REST API with GET /api/v1/devices?limit=50 and receives the first page of results plus a body field named nextPageToken. The API documentation states that results are cursor-paginated. How should the script request the next page?
⚠ Common exam trap
The trap here is substituting familiar offset or page-number parameters for the opaque cursor token the API actually returns.
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
✓
Call GET /api/v1/devices?limit=50&nextPageToken=<value>.
Cursor pagination relies on an opaque token that marks the position of the last retrieved record. The client echoes that token in the next request, and the server returns the subsequent slice. Loop until the token is missing. Offset, page-number, and oversized-limit approaches do not follow the API's documented contract and can skip or repeat data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Call GET /api/v1/devices?limit=50&page=2.
Why it's wrong here
Page-number pagination assumes the server tracks deterministic page boundaries. This API advertises cursor pagination through nextPageToken, so a page parameter is not part of its contract. The server may ignore the unknown parameter and return the first page again, causing an infinite loop that never advances through the dataset.
- ✗
Call GET /api/v1/devices?limit=100 to fetch everything at once.
Why it's wrong here
Increasing the limit does not implement pagination and often violates the maximum page size the API enforces. The server may cap or reject the larger value, and the client still lacks a defined way to reach records beyond the first page. Ignoring the returned token abandons the documented traversal mechanism.
- ✗
Call GET /api/v1/devices?limit=50&offset=50.
Why it's wrong here
Offset pagination uses a numeric skip value and is a different strategy from cursor pagination. The API here returns an opaque nextPageToken rather than an offset, so inventing an offset parameter is unlikely to be recognized. Even if accepted, offsets can skip or duplicate records when data changes between calls, which cursors are designed to avoid.
- ✓
Call GET /api/v1/devices?limit=50&nextPageToken=<value>.
Why this is correct
Cursor pagination advances by passing the token returned in the previous response. Supplying nextPageToken with its exact opaque value tells the server where the last page ended, so it returns the following set of records. This continues until the token is absent, indicating the final page has been reached.
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.