CompTIA Exam Prep - ITF+, A+, Network+, Security+, CySA+

Accurate time is infrastructure nobody thinks about until it breaks. When it does, certificates fail validation, Kerberos refuses tickets, log correlation becomes impossible, and distributed databases disagree about the order of events. NTP is good enough for most of that. PTP exists for the cases where it is not. NTP Versus PTP NTP typically holds a network to within a few milliseconds over a WAN, and under a millisecond on a good LAN. It is simple, resilient, and universally supported. PTP, defined in IEEE 1588, reaches sub-microsecond and often nanosecond accuracy. It achieves that not through a cleverer algorithm but by moving timestamping into hardware and making the network itself participate. The distinction the exam cares about: NTP is software-timestamped and tolerates an ordinary network; PTP needs hardware support in the switches to deliver its headline accuracy. Why Software Timestamping Is Not Enough When NTP records a departure time in software, the packet s...

A client with no address cannot send a directed packet, so DHCP discovery is a broadcast. Routers do not forward broadcasts. Put the DHCP server on a different subnet from the client and, without help, the two can never speak. A relay agent is the help. It is the reason a single DHCP server can serve an entire campus instead of one per VLAN. What the Relay Actually Does The relay agent — almost always the router or layer 3 switch acting as the client's default gateway — listens for DHCP broadcasts on its interface. When one arrives it does three things: Converts the broadcast into a unicast addressed to the configured DHCP server. Writes its own interface address into the giaddr field of the DHCP packet. Forwards it. That third step is the interesting one. The giaddr field is how the server knows which subnet the request came from, and therefore which scope to allocate from. Without it the server would see only its own subnet and have no idea what to offer. ...

Both carry signals on a copper conductor inside a shield, and there the resemblance ends. Coaxial has one centre conductor and carries an unbalanced signal. Twinaxial has two, carrying a balanced differential pair. That single structural difference determines everything about where each is used. Coaxial One centre conductor, a dielectric insulator, a braided shield, an outer jacket. The shield serves as both the return path and the protection against interference. The types worth knowing: RG-6 — cable television and satellite, and the cable-internet drop into a home. 75 ohm, F-type connector. RG-59 — thinner, higher loss, legacy analog video and CCTV. Also 75 ohm. RG-58 — 50 ohm, used by legacy 10BASE2 Ethernet with BNC connectors. Historical, and still examinable. Impedance matters: 75 ohm for video and broadband, 50 ohm for radio and legacy Ethernet. Mixing them causes reflections and signal loss, and it is a standard exam distinction. Twinaxial ...

MPLS forwards packets by a short fixed-length label rather than by looking up a destination address. The label is decided once, at the edge, and every device after that makes a simple lookup in a much smaller table. It is frequently called a layer 2.5 protocol, because the label sits between the layer 2 header and the layer 3 packet. That is a useful way to remember where it lives, though the real point is that MPLS is indifferent to what it carries. How a Packet Moves Two device roles: LER (Label Edge Router) sits at the boundary. The ingress LER classifies an incoming packet, decides its path, and pushes a label. The egress LER pops the label and forwards the packet normally. LSR (Label Switch Router) sits in the core. It reads the incoming label, swaps it for the outgoing one, and forwards. It never inspects the IP header. The path a labelled packet follows is a Label Switched Path , and it is unidirectional — return traffic takes its own LSP, which may be a diff...

Quality of Service does not create bandwidth. It decides who suffers when there is not enough. Every QoS design is a statement about which traffic the business is willing to drop or delay, and the technical machinery exists only to carry out that decision reliably. What Traffic Actually Needs Three measurements, and different applications care about different ones: Bandwidth — how much capacity. A file transfer wants a lot and does not care when it gets it. Latency — one-way delay. Voice needs under about 150 milliseconds before conversation becomes awkward. Jitter — variation in latency. Voice and video tolerate a consistent delay far better than an inconsistent one, because a jitter buffer can absorb the former. Loss matters too, but differently: a retransmitted file is fine, a retransmitted voice packet is useless because it arrives after its moment. The Four Steps Classification identifies traffic — by port, protocol, source, or deep inspe...