Which architectural style is standardized and stateless, commonly used for web service communication?

Which architectural style is standardized and stateless, commonly used for web service communication?

• A. REST
• B. OAuth
• C. JSON
• D. on-premises network

Answer: (A)

REST is an architectural style that defines how networked services should be designed to be interoperable and scalable. Its stateless constraint means every client request carries all the information the server needs; the server doesn’t rely on stored session data between requests. This makes servers simpler and easier to scale and load-balance, since any server can handle any request without needing to share session state. REST maps naturally to the web by using a uniform interface and standard HTTP methods like GET, POST, PUT, and DELETE to operate on resources identified by URLs. This alignment with the existing web infrastructure also supports caching and layered system designs, improving performance and flexibility. While JSON (a data format) is commonly used to represent REST resources, REST itself is not a data format—the style governs how resources are addressed and manipulated over HTTP. OAuth is an authorization framework, not an architectural style. JSON is a data interchange format. An on-premises network describes where infrastructure is deployed, not how services are architected.

REST is an architectural style that defines how networked services should be designed to be interoperable and scalable. Its stateless constraint means every client request carries all the information the server needs; the server doesn’t rely on stored session data between requests. This makes servers simpler and easier to scale and load-balance, since any server can handle any request without needing to share session state.

REST maps naturally to the web by using a uniform interface and standard HTTP methods like GET, POST, PUT, and DELETE to operate on resources identified by URLs. This alignment with the existing web infrastructure also supports caching and layered system designs, improving performance and flexibility. While JSON (a data format) is commonly used to represent REST resources, REST itself is not a data format—the style governs how resources are addressed and manipulated over HTTP.

OAuth is an authorization framework, not an architectural style. JSON is a data interchange format. An on-premises network describes where infrastructure is deployed, not how services are architected.