Cisco Platforms and Development →mediumMultiple SelectObjective-mapped

200-901 Cisco Platforms and Development Practice Question

A developer is using the Meraki Dashboard API to list all networks in an organization. Which TWO of the following are valid methods for pagination?

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

✓

startingAfter and endingBefore parameters

Meraki supports Link header with rel="next" and the startingAfter/endingBefore parameters for pagination.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✗
offset and limit parameters
Why it's wrong here
Not used by Meraki.
✓
startingAfter and endingBefore parameters
Why this is correct
Correct. These parameters are used for cursor-based pagination.
✗
X-Next-Page header
Why it's wrong here
Not used by Meraki.
✗
page and perPage parameters
Why it's wrong here
Meraki uses perPage, but not page number; it uses cursors.
✓
Link header with rel="next"
Why this is correct
The Meraki Dashboard API uses the HTTP `Link` header with `rel="next"` to implement cursor-based pagination, where the header contains the URL for the next page of network objects. This satisfies the stem’s requirement for a valid pagination method because the API does not support offset-based or page-number parameters; instead, it relies on this standardised header to traverse result sets sequentially.

Go deeper