A team of developers is designing RESTful Web services for a new application. What are three properties of the services? (Choose three.)
A.
They can be stateful.
B.
They can be stateless.
C.
Components communicate by exchanging representations of the resource.
D.
Components communicate by directly performing operations on the resource.
E.
They require WSDL service API definitions.
F.
Responses can be labeled as cacheable or non-cacheable.
B variant is misleading. RESTful Web services are stateless by definition.
Then it’s right: stateful web service could not be called REST 🙂
which is good resource representation?
(1) easy to understand
(2) complete
(3) link to other resource
Caching your REST API
The goal of caching is never having to generate the same response twice. The benefit of doing this is that we gain speed and reduce server load. The best way to cache your API is to put a gateway cache (or reverse proxy) in front of it. Some frameworks provide their own reverse proxies, but a very powerful, open-source one is Varnish.
http://restcookbook.com/Basics/caching/
https://www.varnish-cache.org/intro/index.html#intro