nerdexam
Cisco

200-301 · Question #927

Drag and Drop Question Drag and drop the REST principles from the left onto their definitions on the right. Answer:

The correct answer is client-server; layered system; cacheable; stateless; uniform interface. The correct arrangement maps each REST principle to its definition based on the six core Fielding REST constraints: client-server separates UI concerns from data storage concerns; layered system means a client cannot tell whether it is connected directly to the end server or an i

Submitted by suresh_in· Mar 5, 2026Understanding RESTful API architectural principles and constraints, typically covered in API development, cloud integration, or web services certification domains (e.g., MuleSoft, AWS, CompTIA Cloud+, or API-focused exams).

Question

Drag and Drop Question Drag and drop the REST principles from the left onto their definitions on the right. Answer:

Exhibits

200-301 question #927 exhibit 1
200-301 question #927 exhibit 2

Answer Area

Drag items

cacheableclient-serverlayered systemstatelessuniform interface

Correct arrangement

  • client-server
  • layered system
  • cacheable
  • stateless
  • uniform interface

Explanation

The correct arrangement maps each REST principle to its definition based on the six core Fielding REST constraints: client-server separates UI concerns from data storage concerns; layered system means a client cannot tell whether it is connected directly to the end server or an intermediary; cacheable requires responses to define themselves as cacheable or non-cacheable to improve efficiency; stateless means each request from client to server must contain all information needed to understand the request, with no session state stored server-side; and uniform interface centralizes and decouples the architecture by applying a generalized interface between components. These definitions are foundational to RESTful API design and are directly tied to Roy Fielding's original dissertation constraints.

Topics

#REST principles#API design#web services#architectural constraints

Community Discussion

No community discussion yet for this question.

Full 200-301 Practice