Traffic for Cloud Engineers
Traffic management is how user requests reach healthy servers. DNS translates names to addresses, and load balancers distribute connections across instances using health checks, working at layer 4 for TCP or layer 7 for HTTP. Together they provide a stable entry point, high availability and the ability to scale out.
Stage: Networking · Part of the Cloud Engineer roadmap · Last reviewed 19 November 2026
What to learn in Traffic
- Create DNS records of type A, CNAME and MX and explain their roles
- Configure a load balancer with a health check endpoint
- Choose between a layer 4 and a layer 7 load balancer
- Set up HTTPS termination with a managed certificate
- Use weighted or failover DNS routing for a simple recovery plan
Traffic interview questions
What is the difference between a layer 4 and layer 7 load balancer?
A layer 4 balancer routes by IP address and port without reading the content, which is fast and protocol agnostic. A layer 7 balancer understands HTTP, so it can route by host or path, terminate TLS and modify headers.
What is the purpose of a health check?
A health check periodically probes each backend, often an HTTP path, and marks failing instances as unhealthy so the load balancer stops sending them traffic. It lets the system route around failures automatically.
Where Traffic fits in the Cloud Engineer roadmap
Traffic belongs to the Networking stage (intermediate level), which takes about 30 hours. Connect it.
Other units in this stage
Back to the full Cloud Engineer roadmap