Architectural style for web services using HTTP semantics.

Architectural style for web services using HTTP semantics.

• A. SOAP
• B. RESTful
• C. WSDL
• D. UDDI

Answer: (B)

RESTful is the architectural approach that uses HTTP semantics to interact with resources. In REST, each resource is identified by a URI, and standard HTTP methods define the actions on those resources (GET to retrieve, POST to create, PUT to update, DELETE to remove). Responses return representations of the resource, and interactions are stateless—no client context is stored on the server between requests, which aids scalability and simplicity. This HTTP-centric, resource-oriented design is what makes RESTful the best fit when the question specifies using HTTP semantics. SOAP, while it can run over HTTP, is a protocol with its own messaging format and more RPC-like patterns, not anchored to the resource-and-method model. WSDL describes how to access a service, and UDDI is a directory for discovering services; neither defines the HTTP-based architectural style for manipulating resources.

RESTful is the architectural approach that uses HTTP semantics to interact with resources. In REST, each resource is identified by a URI, and standard HTTP methods define the actions on those resources (GET to retrieve, POST to create, PUT to update, DELETE to remove). Responses return representations of the resource, and interactions are stateless—no client context is stored on the server between requests, which aids scalability and simplicity. This HTTP-centric, resource-oriented design is what makes RESTful the best fit when the question specifies using HTTP semantics.

SOAP, while it can run over HTTP, is a protocol with its own messaging format and more RPC-like patterns, not anchored to the resource-and-method model. WSDL describes how to access a service, and UDDI is a directory for discovering services; neither defines the HTTP-based architectural style for manipulating resources.