hardMultiple SelectObjective-mapped
REST API Design Best Practices: Using Nouns for Resources
Which TWO statements about REST API design best practices are correct?
Quick Answer
The correct answer is that HTTP verbs should describe the action performed on the resource. This is because REST API design best practices dictate that URIs should represent resources as nouns, not verbs—so endpoints like `/users` or `/orders` identify the resource, while the HTTP method (GET, POST, PUT, DELETE) conveys the action. Using verbs in the URI, such as `/getUsers` or `/createOrder`, conflates the resource with the operation and violates the uniform interface constraint, making the API less intuitive and harder to maintain. On the Cisco DevNet Associate 200-901 exam, this concept tests your understanding of RESTful design principles, often appearing in questions that ask you to identify correct URI patterns or distinguish between resource-oriented and action-oriented endpoints. A common trap is confusing the use of HTTP verbs with the URI structure—remember that the verb belongs in the request header, not the path. For a quick memory tip: think of your API as a library—you ask for a book (noun) at the counter, but the action of checking it out (verb) is handled by the librarian, not by renaming the book.
⚠ Common exam trap
Cisco often tests the distinction between PUT (full replacement) and PATCH (partial update), and the trap here is that candidates mistakenly think PUT can be used for partial updates because they overlook the idempotent, full-replacement semantics defined in RFC 7231.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Resources should be represented using nouns in the URI
REST API best practices dictate that URIs should represent resources (nouns), not actions. For example, '/users' or '/orders' clearly identifies the resource being manipulated, while verbs like '/getUsers' or '/createOrder' are discouraged as they conflate the resource with the operation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
API versioning should be implemented using query parameters only
Why it's wrong here
Versioning via query parameters is uncommon; path or header versioning is preferred.
- ✗
HTTP PUT method should be used for partial updates to a resource
Why it's wrong here
PUT is for full replacement; PATCH is for partial updates.
- ✓
Resources should be represented using nouns in the URI
Why this is correct
Using nouns for resources (e.g., /devices) is a REST best practice.
- ✗
Responses should return only HTTP status codes without a body
Why it's wrong here
Responses typically include a body with details or representation of the resource.
- ✓
HTTP verbs should describe the action performed on the resource
Why this is correct
Verbs like GET, POST, PUT, DELETE define the action.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 989-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on 200-901
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO statements about REST API design best practices are true? (Choose two.)
medium- A.Avoid API versioning to keep the API simple
- B.Include the HTTP method in the URI path, e.g., /getDevices
- C.Always use file-based transfer for large payloads
- ✓ D.Use nouns for resource endpoints, e.g., /devices instead of /getDevices
- ✓ E.Use HTTP methods appropriately: GET for retrieval, POST for creation, etc.
Why D: RESTful APIs use nouns to represent resources (e.g., /devices) rather than verbs (e.g., /getDevices). This aligns with the uniform interface constraint of REST, where the HTTP method (GET, POST, etc.) defines the action, and the URI identifies the resource. Using nouns keeps the API intuitive, consistent, and scalable.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.