200-901 Understanding and Using APIs Practice Question
A network engineer is using the Cisco DNA Center API to retrieve a list of all sites. The API returns a large number of records, and the response includes a header indicating the total count and a limit on the number of records per page. Which HTTP response header should the engineer inspect to find the URL for the next page of results?
⚠ Common exam trap
The trap here is assuming that X-Total-Count or Location headers provide pagination links, when actually the Link header is the correct one for navigating pages.
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
✓
Link
The Link header is the standard way to provide pagination links in REST APIs. It includes a URL for the next page, allowing clients to iterate through large result sets. Other headers like X-Total-Count give total counts, Location is for resource creation, and Retry-After is for rate limiting. Only Link directly provides the next page URL.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Link
Why this is correct
The Link header is commonly used in REST APIs for pagination, providing URLs for the next, previous, first, or last pages. In Cisco DNA Center API, when a response is paginated, the Link header contains a URL with rel="next" that the client can follow to retrieve the next set of records. Inspecting this header allows the engineer to navigate through all pages efficiently without constructing URLs manually.
- ✗
Location
Why it's wrong here
The Location header is used in HTTP responses to indicate the URL of a newly created resource (e.g., after a POST) or for redirection. It is not used for pagination. In the context of retrieving a list, the Location header is not present. Therefore, it does not help in finding the next page of results.
- ✗
Retry-After
Why it's wrong here
The Retry-After header is used with 503 Service Unavailable or 429 Too Many Requests responses to indicate how long the client should wait before retrying. It has no relation to pagination. Inspecting it would not provide a URL for the next page; it only advises on retry timing after a temporary failure.
- ✗
X-Total-Count
Why it's wrong here
The X-Total-Count header typically provides the total number of records available, which is useful for understanding the dataset size but does not give the URL for the next page. It is an informational header, not a navigational one. Relying on it alone would not allow the engineer to fetch subsequent pages; they would still need to construct the next request manually.
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.