1.1. The Network as Infrastructure

Imagine your network as a city's road system. Without roads, buildings are isolated islands—useful individually but unable to work together. Networks solve this fundamental problem: how do separate systems communicate?

💡 First Principle: Every network design decision balances three competing forces: connectivity (can things communicate?), isolation (can we prevent unwanted communication?), and performance (is communication fast enough?). Think of it like city planning—you want roads connecting neighborhoods (connectivity), but you also need private driveways and gated communities (isolation), all while avoiding traffic jams (performance).

What breaks without this understanding:

• You'll deploy everything in one giant VNet with no segmentation—then scramble when a security audit fails
• You'll create so many network controls that legitimate traffic can't flow
• You'll troubleshoot for hours because you don't know where packets actually go

Consider a typical scenario: your web servers need to reach a database, but the database should never be directly accessible from the internet. This single requirement involves all three forces—and the exam will test your ability to balance them.