200-901 Understanding and Using APIs Practice Question
A developer is building a Python script that calls the Cisco Webex Teams API to list all memberships in a room. The API returns a maximum of 100 items per page and includes a 'Link' header in the response. The developer needs to retrieve all memberships across multiple pages. What is the correct approach to handle pagination using the Link header?
⚠ Common exam trap
The trap here is assuming that pagination is always done via query parameters like page or offset, when many Cisco APIs use Link headers instead.
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
✓
Parse the Link header for the 'rel="next"' URL and make a GET request to that URL to retrieve the next page of results, repeating until no 'next' link is present.
The correct approach is to parse the Link header for the 'rel="next"' URL and follow it. This is how the Webex Teams API implements pagination, using RFC 5988 Link headers. The other options suggest methods not supported by this API, such as page numbers, max parameter for all items, or body tokens. Following the next link ensures all pages are retrieved correctly.
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 'max' query parameter to request all memberships in a single response, avoiding pagination.
Why it's wrong here
The 'max' parameter limits the number of items per page, but the API enforces a maximum of 100 items per page regardless. It cannot return all memberships in one response. Therefore, this approach fails to retrieve all data and is not a valid pagination strategy.
- ✗
Extract the 'nextPageToken' from the JSON response body and include it as a query parameter in the next request.
Why it's wrong here
The Webex Teams API does not include a 'nextPageToken' in the JSON body. Pagination information is provided in the Link header, not the body. Using a token from the body would not work because such a field does not exist, leading to errors or incomplete data retrieval.
- ✗
Increment the 'page' query parameter by 1 in each subsequent request until an empty response is returned.
Why it's wrong here
The Webex Teams API does not use a 'page' query parameter for pagination. It uses cursor-based pagination via the Link header. Incrementing a 'page' parameter would not work because the API ignores such a parameter, leading to repeated or incorrect results. This approach is invalid for this API.
- ✓
Parse the Link header for the 'rel="next"' URL and make a GET request to that URL to retrieve the next page of results, repeating until no 'next' link is present.
Why this is correct
The Link header follows RFC 5988 and contains URLs for pagination, with rel="next" indicating the next page. Making a GET request to that URL retrieves the next set of memberships. Repeating until no 'next' link appears ensures all pages are collected. This is the standard method for Webex Teams API pagination.
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.