Skip to content
javabypankaj
HomeLibraryPopularCommunity
14
REST API & Web
8 topics · 40 questions
1REST Fundamentals0/222HTTP Methods0/553HTTP Status Codes0/444Error Handling & Problem Details0/115Caching & ETags0/116Pagination, Filtering & HATEOAS0/47API Versioning & Content Negotiation0/118API Design Best Practices0/2222
1REST Fundamentals22HTTP Methods53HTTP Status Codes44Error Handling & Problem Details15Caching & ETags16Pagination, Filtering & HATEOAS47API Versioning & Content Negotiation18API Design Best Practices22
8 topics40 Qs0%
01Core Java17002OOP3203Collections6704Exception Handling2805Concurrency & Multithreading12706Java Streams, Lambda & Functional Programming32807Spring & Spring Boot2608Transactions3209JPA & Hibernate6910Microservices19411Kafka & Messaging9112DevOps, CI/CD & Tooling13313Database & SQL14114REST API & Web4015Design Patterns & LLD5716Advanced Java7117Coding Problems: DSA49218AWS & Cloud4119Data Engineering19420QA, Testing & SDET4121System Design3522Security2023Behavioral / HR: STAR Method37
8Topics
40Questions
0%Complete
6 of 8 topics
Topics
1REST Fundamentals0/222HTTP Methods0/553HTTP Status Codes0/444Error Handling & Problem Details0/115Caching & ETags0/11
6Pagination, Filtering & HATEOAS0/44
7API Versioning & Content Negotiation0/118API Design Best Practices0/2222

Pagination, Filtering & HATEOAS

REST API & Web·Topic 6 of 8·4 questions
Q1How do you design pagination in a REST API and why does offset pagination break at deep pages

Offset pagination is simple but slows down at deep pages because the database skips all preceding rows; cursor or keyset pagination stays fast by jumping to the slice after the last seen key.

Read Answer
Q2How do you design filtering and sorting in a REST API and why whitelist fields

Expose filtering and sorting through query parameters, but only against a server-side whitelist of allowed fields, because arbitrary column names invite SQL injection, schema leakage, and unindexed sorts.

Read Answer
Q3What is HATEOAS in practice and why do most real-world REST APIs skip it

HATEOAS means responses carry links to the next possible actions so clients navigate by following them, but most APIs skip full HATEOAS because the complexity outweighs the benefit, preferring OpenAPI documentation instead.

Read Answer
Q4Explain HATEOAS and its role in REST APIs, with Spring HATEOAS

HATEOAS means responses carry links telling the client what actions are possible next from the current state, so clients follow links instead of hardcoding URLs.

Read Answer
Previous · Topic 5Caching & ETags1 questionsNext · Topic 7API Versioning & Content Negotiation1 questions
javabypankaj© 2026 javabypankaj
PrivacyTerms
HomeSearchLibrary