ITForMe Beta Sign in
CCNA 200-301 v1.1 Automation and programmability Runs in your browser · no setup Original practice · Review pending

Validate an automated interface change

Inspect a REST request and JSON response before approving a bounded network automation run.

Estimated12 min
DifficultyIntermediate
Points7
Scenario brief

A dry run will update one lab interface. Review the request and response contract without sending traffic to a real controller.

Content record

Original practice · Review pending

Mapped to Cisco 200-301 objectives · Internal validation 2026-09-30 · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.

Community review →
6.5Describe characteristics of REST-based APIs. 6.7Recognize components of JSON-encoded data. 6.1Explain how automation affects network management.
Show review record and official sources

Method: Clean-room scenario and answer key checked against CCNA v1.1 objectives 6.5 and 6.7; independent SME review remains pending.

Current-profile check: 2026-08-12 · Next review due 2027-02-02

01

Inspect the evidence

Use only the information provided to complete the tasks.

Dry-run exchange

code
PATCH /interfaces/GigabitEthernet1 HTTP/1.1
Content-Type: application/json

{"enabled":true,"description":"Branch uplink"}

HTTP/1.1 200 OK
{"name":"GigabitEthernet1","enabled":true}
02

Complete the response

Partial credit is available for matching, ordering, and multi-select tasks.

Changes will save automatically.
01
multi select

Select the THREE observations supported by the exchange.

3 pts
Need a hint?

Evaluate each option independently against the scenario evidence instead of treating the list as one decision.

Show another hint

Choose only options that directly satisfy the prompt; being generally true is not enough.

02
ordering

Order the controlled automation workflow.

4 pts

Drag the rows or use the arrow buttons to reorder.

  1. 1 Capture current state and intended scope
  2. 2 Validate the payload in a dry run
  3. 3 Apply to the single approved interface
  4. 4 Read back state and test connectivity
Need a hint?

Identify the prerequisite that must happen first and the verification or documentation that belongs last.

Show another hint

For the middle steps, ask what must already be true before each action can safely happen.

Ready to check your work?Unanswered tasks and matches earn no points. A partial submission is scored and saved in your history.
Persistent progress

Attempt history

Every submission is retained. Starting another attempt never replaces or unlocks the previous one.

No attempts yet

Your first submitted score and detailed answer review will appear here.

Community quality control

Question or answer look wrong?

Proposals and votes help staff prioritize review. They never change the scoring key automatically.

Full review queue →
No community corrections yet

Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.

Propose a correction