Which statement best describes REST resource modeling?

Which statement best describes REST resource modeling?

• A. REST Resource Modeling focuses on actions like 'bookTicket' rather than resources.
• B. REST Resource Modeling focuses on nouns (resources) and uses plural endpoints; for example POST /events/{id}/bookings creates a booking resource.
• C. REST resources should always be singular.
• D. REST endpoints should be randomly named.

Answer: (B)

REST resource modeling focuses on representing data as resources described by nouns, not actions. Endpoints are built around resource types, typically using plural names to denote collections, while specific resources are addressed with identifiers. HTTP methods express the operations on those resources. For example, POST /events/{id}/bookings creates a booking resource linked to a particular event, illustrating how a sub-resource models a relationship and how creation is performed through the HTTP verb rather than naming an action in the path. This approach keeps the design centered on resources and their lifecycles rather than verb-based actions in URLs. The other statements drift toward action-oriented paths, insist on singular resource names, or suggest arbitrary naming, which doesn’t align with common REST resource modeling practices.

REST resource modeling focuses on representing data as resources described by nouns, not actions. Endpoints are built around resource types, typically using plural names to denote collections, while specific resources are addressed with identifiers. HTTP methods express the operations on those resources. For example, POST /events/{id}/bookings creates a booking resource linked to a particular event, illustrating how a sub-resource models a relationship and how creation is performed through the HTTP verb rather than naming an action in the path. This approach keeps the design centered on resources and their lifecycles rather than verb-based actions in URLs. The other statements drift toward action-oriented paths, insist on singular resource names, or suggest arbitrary naming, which doesn’t align with common REST resource modeling practices.