Network Operations and Design
The parts of the job that are not configuration - how networks are shaped, what runs them, how they are watched, and what happens when they are automated or lost.
By the end you will be able to
- Match a design shape to the problem it was built to solve
- Explain what each form of virtualization actually isolates
- Read a syslog severity and an SNMP version and act on what you see
- Describe what automation changes about operations, including the risks
- State a recovery objective and choose a design that meets it
Sign in to track your progress, earn XP and unlock the labs in this path.
Modules
- 01
Shapes, Virtualization and the Physical World
How networks are arranged and what they run on - including the one subject this platform cannot demonstrate and says so.
5 activities~45 min - 02
Watching the Network, and Moving Files Around It
How you find out something is wrong without being told, and how configurations and images get on and off a device.
3 activities~38 min - 03
Process, Documentation and Recovery
Most outages are caused by changes, and most recovery plans have never been tested. Both of those are addressable.
3 activities~25 min - 04
Automation and Programmability
What changes when configuration stops being typed - the planes, the controller, the API, and the architectures built on top.
5 activities~47 min - 05
Diagnosis in Practice
The method from the very first module, now that you know every tool it can reach for - and four faults from four domains to apply it to.
3 activities~109 min
Curriculum topics
Each topic page lists every lesson, quiz and hands-on lab that covers it, plus how it maps onto the CCNA and Network+ blueprints.