91 Questions
What is the purpose of system routes in Azure?
To direct data flow from VMs to the Internet
What does a Route Table in Azure contain?
A set of rules specifying how packets should be routed in a virtual network
What is the function of User-Defined Routes (UDRs) in Azure?
To control network traffic by defining the next hop of the traffic flow
In Azure, can a subnet be associated with multiple route tables?
No, a subnet can only be associated with a single route table
What is the role of network virtual appliances (NVAs) in Azure?
To assist with network functions like routing and firewall optimization
Which of the following can be defined as the next hop in User-Defined Routes (UDRs) in Azure?
Virtual network gateway
What is the main purpose of Azure Load Balancer?
To distribute incoming network traffic across multiple servers
What does a network virtual appliance (NVA) help with in Azure?
Network functions like routing and firewall optimization
Which type of communication does the Azure Application Gateway primarily manage?
HTTP and HTTPS traffic
What is the function of Route Tables in Azure?
Contain a set of rules specifying how packets should be routed in a virtual network
What is the purpose of Service Endpoint in Azure networking?
Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic
Which service is NOT available for Service Endpoint in Azure?
Azure Kubernetes Service
What are the key features of Private Link in Azure networking?
Provides private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration
What is the primary function of the Azure Load Balancer?
Distributes inbound traffic to backend resources using load-balancing rules and health probes
What does the Public Load Balancer map public IP address and port number to?
Private IP address and port number of the VM
What is the purpose of an Internal Load Balancer in Azure networking?
Directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure
What is the purpose of Load Balancer SKUs in Azure networking?
Determine the instance limits for the backend pool
What do load balancer rules define in Azure networking?
How traffic is distributed to the backend pool
What is the purpose of Session Persistence in load balancing?
Specifies how traffic from a client should be handled
What role do Health Probes play in load balancing?
Dynamically add or remove VMs from the load balancer rotation based on their response to health checks
Service ______ provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
endpoint
Private Link brings services to a private virtual network, providing private ______ to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
connectivity
The Azure Load Balancer distributes inbound traffic to backend ______ using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
resources
Public Load Balancer maps public IP ______ and port number of incoming traffic to the private IP ______ and port number of the VM and also provides mapping for response traffic from the VM.
address
Internal Load Balancer directs ______ to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
traffic
A public load ______ could be placed in front of an internal load ______ to create a multi-tier application.
balancer
Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
pools
Load balancer rules define how ______ is distributed to the backend pool and can be used in combination with NAT rules.
traffic
Health Probes dynamically add or remove ______ from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
VMs
Application Gateway manages client application ______ to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
requests
Each route table can be associated to multiple subnets, but a subnet can only be associated to a single route table. There are no charges for creating route tables in Microsoft Azure. MST400 Network Routing and Endpoints: User-Defined Routes User-Defined Routes (______) control network traffic by defining the next hop of the traffic flow. The hop can be a virtual network gateway, virtual network, internet, or virtual appliance.
UDRs
NVAs are VMs that help with network functions like routing and firewall optimization. We want to ensure all traffic from the Public subnet goes through the NVA to the Private subnet.
network virtual appliance
A ______ contains a set of rules, called routes, that specifies how packets should be routed in a virtual network.
Route Table
MST400 Network Routing and Endpoints: System Routes Azure uses ______ to direct network traffic Traffic between VMs in the same subnet. Between VMs in different subnets in the same virtual network. Data flow from VMs to the Internet. Site-to-Site and ExpressRoute communication through the VPN gateway.
system routes
In the ______ subnet, there is a network virtual appliance (NVA). NVAs are VMs that help with network functions like routing and firewall optimization. We want to ensure all traffic from the Public subnet goes through the NVA to the Private subnet.
DMZ
We have a virtual network that includes ______ subnets. In the DMZ subnet, there is a network virtual appliance (NVA). NVAs are VMs that help with network functions like routing and firewall optimization. We want to ensure all traffic from the Public subnet goes through the NVA to the Private subnet.
three
MST400 Network Routing and Endpoints: User-Defined Routes User-Defined Routes (UDRs) control network traffic by defining the ______ of the traffic flow. The hop can be a virtual network gateway, virtual network, internet, or virtual appliance.
next hop
MST400 Network Routing and Endpoints: System Routes Azure uses system routes to direct network traffic Traffic between VMs in the same subnet. Between VMs in different subnets in the same virtual network. Data flow from VMs to the Internet. Site-to-Site and ExpressRoute communication through the VPN gateway.
Network Traffic Management
System routes in Azure are used to direct network traffic between VMs in the same subnet, between VMs in different subnets in the same virtual network, and for data flow from VMs to the Internet.
True
A Route Table in Azure contains a set of rules, called routes, that specifies how packets should be routed in a virtual network.
True
User-Defined Routes (UDRs) control network traffic by defining the next hop of the traffic flow, which can be a virtual network gateway, virtual network, internet, or virtual appliance.
True
Network virtual appliances (NVAs) in Azure help with network functions like routing and firewall optimization.
True
The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
True
Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
True
Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
True
Private Link in Azure networking brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
True
Health Probes dynamically add or remove resources from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
True
Service Endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
True
Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
True
The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
True
Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
True
A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
True
Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
True
Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
True
Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
True
Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
True
Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
True
Match the following Azure networking components with their primary functions:
System Routes = Direct network traffic between VMs in the same subnet, between VMs in different subnets in the same virtual network, and from VMs to the Internet User-Defined Routes (UDRs) = Control network traffic by defining the next hop of the traffic flow, which can be a virtual network gateway, virtual network, internet, or virtual appliance Route Table = Contains a set of rules, called routes, that specifies how packets should be routed in a virtual network Network Virtual Appliance (NVA) = Helps with network functions like routing and firewall optimization
Match the following load balancing features in Azure with their functions:
Azure Load Balancer = Distributes inbound traffic to backend resources using load-balancing rules and health probes for inbound and outbound scenarios Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes Load Balancer Rules = Define how traffic is distributed to the backend pool and can be used in combination with NAT rules Session Persistence = Maintains client affinity by consistently routing a client's requests to the same backend resource
Match the following Azure networking services with their primary functions:
Service Endpoint = Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic Private Link = Brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration Application Gateway = Manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications Internal Load Balancer = Directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios
Match the following load balancing components in Azure with their functions:
Public Load Balancer = Maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM Load Balancer SKUs = Include Standard and Basic, with different instance limits for the backend pool NAT Rules = Used in combination with load balancer rules to define how traffic is distributed to the backend pool Backend Pool = Consists of the resources to which traffic is distributed by the load balancer
Match the Azure networking feature with its description:
Service Endpoint = Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic. Private Link = Brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration. Azure Load Balancer = Distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios. Public Load Balancer = Maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
Match the Load Balancer feature with its function:
Load Balancer SKUs = Include Standard and Basic, with different instance limits for the backend pool. Load balancer rules = Define how traffic is distributed to the backend pool and can be used in combination with NAT rules. Session Persistence = Specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol. Health Probes = Dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
Match the load balancing scenario with its description:
Internal Load Balancer = Directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios. Public Load Balancer placed in front of an internal load balancer = Creates a multi-tier application. Application Gateway = Manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications. Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
Match the Azure load balancing feature with its purpose:
Load Balancer SKUs = Determine the instance limits for the backend pool. Session Persistence = Specifies how traffic from a client should be handled. Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks. Internal Load Balancer = Directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure.
Match the Azure load balancing feature with its function:
Public Load Balancer = Maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM. Load balancer rules = Define how traffic is distributed to the backend pool and can be used in combination with NAT rules. Service Endpoint = Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic. Private Link = Brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
Match the load balancing feature with its functionality:
Application Gateway = Manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications. Load balancer rules = Define how traffic is distributed to the backend pool and can be used in combination with NAT rules. Session Persistence = Specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol. Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
Match the Azure load balancing feature with its description:
Public Load Balancer = Maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM. Load Balancer SKUs = Include Standard and Basic, with different instance limits for the backend pool. Service Endpoint = Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic. Private Link = Brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
Match the Azure load balancing feature with its functionality:
Azure Load Balancer = Distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios. Public Load Balancer placed in front of an internal load balancer = Creates a multi-tier application. Application Gateway = Manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications. Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
Match the Azure networking feature with its purpose:
Service Endpoint = Provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic. Private Link = Brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration. Azure Load Balancer = Distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios. Public Load Balancer = Maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
Match the Azure load balancing feature with its purpose:
Load Balancer SKUs = Determine the instance limits for the backend pool. Session Persistence = Specifies how traffic from a client should be handled. Health Probes = Dynamically add or remove resources from the load balancer rotation based on their response to health checks. Internal Load Balancer = Directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure.
Explain the purpose of system routes in Microsoft Azure network traffic management.
System routes in Microsoft Azure are used to direct network traffic between VMs in the same subnet, between VMs in different subnets in the same virtual network, data flow from VMs to the Internet, and for site-to-site and ExpressRoute communication through the VPN gateway.
What are User-Defined Routes (UDRs) and how do they control network traffic in Azure?
User-Defined Routes (UDRs) in Azure control network traffic by defining the next hop of the traffic flow. The next hop can be a virtual network gateway, virtual network, internet, or virtual appliance.
Describe the function of Route Tables in Azure networking.
A Route Table in Azure contains a set of rules, called routes, that specifies how packets should be routed in a virtual network.
What is the purpose of Load Balancer SKUs in Azure networking?
Load Balancer SKUs in Azure include Standard and Basic, with different instance limits for the backend pool.
How can a network virtual appliance (NVA) help with network functions in Azure?
Network virtual appliances (NVAs) in Azure help with network functions like routing and firewall optimization.
Explain the role of a public load balancer in Azure networking.
A public load balancer in Azure maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
What is the primary function of the Azure Load Balancer?
The primary function of the Azure Load Balancer is to distribute inbound traffic to backend resources using load-balancing rules and health probes, and it can be used for inbound and outbound scenarios.
What is the purpose of Service Endpoint in Azure networking?
Service Endpoint in Azure networking provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
Describe the function of Application Gateway in Azure networking.
Application Gateway in Azure networking manages client application traffic to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Explain the concept of Private Link in Azure networking.
Private Link in Azure networking brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
Explain the purpose of Private Link in Azure networking and list some of its key features.
Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration. Some key features include private connectivity, integration with on-premises and peered networks, and protection against data exfiltration.
What are the different SKUs available for Load Balancer in Azure and what are their differences?
Load Balancer SKUs include Standard and Basic. They have different instance limits for the backend pool.
Describe the function of Load balancer rules and their possible combination with NAT rules.
Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules to further control traffic flow.
What is the role of Session Persistence in load balancing and what are some available options?
Session Persistence specifies how traffic from a client should be handled. Some available options include None, Client IP, and Client IP and protocol.
Explain the purpose of Health Probes in Azure Load Balancer and how they dynamically manage backend resources.
Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks. They can be configured using HTTP and TCP custom probes.
What is the primary function of Azure Load Balancer and how does it handle inbound traffic?
The primary function of Azure Load Balancer is to distribute inbound traffic to backend resources using load-balancing rules and health probes. It can be used for both inbound and outbound scenarios.
How does Public Load Balancer map incoming and response traffic in Azure?
Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM, and also provides mapping for response traffic from the VM.
What are some of the services available for Service Endpoint in Azure networking?
Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
Explain the purpose of Service Endpoint in Azure networking and how it enhances security and routing.
Service Endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
What is the main purpose of Private Link in Azure networking and how does it provide connectivity and protection?
Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
Study Notes
Azure Networking and Load Balancing Features
- Service endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
- Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
- Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
- The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
- Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
- Internal Load Balancer directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
- A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
- Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
- Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
- Session Persistence specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol.
- Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
- Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Azure Networking and Load Balancing Features
- Service endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
- Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
- Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
- The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
- Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
- Internal Load Balancer directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
- A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
- Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
- Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
- Session Persistence specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol.
- Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
- Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Azure Networking and Load Balancing Features
- Service endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
- Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
- Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
- The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
- Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
- Internal Load Balancer directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
- A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
- Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
- Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
- Session Persistence specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol.
- Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
- Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Azure Networking and Load Balancing Features
- Service endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
- Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
- Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
- The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
- Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
- Internal Load Balancer directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
- A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
- Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
- Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
- Session Persistence specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol.
- Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
- Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Azure Networking and Load Balancing Features
- Service endpoint provides identity to virtual network services and offers improved security and optimal routing for Azure service traffic.
- Several services are available for Service Endpoint, including Azure Storage, Azure SQL Database, Azure Cosmos DB, and Azure Key Vault.
- Private Link brings services to a private virtual network, providing private connectivity to services on Azure, integration with on-premises and peered networks, and protection against data exfiltration.
- The Azure Load Balancer distributes inbound traffic to backend resources using load-balancing rules and health probes and can be used for inbound and outbound scenarios.
- Public Load Balancer maps public IP address and port number of incoming traffic to the private IP address and port number of the VM and also provides mapping for response traffic from the VM.
- Internal Load Balancer directs traffic to resources inside a virtual network or using a VPN to access Azure infrastructure and is used for various types of load balancing scenarios.
- A public load balancer could be placed in front of an internal load balancer to create a multi-tier application.
- Load Balancer SKUs include Standard and Basic, with different instance limits for the backend pool.
- Load balancer rules define how traffic is distributed to the backend pool and can be used in combination with NAT rules.
- Session Persistence specifies how traffic from a client should be handled and offers options like None, Client IP, and Client IP and protocol.
- Health Probes dynamically add or remove VMs from the load balancer rotation based on their response to health checks and can be configured using HTTP and TCP custom probes.
- Application Gateway manages client application requests to a web app, uses round robin for load balancing, and supports features like path-based routing and multiple site routing for different URL paths and multiple web applications.
Test your knowledge of Azure networking and load balancing features with this quiz. Learn about service endpoints, private link, load balancer types and rules, session persistence, health probes, and more. Perfect for anyone working with Azure infrastructure and networking.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
