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
CCNA Network Services and Security Practice Question
Match each HTTP method to its common REST API action.
⚠ Common exam trap
Be careful not to confuse PUT (full replacement) with PATCH (partial update). Also, remember that GET is read-only and should not create or modify data.
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 data
GET retrieves data; POST creates; PUT replaces; PATCH partially updates; DELETE removes; OPTIONS queries available methods.
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 data
Why this is correct
GET is an HTTP method that requests a representation of the specified resource without modifying server state. It is both safe and idempotent, meaning repeated identical GET requests yield the same result and cause no side effects. In REST APIs, GET is the standard operation for read-only retrieval, typically returning a 200 OK response with the resource body.
- ✗
GET - Create data
Why it's wrong here
GET is not designed for creation because it is a safe, read-only operation that must not alter server state or trigger side effects. Creating data requires sending a request payload and invoking server-side processing, which is the semantic role of POST. Using GET to create resources violates HTTP constraints, leading to problems such as unintended cacheable state changes and vulnerability to cross-site request forgery.
When this WOULD be correct
This option would be correct if the question asked about a non-standard or custom API where GET is used to create a resource (e.g., a legacy system or a poorly designed API that uses GET for creation).
- ✗
POST - Retrieve data
Why it's wrong here
POST is not intended for retrieval because it is designed to submit data to a specified resource for processing, typically causing state changes or resource creation. Retrieval is a read-only operation that should use GET, which is safe and idempotent. Although POST can return data in a response, its primary semantic is server-side processing rather than querying existing resources.
When this WOULD be correct
If the question asked 'Which HTTP method is used to submit data to a server for processing, often resulting in the retrieval of a representation of the result?', then POST would be correct for actions like submitting a search query that returns results.
- ✗
PUT - Partially update data
Why it's wrong here
PUT is defined to replace an entire resource with the representation in the request body, making it inappropriate for partial updates. A partial update modifies only a subset of a resource's fields, which is the purpose of the PATCH method. Because PUT is idempotent and requires the complete new state, applying it to a partial payload would cause missing fields to be reset or removed.
When this WOULD be correct
In a question asking 'Which HTTP method is used to fully update an existing resource?', PUT would be the correct answer, as it replaces the entire resource with the provided representation.
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 dataCorrect answer▾
Why this is correct
GET is an HTTP method that requests a representation of the specified resource without modifying server state. It is both safe and idempotent, meaning repeated identical GET requests yield the same result and cause no side effects. In REST APIs, GET is the standard operation for read-only retrieval, typically returning a 200 OK response with the resource body.
✗GET - Create dataWrong answer — click to see why▾
Why this is wrong here
In REST APIs, GET is defined as a safe and idempotent method used only for retrieving data, not creating it. Creating data is the responsibility of POST or PUT.
★ When this WOULD be the correct answer
This option would be correct if the question asked about a non-standard or custom API where GET is used to create a resource (e.g., a legacy system or a poorly designed API that uses GET for creation).
Why candidates choose this
Candidates may confuse HTTP methods due to lack of practice or mistakenly think GET can create data because they have seen GET requests with query parameters that trigger server-side actions.
✗POST - Retrieve dataWrong answer — click to see why▾
Why this is wrong here
In REST APIs, POST is used to create data, not retrieve it. The GET method is specifically designed for retrieving resources without side effects.
★ When this WOULD be the correct answer
If the question asked 'Which HTTP method is used to submit data to a server for processing, often resulting in the retrieval of a representation of the result?', then POST would be correct for actions like submitting a search query that returns results.
Why candidates choose this
Candidates may confuse POST with GET when they think of 'posting' a request to retrieve data, or they might recall that POST can return a response body, leading them to incorrectly associate it with retrieval.
✗PUT - Partially update dataWrong answer — click to see why▾
Why this is wrong here
PUT is used for full replacement of a resource, not partial updates. PATCH is the correct HTTP method for partial updates in REST APIs.
★ When this WOULD be the correct answer
In a question asking 'Which HTTP method is used to fully update an existing resource?', PUT would be the correct answer, as it replaces the entire resource with the provided representation.
Why candidates choose this
Candidates may confuse PUT with PATCH, especially if they have experience with APIs where PUT is used for updates without distinguishing between full and partial updates.
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
Learn chapter
Diagnosing DNS Record Issues — A, AAAA, CNAME, MX, NS, and PTR Records
Key term
API
An API is a set of rules that allows software applications to communicate and exchange data with each other.
Key term
HTTP
HTTP stands for Hypertext Transfer Protocol, the set of rules web browsers and servers use to communicate and transfer web pages over the internet.
About these practice questions
Courseiva writes every 200-301 question from scratch — 1,389 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.