This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A switching question asks about a VLAN, a trunk, a blocked port, or a bundle. Answer with VLAN ids and a story you are allowed to tell. This page does not name a browser tool. The pillar links the design tools. You explain the rule.
Say which port blocks and why. Say that a trunk does not carry every VLAN unless you made that mistake. If you do not know the platform's default, say so.
This is practice. It is not a vendor exam. You do not reconfigure a switch to demonstrate the answer.
One question. One closet, real or a lab you invent without using someone else's names.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Read one question.
- Name the VLAN or the port.
- Say the rule.
- Do not use a network you should not describe.
- Do not change a switch.
- Stop.
Mistakes that outlive the command
Switching Interview Questions goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A customer closet you should not share.
- A certification claim.
- Every VLAN allowed in the answer by habit.
- Reconfiguring a switch.
- Two features in one answer.
Decisions to write down
One decision for Switching Interview Questions: The example is yours or invented. The rule is named. This is not a certification. No switch was changed. And one question is the scope.
Checks before you call it done
Confirm this before you call the change done: The question is written. The rule is written. No foreign closet was described. No switch was changed. And the page is labeled practice. If one of those fails, stop.
Before you leave the device
Switching Interview Questions ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
This guide does not name a browser tool. The pillar it belongs to links the calculators for the neighbouring work.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.