Bird
0
0

Why might page-based pagination cause inconsistent results when data changes frequently during pagination?

hard📝 Conceptual Q10 of 15
Rest API - Pagination Patterns
Why might page-based pagination cause inconsistent results when data changes frequently during pagination?
ABecause page-based pagination caches old data permanently
BBecause page-based pagination encrypts data causing delays
CBecause page numbers refer to fixed slices, data insertions or deletions shift items causing duplicates or skips
DBecause page-based pagination requires clients to send tokens
Step-by-Step Solution
Solution:
  1. Step 1: Understand page-based pagination behavior

    Page numbers correspond to fixed slices of data based on offset and limit.
  2. Step 2: Consider data changes impact

    If data is inserted or deleted between requests, the fixed slices shift, causing some items to appear twice or be skipped.
  3. Final Answer:

    Because page numbers refer to fixed slices, data insertions or deletions shift items causing duplicates or skips -> Option C
  4. Quick Check:

    Data changes cause shifting in page-based pagination [OK]
Quick Trick: Data changes shift pages causing duplicates or missing items [OK]
Common Mistakes:
  • Thinking pagination encrypts or caches data
  • Confusing page-based with cursor-based pagination
  • Assuming tokens are required for page-based pagination

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Rest API Quizzes