Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Retrieve existing information
Submit or create data
Update or replace an existing resource
Remove a resource
CCNA AI and Network Operations Practice Question
Match each HTTP method to the most accurate action it commonly represents in REST-style APIs.
⚠ Common exam trap
The trap is assuming GET can perform any operation beyond retrieval. Remember that GET must be safe and idempotent; it should never modify or delete resources. Always associate GET with read-only operations.
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 from a resource
HTTP methods correspond to CRUD operations in REST: GET for read, POST for create, PUT for full update, PATCH for partial update, DELETE for delete, and HEAD for headers only.
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 from a resource
Why this is correct
GET is a safe and idempotent HTTP method defined by RFC 9110, meaning it must not alter server state and returns a representation of a specified resource. In RESTful CRUD operations, this maps directly to the read operation, allowing clients to fetch data without side effects. Repeating the same GET request yields the same result, confirming its read-only nature.
- ✗
GET: Create a new resource
Why it's wrong here
Creating a new resource involves submitting a payload to the server, which GET cannot carry reliably since its parameters are typically limited to the URL and it is defined as a safe method. The POST method is designed for creating resources, sending data in the request body and returning a 201 Created status. If GET were used for creation, it would break safety guarantees, and any intermediate proxy or browser preloader could unknowingly execute the operation.
When this WOULD be correct
If the question asked 'Which HTTP method is used to retrieve a representation of a resource?' then GET would be correct, but the action 'Create a new resource' is incorrect for GET.
- ✗
GET: Update an existing resource
Why it's wrong here
Updating a resource changes its state, which contradicts GET's mandatory safety constraint that forbids side effects. The PUT method replaces an entire resource, while PATCH applies partial modifications, both explicitly supporting request bodies and state changes. Using GET to update resources is non-conformant, and because GET requests should be idempotent and cacheable, such misuse would lead to unintended repeated updates and caching anomalies.
When this WOULD be correct
In a question asking about HTTP methods for a non-RESTful API or a poorly designed system, or if the question specifically asks for the method used to send update data via query parameters (though this is not standard REST).
- ✗
GET: Delete a resource
Why it's wrong here
Deleting a resource requires state-changing semantics that GET explicitly lacks, as GET requests are meant to be safe and require no server-side modifications. The DELETE method is the correct HTTP verb for removal, offering explicit intent and idempotency. Using GET to delete a resource violates RFC 9110 and can be accidentally triggered by prefetching, cache warmers, or automated link checkers, leading to data loss.
When this WOULD be correct
If the question asked about a non-standard or legacy API where a GET request with a specific query parameter (e.g., ?action=delete) triggers deletion, or in a poorly designed API that misuses HTTP methods, then GET could be associated with deletion.
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 data from a resourceCorrect answer▾
Why this is correct
GET is a safe and idempotent HTTP method defined by RFC 9110, meaning it must not alter server state and returns a representation of a specified resource. In RESTful CRUD operations, this maps directly to the read operation, allowing clients to fetch data without side effects. Repeating the same GET request yields the same result, confirming its read-only nature.
✗GET: Create a new resourceWrong answer — click to see why▾
Why this is wrong here
GET is defined as a safe, idempotent method for retrieving data, not for creating resources. The POST method is used for creation.
★ When this WOULD be the correct answer
If the question asked 'Which HTTP method is used to retrieve a representation of a resource?' then GET would be correct, but the action 'Create a new resource' is incorrect for GET.
Why candidates choose this
Candidates may confuse GET with POST due to common misuse in web forms where GET is sometimes used to submit data, or they may not clearly distinguish between HTTP method semantics.
✗GET: Update an existing resourceWrong answer — click to see why▾
Why this is wrong here
The GET method is defined as safe and idempotent in HTTP, meaning it should not modify server state. Using GET to update a resource would violate REST principles and HTTP semantics.
★ When this WOULD be the correct answer
In a question asking about HTTP methods for a non-RESTful API or a poorly designed system, or if the question specifically asks for the method used to send update data via query parameters (though this is not standard REST).
Why candidates choose this
Candidates may confuse GET with POST or PUT, or think that sending data in the URL (e.g., /resource?update=value) constitutes an update, overlooking the semantic meaning of HTTP methods.
✗GET: Delete a resourceWrong answer — click to see why▾
Why this is wrong here
In REST APIs, the GET method is defined as safe and idempotent, meaning it should only retrieve data without side effects. Using GET to delete a resource violates HTTP semantics and REST principles.
★ When this WOULD be the correct answer
If the question asked about a non-standard or legacy API where a GET request with a specific query parameter (e.g., ?action=delete) triggers deletion, or in a poorly designed API that misuses HTTP methods, then GET could be associated with deletion.
Why candidates choose this
Candidates may confuse the action with the method if they have seen APIs that use GET for deletion via query parameters, or they may not fully understand the standard HTTP method semantics and think any action can be performed with any method.
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.