Which REST constraint requires resources to be identified by unique URIs and manipulated using a uniform set of HTTP methods?

Which REST constraint requires resources to be identified by unique URIs and manipulated using a uniform set of HTTP methods?

• A. Stateless
• B. Uniform Interface
• C. Cacheable
• D. Code on Demand

Answer: (B)

Uniform Interface is the REST constraint that enforces a consistent way to interact with resources. It requires each resource to be uniquely identifiable by a URI and to be acted upon using a standard, uniform set of HTTP methods (such as GET, POST, PUT, DELETE). This standardization makes interactions predictable and decouples client and server implementations, so clients know exactly how to address a resource and perform operations on it regardless of the resource type. Stateless means each request carries all the information the server needs and the server doesn’t retain session state between requests. Cacheable means responses can be marked as cacheable to improve performance. Code on Demand means clients may execute code fetched from the server. These constraints govern other aspects of RESTful design but do not define how resources are addressed or manipulated via URIs and HTTP methods.

Uniform Interface is the REST constraint that enforces a consistent way to interact with resources. It requires each resource to be uniquely identifiable by a URI and to be acted upon using a standard, uniform set of HTTP methods (such as GET, POST, PUT, DELETE). This standardization makes interactions predictable and decouples client and server implementations, so clients know exactly how to address a resource and perform operations on it regardless of the resource type.

Stateless means each request carries all the information the server needs and the server doesn’t retain session state between requests. Cacheable means responses can be marked as cacheable to improve performance. Code on Demand means clients may execute code fetched from the server. These constraints govern other aspects of RESTful design but do not define how resources are addressed or manipulated via URIs and HTTP methods.