Drag a concept onto its matching description — or click a concept then click the description.
Retrieve a resource
Create a new resource
Update or replace a resource
Remove a resource
Match each HTTP method to the action it most commonly performs in a REST API.
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve a resource
Create a new resource
Update or replace a resource
Remove a resource
⚠ Common exam trap
In this question, focus on the four methods given: GET, POST, PUT, PATCH. The most common pitfall is confusing PUT (full replacement) with PATCH (partial update). Also, remember that POST is for creating resources, not for updating or reading. Do not apply the DELETE concept here.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
GET: Retrieve a resource or collection of resources.
All listed mappings are correct according to RESTful API conventions. GET retrieves a resource, POST creates a new resource, PUT replaces an existing resource, and PATCH applies a partial update.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
GET: Retrieve a resource or collection of resources.
Why this is correct
GET is a safe and idempotent HTTP method used to retrieve a representation of a resource or a collection of resources from a server. It must not cause any side effects on the server state, making it ideal for read-only operations in RESTful APIs. GET requests are commonly cached and should never be used for submitting data that changes server state.
POST: Create a new resource.
Why this is correct
POST is a non-idempotent HTTP method used to create a new resource on the server. When a POST request is sent, the server processes the entity enclosed in the request body and creates a subordinate resource, typically returning a 201 Created status code with a Location header pointing to the new resource. Because each POST request can result in a different resource being created, POST is not safe for repeated submissions without additional safeguards.
PUT: Update or replace an existing resource.
Why this is correct
PUT is an idempotent HTTP method used to update or replace an existing resource at a specific URI. The client sends a complete representation of the resource, and the server replaces the entire current representation with the payload, preserving the resource's identity. Because PUT is idempotent, sending the same PUT request multiple times has the same effect as sending it once, which is a key distinction from POST.
PATCH: Partially update an existing resource.
Why this is correct
PATCH is an HTTP method used to apply partial modifications to an existing resource, unlike PUT which replaces the entire resource. The request body contains a set of instructions describing how the resource should be changed, often using formats like JSON Patch or merge-patch. PATCH is not necessarily idempotent, as the effect of a patch can depend on the current state of the resource, although certain patch documents can be designed to be idempotent.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: May 17, 2026
This 200-301 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-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.