Which statement best captures REST resource modeling practice?

Which statement best captures REST resource modeling practice?

• A. REST endpoints should be action-centric.
• B. Use a single endpoint for all operations.
• C. Model APIs around nouns (resources) and use plural endpoints such as /events and /bookings.
• D. Avoid using HTTP methods to map CRUD operations.

Answer: (C)

The main idea here is that REST APIs are built around resources, which are named as nouns and typically exposed via plural endpoints. Using nouns like events and bookings communicates what you’re working with as resources, and the endpoints represent collections (e.g., /events, /bookings) rather than actions. The actual operations on these resources are conveyed with standard HTTP methods: GET to read, POST to create, PUT/PATCH to update, and DELETE to remove. This separation—resources identified by nouns, actions expressed through HTTP methods—keeps the API intuitive, scalable, and interoperable. Endpoints that are action-centric resemble RPC more than REST and miss the resource-focused modeling, while a single endpoint for all operations or avoiding HTTP methods undermines the clear semantics REST aims to provide.

The main idea here is that REST APIs are built around resources, which are named as nouns and typically exposed via plural endpoints. Using nouns like events and bookings communicates what you’re working with as resources, and the endpoints represent collections (e.g., /events, /bookings) rather than actions. The actual operations on these resources are conveyed with standard HTTP methods: GET to read, POST to create, PUT/PATCH to update, and DELETE to remove. This separation—resources identified by nouns, actions expressed through HTTP methods—keeps the API intuitive, scalable, and interoperable. Endpoints that are action-centric resemble RPC more than REST and miss the resource-focused modeling, while a single endpoint for all operations or avoiding HTTP methods undermines the clear semantics REST aims to provide.