
ACLs: order, match, action and the implicit deny
The first matching entry decides the packet; everything unmatched hits an implicit deny.
Protocols, routing, VLANs and network infrastructure.

The first matching entry decides the packet; everything unmatched hits an implicit deny.

What an AI assistant may do in network operations, and the approval a change still needs.

A play can declare the end state; getting the device there is the other half of the job.

Policy filters first; attributes only rank the routes that policy already allowed.

Over SSH a CLI is text: why its output is untrusted and where the credential lives.

Three states, not two: measuring how far a network drifted from what you declared.

An archive answers what changed and why; only the device says what is running now.

A declared schema and a screen of text are different promises to the caller.

A DMZ does not make a service safe; it adds a second boundary before the inside network.

Who may answer a name, and how the answer is proven genuine before anything acts on it.

A static route never notices a failure; a routing protocol lets routers repair the path.

The outbound direction is rarely filtered, and that is where a compromised host escapes.

A firewall policy sets intent; an ACL is the mechanism that carries it onto the device.

One gateway address held by two routers: what redundancy covers, and what it does not.

An IPS blocks, an IDS cannot; placement decides the view, and an alert is not a verdict.

Three mechanisms, three failures: address scopes, neighbour discovery and dual stack.

Each source of network evidence answers one question well, and leaves the rest open.

An estate is multi-site when its parts fail alone: name the unit of failure first.

Group delivery and traffic treatment pay off only where a link or a fan-out is saturated.

NAT and PAT rewrite a packet header; the filtering is a side effect of that state.

How flow telemetry turns packets into records, and what a record can and cannot show.

An adjacency, an area and a metric together decide which links a router sees.

Where a capture is taken, and how much of each packet it keeps, decide what it can prove.

A change needs proof it can apply, proof it is in use, and a prepared way back.

A network reply becomes a decision only after a gate decides whether it can be trusted.

Convergence has phases, and the network design decides which one dominates.

Scalability is a set of axes; each breaks for its own reason, at its own size.

Centralising control moves the decision, not the packet, and buys reach as well as risk.

A VLAN draws the segment; only an enforcement point decides what may cross it.

A tunnel protects the path, not the endpoint: the device at the far end is unverified.

Polling is a pull the manager starts; a trap or an inform is a push the agent starts.

Hierarchy is what lets prefixes aggregate; a flat address plan cannot be summarised.

Severity steers handling; it never certifies that the claimed event occurred.

An inventory says which devices, variables say what, and precedence decides who wins.

The shortest path ignores load and capacity; steering traffic around it is not free.

A tunnel joins two points; an estate needs a topology, and that topology is the design.

How VXLAN wraps an Ethernet frame in UDP and how EVPN replaces flooding with routes.

What an access port and a trunk port each carry, how untagged and IEEE 802.1Q-tagged traffic differ on a trunk, and how to configure and verify both on Cisco IOS XE.

Why IPv4 ARP and IPv6 Neighbor Discovery map a layer-3 address to a layer-2 address on the local link, what each protocol actually does, and where their trust model breaks.

What each basic network tool really answers, how to read its result, and the conclusions it does not support.

How a DHCP server is scoped to a subnet, how leases and reservations decide which address a client gets, and how a relay agent lets one server serve other segments.

What DNS and DHCP each solve, how resolution and address assignment actually work, and why both are unauthenticated by default.

How the common DNS record types answer different questions, how a resolver walks the delegations to the authoritative server that owns a name, and how a Cisco IOS-XE device resolves and serves names.

What an Ethernet frame carries, what a MAC address identifies, and how a switch builds the table it forwards from.

What ICMP does inside IP, how TCP and UDP differ, and why a port identifies a process rather than a trusted service.

Why two VLANs cannot reach each other at Layer 2, and how one Layer-3 interface per VLAN — a router subinterface or a switch SVI — routes traffic between them.

How an address splits into a prefix and a host part, why a prefix boundary can fall inside an octet, and what the default gateway actually does in IPv4 and IPv6.

How link aggregation bundles parallel links into one logical interface, what LACP negotiates before the bundle is used, and why one flow still moves at one link speed.

What the native VLAN means on an 802.1Q trunk, how untagged traffic is classified, and why the choice affects spanning tree and segmentation.

Four devices, four different decisions: the information each one uses, the scope it applies in, and why "which layer it is" is the wrong question.

How NTP keeps network devices on the same clock - the server hierarchy, the round-trip measurement, and why unauthenticated time is a risk.

Why the layered models exist, what each layer adds to a packet, and where OSI and TCP/IP differ.

How a switch port powers a device over the cable (PoE) and how both ends agree on speed and duplex — and the Cisco IOS-XE commands used to inspect and control them.

What a routing table entry contains, how a device picks the longest matching prefix and its next hop, and what the default gateway and the default route actually are.

How a static route and a default route are written on Cisco IOS-XE, how the router chooses between routes, and when a manually configured route fails silently.

Why a Layer 2 loop becomes a broadcast storm, how STP elects a root and blocks the ports that would close a loop, and how to configure and verify it on Cisco IOS-XE.

How a Cisco IOS-XE switch stores what it has learned, how to read, populate, age and clear the MAC address table, and what its entries actually tell you about a Layer 2 network.

How unicast, broadcast and multicast address traffic, why IPv6 dropped broadcast, and why the size of a broadcast domain is an operational problem.

How IEEE 802.1Q lets a single link carry many VLANs — the 4-byte tag, access and trunk ports, and the native VLAN.