A network automation script sends this HTTP request to a controller API:
POST /api/v1/devices
What does the POST method typically indicate in a RESTful API?
A network automation script sends this HTTP request to a controller API:
POST /api/v1/devices
What does the POST method typically indicate in a RESTful API?
Answer choices
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
It retrieves an existing resource without changing it
That describes GET, not POST. GET is normally used when a client wants to read information from the server without changing the resource. Learners sometimes remember that both are HTTP methods and stop there, but the exam expects you to match each method with its usual purpose.
It creates a new resource or submits data to be processed
Correct. This is correct. POST commonly creates a new resource or submits data to the API for processing. In automation questions, that usually means the script is asking the controller to add something or perform an action using the payload it sends.
It deletes the targeted resource permanently
DELETE is the method most commonly associated with removing a resource. POST does not typically indicate deletion. Choosing this option would confuse object creation/submission with object removal, which are separate actions in RESTful design.
It replaces the entire existing resource in an idempotent way
PUT is more closely associated with full replacement or idempotent update behavior. POST is not usually the answer when a question asks about idempotent full replacement of an existing resource.
Common exam trap
A frequent exam trap is mistaking POST for GET or PUT. Some candidates incorrectly believe POST retrieves data like GET or replaces resources idempotently like PUT. This confusion arises because all are HTTP methods, but their purposes differ significantly. POST is non-idempotent and used for creating or submitting data, so repeating a POST can cause multiple resource creations. Misunderstanding this can lead to incorrect answers and flawed automation scripts that unintentionally duplicate resources or trigger repeated actions. The exam expects you to clearly associate POST with creation or submission, not retrieval or idempotent replacement.
Technical deep dive
The POST method is a fundamental HTTP verb used in RESTful APIs to submit data to a server. Unlike GET, which only retrieves data, POST sends information that the server processes to create a new resource or perform an action. In the context of network automation and programmability, POST requests often carry JSON or XML payloads that instruct a network controller to add devices, configure settings, or trigger workflows. This method is essential for dynamic network management where automation scripts interact with APIs to modify network state. The decision to use POST versus other HTTP methods depends on the intended operation. GET is for safe, read-only retrievals; DELETE removes resources; PUT replaces resources idempotently. POST is unique because it is not idempotent—repeating the same POST can create multiple resources or cause repeated side effects. Cisco’s network automation APIs leverage POST to onboard devices or submit configuration changes, making it the go-to method for creating or submitting data rather than just reading or deleting. A common exam trap is confusing POST with GET or PUT. Learners may think POST is for retrieval or idempotent updates, but POST’s non-idempotent nature means it can cause multiple creations if repeated. In practical Cisco automation, understanding POST’s role prevents misusing API calls that could lead to duplicate devices or unintended actions. Recognizing POST as the method for create-or-submit operations aligns with Cisco’s controller API design and ensures accurate automation scripting and exam success.
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
Practise DHCP scopes, relay, leases and troubleshooting.
Practise routing-table output, longest-prefix match, AD and route selection.
Practise trunk verification and VLAN forwarding across switches.
Practise WLAN security, authentication and wireless architecture concepts.
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
Question 2
Question 3
Question 4
Question 5
Question 6
FAQ
The POST method in RESTful APIs submits data to the server to create a new resource or trigger processing actions.
The correct answer is: It creates a new resource or submits data to be processed — POST usually means the client is submitting information to create a new resource or asking the server to process the provided payload. In a controller-based networking context, that often means onboarding a device, creating an object, or starting a workflow. This question is testing method recognition rather than deep programming skill. GET is commonly used for retrieval, DELETE for removal, and PUT for full replacement or update behavior that is typically idempotent. POST is different because repeating the same POST can create multiple objects or trigger repeated actions, depending on the API design. For CCNA purposes, the plain-English takeaway is simple: POST is generally associated with create-or-submit behavior, not read-only retrieval.
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Sign in to join the discussion.