300-435 Question 11
Single answerAn enterprise network engineer is automating configurations for a set of network devices using APIs. The engineer needs a stateless API style that adheres to standard HTTP methods, supports a variety of media types for data exchange, and is suitable for web-based integrations. Which API style should the engineer choose?
- A
REST
- B
RPC
- C
SOAP
- D
gRPC
Show answer and explanation
Correct answer: A
Explanation
REST is the correct choice because it is a stateless API style that uses standard HTTP methods (e.g., GET, POST) and supports a variety of media types such as JSON and XML. These characteristics make it highly suitable for web-based integrations. RPC, SOAP, and gRPC, while useful in specific scenarios, do not meet the requirements outlined in the question.
- A. Correct.
REST (Representational State Transfer) is a stateless API style that uses standard HTTP methods such as GET, POST, PUT, and DELETE. It is widely used for web-based integrations and supports various media types such as JSON and XML for data exchange.
- B. Incorrect.
RPC (Remote Procedure Call) focuses on executing procedures on a remote server rather than adhering to HTTP standards. It is not stateless and does not use standard HTTP methods for operations, making it less suitable for web-based integrations.
- C. Incorrect.
SOAP (Simple Object Access Protocol) is a protocol rather than an API style. Although it supports stateless operations, it is more complex and not as commonly used for modern web-based integrations as REST.
- D. Incorrect.
gRPC is a high-performance RPC framework that uses HTTP/2 and Protocol Buffers for communication. While it is efficient, it is not designed to adhere to standard HTTP methods or media types, making it less suitable for web-based integrations compared to REST.