Which two options are REST principles? (Choose two.)

Question

Options

• ARESTful applications use a stateless architecture.
• BRESTful application use HTTP headers and status codes as a contract with the clients.
• CRESTful applications cannot use caching.
• DRESTful application servers keep track of the client state.
• ERESTful applications favor tight coupling between the clients and the servers.

• A
  92% (22)
• C
  4% (1)
• E
  4% (1)

Explanation

Statelessness (A) is a core REST constraint - each request from client to server must contain all the information needed to process it; the server stores no session state between requests. HTTP headers and status codes as a contract (B) reflects REST's use of the HTTP protocol natively, where status codes (200, 404, 500, etc.) and headers (Content-Type, Authorization) communicate meaning between client and server without out-of-band agreements.

C is wrong because REST explicitly encourages caching - responses should be labeled as cacheable or non-cacheable to improve performance. D is wrong because it's the direct opposite of A; REST servers are stateless and do not track client state between requests. E is wrong because REST favors loose coupling - clients and servers interact only through a uniform interface, allowing each to evolve independently.

Memory tip: Think of REST as a forgetful waiter - each time you call, you must re-introduce yourself (stateless), and the restaurant uses a standard menu and pricing system everyone understands (HTTP as the uniform contract). The waiter doesn't remember your last order, but the kitchen can cache your favorite dish.

No community discussion yet for this question.