A client consumes an API that returns paginated results via Link headers. The API occasionally returns a `429 Too Many Requests` response with a `Retry-After` header. The client must retrieve all pages without being permanently blocked. What is the best strategy?

On a 429 response, wait for the number of seconds specified in `Retry-After`, then retry the same request.

Switch to a different pagination style, such as offset/limit.

Ignore the 429 response and continue with the next page.

Retry immediately with a different `User-Agent` header.

A service consumes a REST API that uses cursor-based pagination. Each response includes a `nextCursor` field, which is `null` on the last page. The initial request uses no cursor. Which loop correctly retrieves all pages?

`for i in range(100):` — fetch 100 pages unconditionally.

`while True:` — fetch pages until an empty list is returned.

`while next_cursor is not None:` — fetch, then update `next_cursor` from the response.

`while 'next' in response['links']:` — check for a next link.

What is a common strategy to handle rate limiting when iterating through a paginated API?

Ignoring the rate limit and retrying immediately

Increasing the page size to reduce the number of requests

Sending all requests in parallel to finish faster

Pausing between requests based on the Retry-After header

CiscoCertified DevNet Professional

Domain 2Objective 4

Construct an Application That Consumes a REST API That Supports Pagination 350-901 Practice Questions (Page 6)

Part of the 2.0 Using APIs domain, which accounts for 20% of the 350-901 exam. Cisco does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–16 in this domain), expect 2–3 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

9concepts

20%of the exam

9 Concepts in This Objective

Understand REST API pagination
Parse pagination metadata
Implement page-based pagination
Implement offset/limit pagination
Implement cursor-based pagination
Handle link headers
Loop through paginated responses
Aggregate paginated data
Handle pagination errors and edge cases

Questions 26–29

26expert · hard
A client consumes an API that returns paginated results via Link headers. The API occasionally returns a `429 Too Many Requests` response with a `Retry-After` header. The client must retrieve all pages without being permanently blocked. What is the best strategy?
Select an answer first
27application · medium
A service consumes a REST API that uses cursor-based pagination. Each response includes a `nextCursor` field, which is `null` on the last page. The initial request uses no cursor. Which loop correctly retrieves all pages?
Select an answer first
28foundation · easy
What is a common strategy to handle rate limiting when iterating through a paginated API?
Select an answer first
29application · easy
An API response for a page-based endpoint includes `{"items": [...], "page": 2, "perPage": 10, "totalRecords": 25}`. The client has already processed page 1. How many more requests are needed to retrieve all remaining records?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to 350-901

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “350-901” is a trademark of its owner, used for identification only.

Construct an Application That Consumes a REST API That Supports Pagination 350-901 Practice Questions (Page 6)

Questions 26–29

A client consumes an API that returns paginated results via Link headers. The API occasionally returns a `429 Too Many Requests` response with a `Retry-After` header. The client must retrieve all pages without being permanently blocked. What is the best strategy?

A service consumes a REST API that uses cursor-based pagination. Each response includes a `nextCursor` field, which is `null` on the last page. The initial request uses no cursor. Which loop correctly retrieves all pages?

What is a common strategy to handle rate limiting when iterating through a paginated API?

An API response for a page-based endpoint includes `{"items": [...], "page": 2, "perPage": 10, "totalRecords": 25}`. The client has already processed page 1. How many more requests are needed to retrieve all remaining records?

Keep studying — 2.0 Using APIs