What is one reason to prefer REST over SOAP in API design when limited resources are available?

• A. REST requires more complex configurations
• B. REST permits multiple data formats
• C. REST cannot cache reads
• D. REST uses non-standard protocols

Answer: (B)

Choosing REST over SOAP in API design, especially when resources are limited, is often supported by the fact that REST permits multiple data formats. This versatility allows development teams to work with the data formats that best fit their needs and infrastructure, such as JSON, XML, HTML, and plain text. JSON, in particular, is lightweight and easier to parse, making it an ideal choice for mobile or web applications where bandwidth and data processing capabilities are concerns. This flexibility can lead to faster development cycles and simpler integration with various clients and servers, thus optimizing resource use.

In contrast to this, complexity in configurations, limited caching capabilities, and reliance on non-standard protocols are not the primary strengths of REST when compared to SOAP. The simplicity and lighter nature of REST APIs make them more suitable for constrained environments where system resources, such as time, processing power, and bandwidth, may be limited.