What architectural style defines a web service as a communication medium between systems on the web, using standard HTTP methods to operate on resources?

What architectural style defines a web service as a communication medium between systems on the web, using standard HTTP methods to operate on resources?

• A. REST
• B. SOAP
• C. GraphQL
• D. XML-RPC

Answer: (A)

REST is an architectural style for building networked applications where a web service is viewed as a collection of resources identified by URIs, and clients interact with those resources using the standard HTTP methods (such as GET, POST, PUT, DELETE). This approach emphasizes a uniform interface: each resource has a representation (often JSON or XML), and the same set of HTTP verbs perform predictable actions on any resource. The statelessness of REST means each request contains all the information needed to process it, and responses can be cached when appropriate, improving scalability. This description matches the prompt because the service operates through resources on the web and uses standard HTTP methods to manipulate those resources. SOAP, by contrast, uses a protocol with its own envelope and RPC-style operations rather than resource-based interactions. GraphQL focuses on querying data through a single endpoint rather than resource-oriented operations via HTTP methods. XML-RPC uses XML to perform remote procedure calls, not a resource-centric design.

REST is an architectural style for building networked applications where a web service is viewed as a collection of resources identified by URIs, and clients interact with those resources using the standard HTTP methods (such as GET, POST, PUT, DELETE). This approach emphasizes a uniform interface: each resource has a representation (often JSON or XML), and the same set of HTTP verbs perform predictable actions on any resource. The statelessness of REST means each request contains all the information needed to process it, and responses can be cached when appropriate, improving scalability.

This description matches the prompt because the service operates through resources on the web and uses standard HTTP methods to manipulate those resources. SOAP, by contrast, uses a protocol with its own envelope and RPC-style operations rather than resource-based interactions. GraphQL focuses on querying data through a single endpoint rather than resource-oriented operations via HTTP methods. XML-RPC uses XML to perform remote procedure calls, not a resource-centric design.