Az 104 session 6 azure networking part2

https://azureezy.com
© 2020 AzureEzy and AzureTalk. All rights reserved!
Session 6
AZ-104: Microsoft Azure
Administrator
1

AzureTalk Core Team
2

Today’s Session Speaker
Niraj Kumar
AzureTalk Founder
Enterprise Architect, MCT
3
Ashish Raj
AzureTalk Core Team
Member, DevOps Architect
Vipin Jha
AzureTalk Core Team
Member, Consultant, MCT

AZ-104 Skills Measured
• Manage Azure identities and governance (15-20%)
• Deploy and manage Azure compute resources (25-30%)
• Implement and manage storage (10-15%)
• Configure and manage virtual networking (30-35%)
• Monitor and back up Azure resources (10-15%)
4

AZ-104 Prerequisites
5
Understanding of
• Operating systems
• Virtualization
• Network configuration
• Active Directory
• Resilience and disaster recovery

Agenda
6
• Azure Load Balancer
• Azure Application Gateway
• Traffic Manager
• Azure DNS

Azure Load Balancer

Azure Load Balancer
8
• Azure Load Balancer
• Load Balancer concepts
• Load Balancer components
• Load Balancer SKUs

Azure Load Balancer
9
Endpoints
Load
Balancer
• Evenly distribute load across to backend
pool
• Single point of contact for clients
• Distributes inbound flows that arrive at
the load balancer's front end to backend
pool instances
• Flows as per load balancing rules and
health probes
• Backend pool
• Azure Virtual Machines
• virtual machine scale set
• Operates at layer 4 of OSI model

Load Balancer Types
10Reference : Microsoft Docs
• Public Load Balancer
• Frontend IP configuration Public IP
address
• Maps public IP and port of incoming
traffic to the private IP and port of
the VM
• Internal Load Balancer
• Frontend IP configuration Private IP
address
• Distributes traffic to resources that
are inside a virtual network

Load Balancer Components
11
• Frontend IP configuration Public / Private IP Address
• Backend pool
• Health probes
• Load Balancing rules
• High Availability Ports

Backend Pools
12
• VM or instances in a VMSS
• Adding or removing VMs from
the backend pool
reconfigures load balancer
without additional operations
• Scope is any VM in VNet based
on SKU

Health probes
13
• Health status of instances in backend pool
• Define unhealthy threshold
• Health probe types : TCP, HTTP, and HTTPS
• When a probe fails to respond, Load Balancer
stops sending new connections to the
unhealthy instances
• Probe failure doesn't affect existing
connections
• Connection continues until the application:
• Ends the flow
• Idle timeout occurs
• VM shuts down

Load Balancer Rules
14
• Define how incoming
traffic is distributed to
all instances within
Backend Pool
• Maps a given Frontend IP
configuration and port to
multiple backend IP
addresses and ports
Reference : Microsoft Docs

Inbound NAT rules
15
• Forwards incoming traffic
sent to Frontend IP
address and port
combination
• Traffic is sent to a specific
virtual machine or
instance in the backend
pool

Session Persistence
16
Internet

Session Persistence
17
Internet

Session Persistence
18
Internet
Connection 2

Load Balancer SKUs
19
Basic Load Balancer Standard Load Balancer
Backend pool Size Up to 300 instances Up to 1000 instances
Backend pool
endpoints
• VM in a single availability
Set
• virtual machine scale set
Any VM or virtual machine scale
sets in a single VNet
Health probes TCP, HTTP TCP, HTTP, HTTPS
Availability Zones Not available Zone-redundant and zonal
frontends for inbound and outbound
traffic
Secure by default Open by default, NSG
optional
• Closed to inbound flows unless
allowed by a NSG
• Internal traffic from VNet to
internal load balancer is allowed

Question 1
In Azure Load balancer health probes HTTPS is supported
in Both SKU Basic and Standard.
a) True
b) False
20
https://q.azureezy.com/1

Question 1
In Azure Load balancer health probes HTTPS is supported
in Both SKU Basic and Standard.
a) True
b) False
21

Azure Application Gateway

Application Gateway
23
• Manages the requests that client applications can
send to a web app
• Routes traffic to a pool of web servers
• Application layer routing
• Pool of web servers
• Azure virtual machines
• Azure virtual machine scale sets
• Azure App Service
• On-premises servers
• Public or Internal IP addresses
• FQDN

Application Gateway
24

Application Gateway Routing
25
Path-based routing
Send requests with
different paths in the URL
to a different back-end
pool

