What are two main guiding principles of REST? (Choose two.)

Question

Options

• Acacheable
• Btrackable
• Cstateless
• Dsingle-layer system

• A
  4% (1)
• C
  93% (26)
• D
  4% (1)

Explanation

Stateless (C) and Cacheable (A) are both correct - the question asks for two, and the listed answer appears incomplete. Both are official REST architectural constraints defined by Roy Fielding.

Stateless (C) means each client request must contain all information needed to process it; the server holds no session state between requests. This simplifies scaling because any server instance can handle any request. Cacheable (A) means responses must indicate whether they can be cached, allowing clients or intermediaries to reuse responses and reduce server load.

Trackable (B) is not a REST constraint at all - it's a distractor with no formal definition in REST architecture. Single-layer system (D) inverts a real constraint: REST requires a layered system (multiple layers like load balancers, caches, gateways are allowed), not a single-layer one.

Memory tip: Think of REST as a SUCLU system - Stateless, Uniform interface, Cacheable, Layered, Client-server (plus optional Code-on-demand). If an answer choice contradicts or invents a constraint (trackable, single-layer), it's wrong.

No community discussion yet for this question.