easyMultiple ChoiceObjective-mapped
200-901 Practice Question: A Python script uses the Cisco Webex API to list…
A Python script uses the Cisco Webex API to list all rooms. The response includes pagination via the 'Link' header with 'rel="next"'. What is the correct way to retrieve the next page of rooms?
⚠ Common exam trap
Cisco often tests the misconception that pagination always uses simple page numbers or offsets, but the trap here is that the Webex API uses the Link header with 'rel="next"' for cursor-based pagination, and candidates may incorrectly assume a traditional page counter or offset approach.
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 URL with 'rel="next"' and send a GET request to that URL.
The Webex API uses HTTP Link headers for pagination, as specified in RFC 5988. The 'Link' header contains a URL with 'rel="next"' that points directly to the next page of results. To retrieve the next page, you must parse this header, extract the URL, and send a GET request to that URL. This is the standard approach for cursor-based or token-based pagination, which is common in RESTful APIs that avoid offset-based pagination for consistency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Parse the 'Link' header for the URL with 'rel="next"' and send a GET request to that URL.
Why this is correct
This is the correct method for cursor-based pagination.
- ✗
Increment a page counter and append '?page=2' to the original URL.
Why it's wrong here
Webex API uses cursor-based pagination, not page numbers; appending '?page=2' may not work.
- ✗
Use the total count returned in the response to calculate the offset.
Why it's wrong here
Offset-based pagination is not used; using total count may not yield correct results.
- ✗
Send a POST request to the same endpoint with the 'cursor' parameter.
Why it's wrong here
Retrieving data should use GET, not POST, and cursor is not passed as a parameter.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 989 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.