Continue your lesson
Tie every forwarding decision to interface state, Layer 2 state, addressing, routing, and policy.
Block 1 of 1Compare HTTP GET · HTTP POST · HTTP PUT · HTTP DELETE
Current · 3 min
Compare HTTP GET · HTTP POST · HTTP PUT · HTTP DELETE
Optional concept notes
HTTP GET
Retrieves a resource representation without requesting a state change.
HTTP POST
Submits data for processing or creates a subordinate resource.
HTTP PUT
Creates or replaces the state at a specified resource URI.
HTTP DELETE
Requests removal of the resource identified by a URI.
Complete one provider lesson, then answer four related questions. That is enough for today; more practice is optional.
Your lesson stays open here while the provider opens in another tab. Choose one source; the notes above are optional.
Practice the reasoning here
Write or inspect a small Cisco configuration, name the expected show-command evidence, and explain how a frame or packet crosses it.
- State the expected result before changing or testing anything.
- Name the observation, command, log, or report that would confirm it.
- Explain why the closest alternative does not fit the same requirement.
Check the whole objective
This unlocks objective 6.5 for recall. The latest checkpoint needs 70% or higher; a lower result puts the lesson back near the front of your timeline.