Cloud Networking for Network Engineers
Cloud networking is how virtual networks are built in AWS, Azure or Google Cloud. It includes VPCs or VNets with subnets and route tables, peering and transit gateways, load balancers, CDNs and managed DNS, which replace physical gear with API-defined resources.
Stage: Cloud and Modern Networking · Part of the Network Engineer roadmap · Last reviewed 19 November 2026
What to learn in Cloud Networking
- Create a VPC with public and private subnets and route tables
- Explain how NAT gateways let private instances reach the internet
- Connect two VPCs using peering and note its non-transitive nature
- Choose between Layer 4 and Layer 7 load balancers
- Describe how a CDN and DNS routing improve latency
Cloud Networking interview questions
What makes a subnet public in AWS?
A subnet is public when its route table has a route to an internet gateway and instances have public IPs. A private subnet lacks that route and reaches the internet, if at all, through a NAT gateway.
Why is VPC peering described as non-transitive?
If VPC A peers with B and B peers with C, A cannot reach C through B. Each pair needs its own peering, which is why transit gateways are used when many networks must interconnect.
Where Cloud Networking fits in the Network Engineer roadmap
Cloud Networking belongs to the Cloud and Modern Networking stage (beginner level), which takes about 5 hours. Hybrid reality.
Other units in this stage
Back to the full Network Engineer roadmap