Continuation Token
← Back to DP-420 Terminology Reference
Category: Client Connectivity & SDK
Summary: Opaque value used to resume a paginated query/feed from where the last page left off.
Overview
A continuation token is an opaque value returned by Azure Cosmos DB when a query or read-feed operation has more results available than were returned in the current page. Passing this token back into the next request resumes retrieval exactly where the previous page left off, enabling efficient, stateless pagination across large result sets.
More Info & Links
DP-420 Style Practice Questions
Q1. What is the purpose of a continuation token in Azure Cosmos DB?
- A. Resuming a paginated query or read-feed operation from where the previous page left off
- B. Encrypting query results in transit
- C. Authenticating the client against Microsoft Entra ID
- D. Specifying the container's partition key
Q2. When would a client receive a continuation token from Azure Cosmos DB?
- A. When a query or feed operation has more results available beyond the current page
- B. Only when using the Table API
- C. Only when TTL is enabled
- D. Only during a regional failover
Answer Key
Answers are listed at the very end so you can attempt the questions first.
- Q1 (Continuation Token): A. Resuming a paginated query or read-feed operation from where the previous page left off — Continuation tokens allow stateless pagination by letting subsequent requests resume exactly where the last page ended.
- Q2 (Continuation Token): A. When a query or feed operation has more results available beyond the current page — A continuation token is returned whenever there are additional results beyond what was returned in the current page.
DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page
