Explain how you would design network connectivity between 40 VPCs/VNets and an on-premises data center.
Short answer
Use a hub-and-spoke topology with a transit hub (AWS Transit Gateway or Cloud WAN, Azure Virtual WAN or hub VNet, GCP Network Connectivity Center or Shared VPC), a non-overlapping IP plan, centralized inspection and egress, hybrid connectivity via dedicated links plus VPN backup, private DNS resolution in both directions, and segmentation through route tables.
Detailed answer
flowchart TB ONP[On-premises DC] -- Direct Connect / ExpressRoute / Interconnect + VPN backup --> HUB[Transit hub] HUB --> INSP[Inspection: firewalls] HUB --> EG[Central egress / NAT] HUB --> P1[Prod spokes] HUB --> P2[Non-prod spokes] HUB --> SH[Shared services: DNS, AD, tooling]
Segmentation: separate route tables so non-prod cannot reach prod; inspection for north-south and selected east-west traffic; hybrid DNS resolvers.
What the interviewer expects
Scalable topology, IP planning, security inspection and DNS.
Common mistakes to avoid
VPC peering mesh at scale, overlapping CIDRs, ignoring DNS.