Module 5 - Configure VNet Peering Flashcards
Determine Gateway Transit and connectivity needs
Gateway transit allows peered virtual networks to share the gateway and get access to resources
No VPN gateway is required in the peered spoke network
Default VNet peering provides full connectivity
IP address spaces of connected networks cant overlap.
UDR -
Create VNet Peering
Allow virtual access settings
Configure forwarded traffic settings
2 peering links must be created and show in connected status
Determine service chaining uses
Leverage user defined routes and service chaining to implement custom routing
Implement a VNet hub with network virtual appliance or VPN gateway
Service Chaining enables you to direct traffic from one virtual network to a virtual appliance , or virtual network gateway , in a peered virtual network , through user defined routes
Configure Network Routing and endpoints Introduction
Review systems routes
Identify user defined routes
Review System Routes
Directs network traffic between virtual machines , on prem networks , and the internet.
System routes is used when:
Traffic between VMs in the same subnet
Between VMs in different subnets in the same virtual network
data flow from VMs to the internet
Communication between VMs using a VNet To VNet VPN
Site to Site and expressRoute communication through the VPN gateway.
VPN is needed only when you trying to connect VNets that are from your on on prem to azure , AWS , and other cloud providers
Identify User defined Routes
A route table contains a set of rules called routes , that specifies how packets should be routed in a virtual network
User defined routes are custom routes that specify the next hop of traffic flow
The next hop can be a virtual network , gateway , internet or virtual appliance.
Review https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview#system-routes to see how azure routes the traffic
Determine VNet Peering
Two types of peering : global and regional
