<s:WWH/>PUBLIC BETA
WWH METHOD GROWING

WHAT. WHY. HOW.

A practical way to understand technology instead of memorising isolated facts. Start with what it is, understand why it matters, then learn how it actually works, fails and gets checked.

WHATWhat is it? What role does it play in the system?
WHYWhy does it exist, and why does it matter to users or administrators?
HOWHow does it work, how do you use it, and how do you verify it when something fails?
WWH IN ACTION

Technical concepts explained end to end.

The examples below show the intended learning style. The concept library is being expanded carefully rather than filled with shallow summaries.

DHCP

WHAT

Automatically supplies devices with IP configuration such as address, prefix, gateway and DNS settings.

WHY

Reduces manual configuration, mistakes and operational effort when devices join or move between networks.

HOW

A client and DHCP service negotiate configuration, commonly remembered as Discover → Offer → Request → Acknowledge.

DNS

WHAT

Maps names such as server01 or example.com to records applications can use, including IP addresses.

WHY

Users and applications depend on stable names even when underlying addresses or services change.

HOW

The client checks local knowledge and configured resolvers; the resolver answers from cache or follows DNS delegation until it can return an answer or an error.

HTTPS

WHAT

HTTP carried over a protected TLS connection.

WHY

It protects data in transit and lets the client authenticate the service identity represented by the certificate.

HOW

Name resolution and network reachability come first, then the client and server negotiate TLS before protected HTTP traffic is exchanged.

USE THE RIGHT SURFACE

Learn, reference, diagnose or calculate.

WWH pages have different jobs so you do not have to force every task into one interface.

CONCEPT LIBRARY

More walkthroughs are being added.

New topics are added when they can be explained clearly with useful WHAT, WHY and HOW depth.

Routing & packet pathHow a host decides where traffic goes and what happens across gateways.GROWING
Kerberos authenticationTickets, KDC roles, SPNs, time and the evidence behind common failures.GROWING
Group PolicyHow scope, processing, DC/DNS dependencies and client evidence fit together.GROWING
Intune enrollmentIdentity, enrollment, MDM authority, policy and client-side evidence.GROWING