200-901 Understanding and Using APIs Practice Question
A developer is building a Python script that calls the Cisco Webex Teams API to fetch a list of rooms. The API returns a response with a Link header containing a URL with a 'pageToken' parameter. What should the developer do to retrieve the next page of results?
⚠ Common exam trap
The trap here is assuming that pagination always uses a page number or an offset parameter, when many modern APIs use opaque tokens provided in the Link header.
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
✓
Extract the URL from the Link header and make a GET request to that URL.
The Link header in HTTP responses provides a ready-to-use URL for the next page of results. The developer should extract that URL and perform a GET request to it. This approach is consistent with RFC 5988 and is the method used by Cisco Webex APIs for cursor-based pagination.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increment the 'page' query parameter by 1 and resend the original request.
Why it's wrong here
The Webex API does not use a 'page' query parameter for pagination. It uses a 'pageToken' parameter provided in the Link header. Incrementing a 'page' parameter would not work because the API does not recognize it and would likely return the same first page or an error.
- ✓
Extract the URL from the Link header and make a GET request to that URL.
Why this is correct
The Link header follows RFC 5988 and contains a URL for the next page. The developer must parse the header, extract the URL, and issue a GET request to it to retrieve the next set of results. This is the standard cursor-based pagination method used by the Webex API.
- ✗
Use the 'next' field in the JSON response body to construct a new request.
Why it's wrong here
The Webex API does not include a 'next' field in the JSON response body for pagination. Pagination information is provided in the HTTP Link header, not in the body. Relying on a non-existent field would cause the script to fail to retrieve subsequent pages.
- ✗
Send a POST request to the same endpoint with the 'pageToken' in the request body.
Why it's wrong here
Pagination for GET requests is done via GET requests, not POST. The 'pageToken' is passed as a query parameter in the URL from the Link header, not in the request body. Using POST would be incorrect and likely result in an error or unexpected behavior.
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.