Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Retrieve a resource
Create a new resource
Update or replace a resource
Remove a resource
Question 156 of 1,389
CCNA Network Services and Security Practice Question
Match each REST API method to the action it most closely represents in a typical network automation workflow.
⚠ Common exam trap
Be careful not to confuse PUT and PATCH: PUT replaces the entire resource, while PATCH applies a partial update. Also, remember that POST is for creating new resources, not for updating. These are common traps in CCNA automation questions.
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 retrieves data, POST creates new resources, PUT updates/replaces, PATCH partially updates, DELETE removes, and OPTIONS queries available methods.
GET retrieves data, POST creates new resources, PUT updates/replaces, PATCH partially updates, DELETE removes, and OPTIONS queries available methods. These correspond to common network automation workflows.
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 retrieves data, POST creates new resources, PUT updates/replaces, PATCH partially updates, DELETE removes, and OPTIONS queries available methods.
Why this is correct
This is correct because it accurately describes the standard REST API methods and their actions in network automation workflows. GET is used to retrieve configuration or status data, POST to create new resources like interfaces or VLANs, PUT to replace entire resources, PATCH to apply partial updates, DELETE to remove resources, and OPTIONS to discover supported methods.
- ✗
GET retrieves data, POST creates new resources, PUT partially updates, PATCH updates/replaces, DELETE removes, and OPTIONS queries available methods.
Why it's wrong here
This incorrect mapping also swaps PUT and PATCH, but the more fundamental issue is that it treats the method semantics as interchangeable. In RESTful APIs, using PATCH for a full update would require a standard body where none exists, and using PUT for a partial update violates the requirement that PUT's payload be the same as what a GET would return. For network automation, this can lead to inconsistent state and failed idempotent retries.
When this WOULD be correct
If the exam question defined PUT as 'modify resource fields' (partial update) and PATCH as 'replace entire resource' (full update), then option B would match that non-standard mapping.
- ✗
GET retrieves data, POST updates/replaces, PUT creates new resources, PATCH partially updates, DELETE removes, and OPTIONS queries available methods.
Why it's wrong here
This option inverts the roles of POST and PUT. In REST, POST is used to create a new resource (e.g., adding a VLAN), while PUT replaces the entire representation of an existing resource (e.g., updating a full interface config). Because PUT is idempotent and POST is not, swapping them breaks the contract that network automation tools rely on for safe retries.
When this WOULD be correct
In a question that asks which methods are idempotent, PUT is idempotent (full update/replace) and POST is not, but if the question focused on partial updates, PATCH would be correct. However, for a matching question where PUT is defined as 'update/replace' and POST as 'create', this option would be wrong.
- ✗
GET retrieves data, POST creates new resources, PUT partially updates, PATCH updates/replaces, DELETE removes, and OPTIONS queries available methods.
Why it's wrong here
This option mistakenly assigns partial updates to PUT and full replacement to PATCH. The HTTP method PUT is defined by RFC 7231 to replace the target resource with the enclosed representation, making it idempotent, whereas PATCH is explicitly for partial modifications, such as changing only the description field of a device interface. Swapping these would cause a client sending a small change via PUT to wipe out unrelated configuration.
When this WOULD be correct
If the exam question defined PUT as 'partially updates' and PATCH as 'updates/replaces' (e.g., in a non-standard or legacy API design), then option D would be correct. For example, a question about a custom API where PUT is used for partial updates and PATCH for full replacements.
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 retrieves data, POST creates new resources, PUT updates/replaces, PATCH partially updates, DELETE removes, and OPTIONS queries available methods.Correct answer▾
Why this is correct
This is correct because it accurately describes the standard REST API methods and their actions in network automation workflows. GET is used to retrieve configuration or status data, POST to create new resources like interfaces or VLANs, PUT to replace entire resources, PATCH to apply partial updates, DELETE to remove resources, and OPTIONS to discover supported methods.
✗GET retrieves data, POST creates new resources, PUT partially updates, PATCH updates/replaces, DELETE removes, and OPTIONS queries available methods.Wrong answer — click to see why▾
Why this is wrong here
PUT is for full update/replace, not partial update; PATCH is for partial update, not full update/replace. Option B swaps these roles.
★ When this WOULD be the correct answer
If the exam question defined PUT as 'modify resource fields' (partial update) and PATCH as 'replace entire resource' (full update), then option B would match that non-standard mapping.
Why candidates choose this
Candidates often confuse PUT and PATCH because both are used for updates, and they may think 'partial' is a subset of 'update' without remembering the standard HTTP semantics.
✗GET retrieves data, POST updates/replaces, PUT creates new resources, PATCH partially updates, DELETE removes, and OPTIONS queries available methods.Wrong answer — click to see why▾
Why this is wrong here
Option C incorrectly swaps the roles of PUT and POST: PUT is for creating/replacing resources, not updating/replacing, and POST is for creating, not updating/replacing.
★ When this WOULD be the correct answer
In a question that asks which methods are idempotent, PUT is idempotent (full update/replace) and POST is not, but if the question focused on partial updates, PATCH would be correct. However, for a matching question where PUT is defined as 'update/replace' and POST as 'create', this option would be wrong.
Why candidates choose this
Candidates may confuse PUT and POST because both can be used to create resources in some APIs, and they might think PUT is for updates only, not replacements.
✗GET retrieves data, POST creates new resources, PUT partially updates, PATCH updates/replaces, DELETE removes, and OPTIONS queries available methods.Wrong answer — click to see why▾
Why this is wrong here
This option incorrectly swaps the actions for PUT and PATCH: PUT should be used for full updates/replacements, while PATCH is for partial updates. In REST APIs, PUT is idempotent and replaces the entire resource, whereas PATCH applies partial modifications.
★ When this WOULD be the correct answer
If the exam question defined PUT as 'partially updates' and PATCH as 'updates/replaces' (e.g., in a non-standard or legacy API design), then option D would be correct. For example, a question about a custom API where PUT is used for partial updates and PATCH for full replacements.
Why candidates choose this
Candidates often confuse PUT and PATCH because both are used for updates, and the terms 'partial' and 'replace' can be misremembered. The similarity in their purposes makes it easy to swap their definitions under exam pressure.
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?”
Visual reference
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.