Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Retrieve information
Create or submit data
Update or replace a resource
Remove a resource
Question 948 of 1,389
CCNA GET retrieves data without side effects Practice Question
Match each REST-style method to the most common intent.
⚠ Common exam trap
The exam tests your understanding of the specific intent of each HTTP method. Common traps include confusing GET with POST for creation, or PUT with PATCH for updates. Remember: GET is read-only, POST creates, PUT replaces, PATCH modifies partially.
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 a resource
RESTful methods map to CRUD operations: GET retrieves, POST creates, PUT replaces, PATCH partially updates, DELETE removes, and OPTIONS returns allowed 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 a resource
Why this is correct
GET is the proper HTTP method for retrieving a resource because it is defined as safe and idempotent, meaning it produces no side effects on the server and can be repeated safely. The request is sent without a body, and the server returns the current state of the resource identified by the URI. GET responses are cacheable, which is essential for efficient network operations. This aligns with the REST architectural constraint of using standardized methods for their intended semantic purpose.
- ✗
GET - Create a new resource
Why it's wrong here
GET is explicitly designed for safe retrieval, and its use for creation is incorrect because GET requests must not cause any side effects on the server—clients, proxies, and caches assume they are read-only. Creating a resource via GET would break the uniform contract of HTTP, leading to problems such as unintended resource creation from link prefetching, browser history, or web crawlers. Additionally, GET requests are not intended to carry complex payloads for entity creation; POST is the standard method for transmitting data that results in a new resource. RESTful APIs should rely on POST (and sometimes PUT) for creation semantics.
When this WOULD be correct
If the question asked 'Which HTTP method is used to retrieve a resource?' then 'GET - Retrieve a resource' would be correct. Alternatively, if the question was about a non-standard API that uses GET for creation (which violates REST principles), but this is not typical for the exam.
- ✗
POST - Retrieve a resource
Why it's wrong here
POST is defined for submitting data to be processed, typically resulting in the creation of a new resource or the triggering of a server-side action. Unlike GET, POST is neither safe nor idempotent, as each invocation can produce different outcomes or side effects. Using POST to merely retrieve a resource would violate the uniform interface principle of REST, because the server would need to interpret the request as a retrieval despite the method's established semantics. The correct retrieval method is always GET, which is explicitly designed for read-only operations.
When this WOULD be correct
If the question asked 'Which method is used to submit data to create a new resource?', then POST would be correct.
- ✗
PUT - Partially update a resource
Why it's wrong here
PUT is intended to replace the entire representation of a target resource with the request payload, making it an idempotent operation—repeated identical PUT requests yield the same state. A partial update is specifically handled by PATCH, which applies a set of changes described in the request body without replacing the whole resource. Therefore, using PUT for a partial update misrepresents the method's semantics and can lead to unintended data loss if the full representation is not supplied. The distinction between PUT and PATCH is critical in RESTful API design.
When this WOULD be correct
In a question asking 'Which HTTP method is used to replace an entire resource?' or 'Which method is idempotent and updates a resource by sending a complete representation?', PUT would be 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 a resourceCorrect answer▾
Why this is correct
GET is the proper HTTP method for retrieving a resource because it is defined as safe and idempotent, meaning it produces no side effects on the server and can be repeated safely. The request is sent without a body, and the server returns the current state of the resource identified by the URI. GET responses are cacheable, which is essential for efficient network operations. This aligns with the REST architectural constraint of using standardized methods for their intended semantic purpose.
✗GET - Create a new resourceWrong answer — click to see why▾
Why this is wrong here
In REST, GET is defined as a safe, idempotent method used only for retrieving resources, not for creating them. Creating a new resource requires POST or PUT.
★ When this WOULD be the correct answer
If the question asked 'Which HTTP method is used to retrieve a resource?' then 'GET - Retrieve a resource' would be correct. Alternatively, if the question was about a non-standard API that uses GET for creation (which violates REST principles), but this is not typical for the exam.
Why candidates choose this
Candidates may confuse GET with POST because they know both can send data, or they might think 'GET' can create resources if the server processes query parameters to create something, which is a common misconception.
✗POST - Retrieve a resourceWrong answer — click to see why▾
Why this is wrong here
POST is used to create a new resource, not retrieve one. The HTTP method for retrieval is GET.
★ When this WOULD be the correct answer
If the question asked 'Which method is used to submit data to create a new resource?', then POST would be correct.
Why candidates choose this
Candidates may confuse POST with GET because both can send data, but they forget that POST is for creation/submission, not retrieval.
✗PUT - Partially update a resourceWrong answer — click to see why▾
Why this is wrong here
PUT is used to fully replace a resource, not partially update. PATCH is the correct method for partial updates.
★ When this WOULD be the correct answer
In a question asking 'Which HTTP method is used to replace an entire resource?' or 'Which method is idempotent and updates a resource by sending a complete representation?', PUT would be correct.
Why candidates choose this
Candidates may confuse PUT with PATCH, or think 'update' broadly applies to PUT, overlooking the 'partial' distinction.
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?”
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: Apr 12, 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.