200-901 Cisco Platforms and Development Practice Question
A developer is writing a Python script to interact with a Cisco Meraki Dashboard API. The script retrieves a list of organizations and then, using the organization ID, retrieves the networks for that organization. The API returns a 200 OK with a JSON body and a Link header containing a URL for the next page. The developer wants to ensure all networks are retrieved. Which approach should the developer take?
⚠ Common exam trap
The trap here is assuming that pagination is done with simple page numbers or offsets, rather than the cursor-based Link header used by Meraki.
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 and follow the URL for the next page until no Link header is present.
The Meraki Dashboard API implements pagination using the Link header, which contains a URL for the next page of results. To retrieve all networks, the developer must follow the 'next' link until it is absent. Other methods like using a 'page' parameter, increasing 'perPage', or looking for an 'offset' field do not align with the API's design and will not work.
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 and follow the URL for the next page until no Link header is present.
Why this is correct
The Meraki Dashboard API uses pagination via the Link header. When more results exist, the Link header includes a rel="next" URL. By following that URL until no next link is provided, the developer can retrieve all networks. This is the correct method to handle pagination in the Meraki API.
- ✗
Parse the response for an 'offset' field and use it in subsequent requests until the offset equals the total count.
Why it's wrong here
The Meraki API does not include an 'offset' field in its responses. Pagination is handled via the Link header with a cursor-based approach. Looking for an 'offset' field would yield no results, and the developer would not retrieve additional pages. This method is incorrect for the Meraki API.
- ✗
Use the 'perPage' query parameter set to 1000 to retrieve all networks in a single request.
Why it's wrong here
The Meraki API has a maximum 'perPage' limit (typically 1000 for some endpoints, but often 100 for others). Even if set to the maximum, it may not return all networks if the total exceeds that limit. The Link header must still be followed for complete results. Thus, this approach is insufficient.
- ✗
Send the same GET request with an increased 'page' query parameter until an empty array is returned.
Why it's wrong here
The Meraki API does not use a 'page' query parameter for pagination. Instead, it uses the Link header with a 'startingAfter' parameter for cursor-based pagination. Using a 'page' parameter would be ignored, and the developer would repeatedly receive the first page, never retrieving all networks.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 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 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.