Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Retrieve information
Submit or create data
Update or replace a resource
Remove a resource
CCNA AI and Network Operations Practice Question
Match each REST-style method to the action it most commonly represents.
⚠ Common exam trap
The exam often tests the distinction between PUT (full replacement) and PATCH (partial modification). Many candidates incorrectly assign PUT to 'update' and PATCH to 'replace'.
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
✓
GET - Retrieve, POST - Create, PUT - Replace, PATCH - Partial Modify, DELETE - Remove, HEAD - Headers only
REST methods are standardized: GET retrieves, POST creates, PUT replaces, PATCH partially modifies, DELETE removes, and HEAD retrieves only headers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
GET - Retrieve, POST - Create, PUT - Replace, PATCH - Partial Modify, DELETE - Remove, HEAD - Headers only
Why this is correct
GET is a safe, read-only method used to retrieve a representation of a resource, while POST is the standard method for creating a new resource under a given URI. PUT replaces the entire target resource with the request payload, whereas PATCH applies a partial modification, and DELETE removes the resource entirely. HEAD is identical to GET but returns only response headers, no body.
- ✗
GET - Retrieve, POST - Update, PUT - Create, PATCH - Delete, DELETE - Replace, HEAD - Headers only
Why it's wrong here
This pairing systematically misassigns HTTP verbs: POST is for creating resources, not updating them; PUT is for full replacement, not creation; PATCH is for partial modification, not deletion; and DELETE is for removal, not replacement. The error likely stems from treating these methods as generic actions rather than their defined REST semantics, so each mapping violates RFC 7231.
When this WOULD be correct
If the question asked to match methods to actions in a non-standard API design (e.g., a legacy system where POST updates, PUT creates, PATCH deletes, DELETE replaces), this option would be correct.
- ✗
GET - Retrieve, POST - Create, PUT - Update, PATCH - Replace, DELETE - Remove, HEAD - Headers only
Why it's wrong here
Here PUT is mistakenly labeled 'Update' when it actually demands a complete replacement of the resource representation, and PATCH is labeled 'Replace' when it only modifies a subset of fields. This inversion conflates idempotent full updates with partial, targeted changes, leading clients to either over-send data or under-apply changes.
When this WOULD be correct
If the exam question defined PUT as 'Update entire resource' and PATCH as 'Replace specific fields' (non-standard but possible in some contexts), or if the question asked for 'most common' actions in a system where PUT is used for updates and PATCH for full replacement.
- ✗
GET - Retrieve, POST - Create, PUT - Replace, PATCH - Update, DELETE - Remove, HEAD - Headers only
Why it's wrong here
This mapping is incorrect because 'update' is ambiguous: PUT performs a full replacement of the resource, not a generic update, and PATCH is specifically designated for partial modifications. Using 'update' for PATCH blurs the distinction between replacing the whole entity and changing only selected fields, which is critical for API correctness.
When this WOULD be correct
If the question defined PATCH as 'Update' and PUT as 'Replace' (e.g., in a non-standard API design scenario), then D would match. For example, a question that says 'Match each method to its most common action in a system where PUT replaces entire resources and PATCH updates fields' would make D correct.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓GET - Retrieve, POST - Create, PUT - Replace, PATCH - Partial Modify, DELETE - Remove, HEAD - Headers onlyCorrect answer▾
Why this is correct
GET is a safe, read-only method used to retrieve a representation of a resource, while POST is the standard method for creating a new resource under a given URI. PUT replaces the entire target resource with the request payload, whereas PATCH applies a partial modification, and DELETE removes the resource entirely. HEAD is identical to GET but returns only response headers, no body.
✗GET - Retrieve, POST - Update, PUT - Create, PATCH - Delete, DELETE - Replace, HEAD - Headers onlyWrong answer — click to see why▾
Why this is wrong here
POST is for creating resources, not updating; PUT is for replacing, not creating; PATCH is for partial modification, not deleting; DELETE is for removing, not replacing.
★ When this WOULD be the correct answer
If the question asked to match methods to actions in a non-standard API design (e.g., a legacy system where POST updates, PUT creates, PATCH deletes, DELETE replaces), this option would be correct.
Why candidates choose this
Candidates often confuse POST and PUT, mistakenly thinking POST can update and PUT can create, and may misremember PATCH and DELETE actions.
✗GET - Retrieve, POST - Create, PUT - Update, PATCH - Replace, DELETE - Remove, HEAD - Headers onlyWrong answer — click to see why▾
Why this is wrong here
In REST, PUT is idempotent and typically used for full replacement, not update; PATCH is for partial modification. Option C incorrectly assigns PUT to Update and PATCH to Replace.
★ When this WOULD be the correct answer
If the exam question defined PUT as 'Update entire resource' and PATCH as 'Replace specific fields' (non-standard but possible in some contexts), or if the question asked for 'most common' actions in a system where PUT is used for updates and PATCH for full replacement.
Why candidates choose this
Candidates often confuse PUT and PATCH because both are used for modifying resources, and many APIs use PUT for updates, leading to the misconception that PUT is the standard update method.
✗GET - Retrieve, POST - Create, PUT - Replace, PATCH - Update, DELETE - Remove, HEAD - Headers onlyWrong answer — click to see why▾
Why this is wrong here
In REST, PATCH is for partial modification, not full update; PUT is for replace/update. Option D incorrectly assigns 'Update' to PATCH, which is actually 'Partial Modify'.
★ When this WOULD be the correct answer
If the question defined PATCH as 'Update' and PUT as 'Replace' (e.g., in a non-standard API design scenario), then D would match. For example, a question that says 'Match each method to its most common action in a system where PUT replaces entire resources and PATCH updates fields' would make D correct.
Why candidates choose this
Candidates often confuse PATCH and PUT because both modify resources; they may think 'Update' is a general term for PATCH, overlooking that PUT is for full replacement and PATCH for partial changes.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.