CCNA AI and Network Operations Practice Question
A network engineer is reviewing REST API behavior. Which two statements are true?
⚠ Common exam trap
A common exam trap is misinterpreting the function of HTTP methods in REST APIs, such as believing DELETE encrypts data or PUT retrieves resource lists. DELETE actually removes resources, and PUT replaces or updates existing resources. Confusing POST and PUT is also frequent, where POST creates new resources while PUT replaces them. These misunderstandings can lead to incorrect answers or automation scripts that cause unintended network changes. The exam expects precise knowledge of REST API method purposes, especially in Cisco automation contexts.
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 is commonly used to retrieve information from an API
GET is used to retrieve data without changing server state, while POST commonly creates a new resource or submits data for processing. PUT is usually for full replacement, and DELETE removes a resource.
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 is commonly used to retrieve information from an API
Why this is correct
GET is the standard read method in REST APIs, designed to retrieve a representation of a resource without modifying server state. Because it is safe and idempotent, repeated identical GET requests produce the same result, making it the natural choice for queries. A successful GET commonly returns a 200 OK response with the requested payload.
- ✓
POST is commonly used to create a new resource
Why this is correct
POST is used to submit data to the server to create a new resource, especially when the client does not determine the URI. Unlike PUT, POST is non-idempotent, meaning identical POST requests can create multiple resources. A typical response is 201 Created, optionally including a Location header identifying the newly created resource.
- ✗
DELETE is used to encrypt a payload before transport
Why it's wrong here
DELETE is an HTTP method specifically intended to remove a specified resource from the server, not to secure data in transit. Encryption of payloads is handled by transport-layer protocols such as TLS, not by the HTTP method. While a DELETE request may return 200 OK or 204 No Content, it has no role in encrypting content before transmission.
When this WOULD be correct
If the question asked 'Which HTTP method is used to remove a resource from a server?' then DELETE would be correct.
- ✗
PUT always retrieves a list of resources
Why it's wrong here
PUT is designed to update or replace an existing resource at a specific URI, not to retrieve a list of resources. It is idempotent, meaning repeated PUT requests yield the same state, which is appropriate for full updates. Retrieving resources is the function of GET, so stating that PUT always retrieves a list conflates the distinct roles of these methods.
When this WOULD be correct
In a question asking about REST API methods for batch operations, if the API uses PUT to replace a collection of resources (e.g., PUT /items to replace the entire list), then PUT could be described as retrieving a list after replacement, but this is non-standard.
- ✗
GET requires a token in every API design
Why it's wrong here
Token-based authentication is a common API practice, but it is not a requirement of the HTTP GET method itself. Many APIs use API keys, basic authentication, or no authentication at all for public endpoints. The HTTP specification defines GET as a retrieve operation without mandating any particular authentication mechanism, so tokens are an implementation choice, not a universal rule.
When this WOULD be correct
In an exam scenario where the question states 'For a REST API that enforces token-based authentication for all endpoints, which statement about GET requests is true?', then 'GET requires a token' would be correct if the API design mandates tokens for all methods.
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 is commonly used to retrieve information from an APICorrect answer▾
Why this is correct
GET is the standard read method in REST APIs, designed to retrieve a representation of a resource without modifying server state. Because it is safe and idempotent, repeated identical GET requests produce the same result, making it the natural choice for queries. A successful GET commonly returns a 200 OK response with the requested payload.
✗DELETE is used to encrypt a payload before transportWrong answer — click to see why▾
Why this is wrong here
DELETE is an HTTP method used to delete a resource, not to encrypt payloads. Encryption is handled by protocols like TLS, not by HTTP methods.
★ When this WOULD be the correct answer
If the question asked 'Which HTTP method is used to remove a resource from a server?' then DELETE would be correct.
Why candidates choose this
Candidates may confuse DELETE with security functions, assuming it 'deletes' or 'hides' data through encryption, due to the word 'delete' being associated with removal or obscuring.
✗PUT always retrieves a list of resourcesWrong answer — click to see why▾
Why this is wrong here
PUT is used to update or replace a specific resource, not to retrieve a list of resources. Retrieving a list is typically done with GET.
★ When this WOULD be the correct answer
In a question asking about REST API methods for batch operations, if the API uses PUT to replace a collection of resources (e.g., PUT /items to replace the entire list), then PUT could be described as retrieving a list after replacement, but this is non-standard.
Why candidates choose this
Candidates may confuse PUT with GET due to similar sounding names or mistakenly think PUT can be used for retrieval in some designs.
✗GET requires a token in every API designWrong answer — click to see why▾
Why this is wrong here
GET does not require a token in every API design; authentication mechanisms like tokens are optional and depend on the API's security requirements.
★ When this WOULD be the correct answer
In an exam scenario where the question states 'For a REST API that enforces token-based authentication for all endpoints, which statement about GET requests is true?', then 'GET requires a token' would be correct if the API design mandates tokens for all methods.
Why candidates choose this
Candidates may assume that all REST APIs require authentication tokens because many real-world APIs (e.g., OAuth2) do, but it's not a universal requirement.
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
Agentic AI in Network Operations
Key term
API
An API is a set of rules that allows software applications to communicate and exchange data with each other.
Key term
REST API
A REST API is a set of rules that allows different software applications to communicate with each other over the internet using standard HTTP methods.
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.