26
Multiple site hosting
• Register multiple DNS names
(CNAMEs) for the IP address of
the Application Gateway,
specifying the name of each
site
• Separate listeners to wait for
requests for each site
• Each listener passes the
request to a different rule
different back-end pool

27
Other Routing Capabilities
• Redirection: Used to another site
• Rewrite HTTP Headers: Allow client and server to pass
information with request or response
• Custom Error Pages: Own branding and layout

Question 2
Azure Application Gateway works at which layer of OSI
model?
a) Layer 2
b) Layer 3
c) Layer 4
d) Layer 7
28

Question 2
Azure Application Gateway works at which layer of OSI
model?
a) Layer 2
b) Layer 3
c) Layer 4
d) Layer 7
29

Traffic Manager

Traffic Manager
31
• DNS-based traffic load balancer
• Distribute traffic to services across global Azure regions
• High availability and responsiveness
• Use DNS to Direct client to endpoint based on routing
method & health
• Endpoint is Internet-facing service hosted inside or outside
of Azure
• Not a proxy or gateway
• Does not see traffic between client and service

How Client Connect
32Reference : Microsoft Docs

Priority Traffic Routing
33
• Sends all traffic to primary
(highest-priority) endpoint
• If primary endpoint is not
available, Traffic Manager
routes traffic to second
endpoint
• Endpoint availability is based
on configured status (enabled
or disabled)
• Lower values represent a
higher priority

Performance Traffic Routing
34
• Closest endpoint is not
measured by geographic
distance
• Closest endpoint measured
by network latency using
Internet Latency Table
• Lowest latency is high
performance

Weighted Traffic Routing
35
• Distribute traffic evenly
or to use a pre-defined
weighting
• Weight is an integer from
1 to 1000
• If omitted, Traffic
Managers uses a default
weight of '1’
• The higher weight, the
higher the priority

Geographic Traffic Routing
36
• Route traffic to specific endpoints
(Azure, External or Nested) based
on geographic location their DNS
query originates from
• Geographic region can be at
following levels
• World– any region
• Regional Grouping Africa, Middle
East
• Country/Region Ireland, Peru
• State/Province USA-California,
Australia-Queensland

Load balancing Decision
37
• Traffic type: Web (HTTP/HTTPS) application,
Public facing or Internal
• Global or regional: Load balance VMs or VMSS
within a VNet, or across regions, or both
• Availability: Service SLA
• Cost
• Features and limits

Azure DNS
39

Azure DNS
40
• Manage domains using Azure credentials
• Act as SOA for domain
• Can't use Azure DNS to register domain
• Domains can be hosted in Azure DNS for record
management

Azure DNS Benefits
41
• Improved Security : RBAC, Activity logs, Resource Lock
• Ease of use
• Manage DNS records for Azure services
• Provide DNS for external resources
• Use Azure credentials
• Azure portal, Azure PowerShell, Azure CLI, Integrate using REST
API & SDKs
• Private DNS domains
• Alias record sets
• Azure public IP address
• Azure Traffic Manager profile
• Azure Content Delivery Network endpoint

Azure Private DNS
42
• Name resolution for VMs within a VNet, & between VNet
• Custom domain names instead Azure-provided names
• No need to invest in a DNS solution
• DNS record : A, CNAME, TXT, MX, SOA, AAAA, PTR, and SVR
• Host names for VMs in VNet automatically maintained
• Split-horizon DNS supported

Question 3
We can use Resource Lock to protect Azure Private DNS
zone from accidental deletion.
a) True
b) False
43

Question 3
We can use Resource Lock to protect Azure Private DNS
zone from accidental deletion.
a) True
b) False
44

Break
45

Demo
1. Create Azure Public Load balancer
2. Create Azure Application Gateway
3. Create Azure Traffic Manager Profile
4. Create Azure DNS zone for internal name resolution
5. Create Azure DNS zone for external name resolution

48
https://bharatguru.in
Thanks!https://azureezy.com/az-104
https://t.me/AzureTalk
https://youtube.com/AzureTalk
https://www.linkedin.com/in/nirajkum/
https://www.linkedin.com/in/vipinkumarjha/
https://www.linkedin.com/in/ashishrajsrivastava
https://azuredevopspro.com
https://youtube.com/c/AshishRajSrivastava
@AshishRajS

Az 104 session 6 azure networking part2

More Related Content

What's hot (20)

Similar to Az 104 session 6 azure networking part2 (20)

Recently uploaded (20)

Az 104 session 6 azure networking part2