Question 1

True or false: Using query parameters like /users?id=5 is more RESTful than /users/5.

Accepted Answer

False. REST favors hierarchical resource paths; /users/5 is the standard identifier, while query parameters are for filtering collections.

Question 2

True or false: Statelessness in REST means the server never stores any session data between requests.

Accepted Answer

True. Each request from client to server must contain all necessary info; server-side sessions violate the stateless constraint.

Question 3

True or false: Returning different representations of the same resource based on the Accept header is compliant with REST constraints.

Accepted Answer

True. Content negotiation via Accept headers is a core REST constraint, allowing the same URI to serve different formats (e.g., JSON, XML) based on client preferences.

Question 4

True or false: Caching in REST APIs can reduce server load even when responses are dynamic.

Accepted Answer

True. REST encourages explicit cache headers (e.g., ETag, Cache-Control) that allow clients and intermediaries to cache dynamic responses conditionally.

Question 5

True or false: REST APIs require JSON for all request and response bodies.

Accepted Answer

False. REST is format-agnostic; it can use XML, plain text, HTML, or YAML. JSON is common but not mandatory.

Question 6

True or false: REST APIs must always use HTTP as the underlying protocol.

Accepted Answer

False. REST is an architectural style, not tied to HTTP; it can be implemented over CoAP, gRPC, or other protocols, though HTTP is most common.

Question 7

True or false: Hypermedia links in API responses are optional in a true RESTful design.

Accepted Answer

False. HATEOAS (hypermedia as the engine of application state) is a key REST constraint; without it, the API is merely HTTP RPC, not RESTful.

Question 8

True or false: Using the POST method for a safe and idempotent operation violates REST principles.

Accepted Answer

True. POST is not safe or idempotent; safe, idempotent operations (like reading data) should use GET/HEAD. Using POST breaks the RESTful contract.

REST API Trivia Questions