200-901 Understanding and Using APIs Practice Question
When using the Cisco DNA Center intent API to retrieve issues, the response includes a Link header with rel="next" and a URL. What type of pagination is this?
⚠ Common exam trap
200-901 often tests whether candidates recognize the Link header as cursor-based pagination rather than assuming all pagination uses offset/limit or page parameters — the header form is the giveaway.
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
✓
Cursor-based pagination via Link header
A Link header containing rel="next" with a URL is the standard HTTP mechanism for cursor-based (or token-based) pagination, where the server returns an opaque link to the next page rather than requiring the client to compute offsets. Cisco DNA Center's intent API uses this pattern, returning a Link header with rel="next" and rel="prev" as applicable. The client simply follows the URL until no next link is present.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Offset/limit pagination
Why it's wrong here
Offset/limit pagination passes explicit offset and limit query parameters, letting clients jump to arbitrary positions; DNA Center instead returns an opaque cursor URL in the Link header. Offset/limit would be correct for APIs such as those exposing page numbers via start and count parameters.
- ✓
Cursor-based pagination via Link header
Why this is correct
A Link header carrying rel="next" with an opaque URL is cursor-based pagination: the server dictates the next page location rather than the client computing offsets. This satisfies the scenario's identification of the pagination style used by the DNA Center issues endpoint.
- ✗
Page-based pagination
Why it's wrong here
Page-based pagination uses a page number parameter to request a specific numbered page; the Link header here carries a cursor URL rather than a page index. Page-based schemes suit APIs where clients must jump directly to a chosen page, not follow sequential next links.
- ✗
No pagination
Why it's wrong here
A Link header with rel="next" explicitly supplies a cursor URL for the following page, so pagination is present; claiming none contradicts the header itself. It tempts candidates who assume APIs return everything in one response, which holds only for endpoints that genuinely return a single unpaginated collection.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.