Most outages that look like application bugs turn out to be network problems: a name that no longer resolves, a certificate that expired, a connection that times out. Networking is how every service in your stack reaches every other one, and a site reliability engineer needs to be able to reason about each hop a request takes.
You'll start with DNS, the system that turns a domain name into an IP address, and then look at HTTP, the request and response protocol that most of your services speak. From there the module covers TLS, which encrypts and authenticates those connections, and load balancers, which spread traffic across servers and keep a service available when one of them fails.
Once you can follow a request from the browser to a healthy server and back, you'll be ready for the next module, Scripting & Automation, where you start writing code to remove manual work.
A walkthrough of the Domain Name System: how a name is matched to an IP address, and how resolvers and name servers cooperate to answer the question.
How browsers and servers talk over HTTP, including the request and response cycle, common methods like GET and POST, and the meaning of status codes.
What TLS is, where it came from, and how it provides privacy, integrity, and authentication for connections across the internet.
An introduction to load balancers, how they distribute traffic across servers, and the main types you will meet in production.