1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Exam Prep 70-533: Implementing Microsoft Azure Infrastructure Solutions

Azure Resource Manager Load Balancer


Overview of the course
Course Intro
Course Overview
Start course


Exam Prep 70-533: Implementing Microsoft Azure Infrastructure Solutions

The purpose of this course is to help prepare you for the Microsoft Azure 70-533 Exam. This course focuses on key points that are meant to fill in the learning gaps for those who already have a base foundational knowledge of Microsoft Azure.

What You'll Learn in this Exam Prep 70-533

Lesson What you'll learn
Overview of the Course Overview of the course and the Learning Objectives
About the 70-533 Exam Learn about the exam, its objectives, and certification paths
Design and Implement Azure App Service Apps Discuss App Service Plans and Web Apps
Create and Manage ARM Virtual Machines Understand ARM VMs, pricing, resiliency and configuration limits
Design and Implement a Storage Strategy Learn to Implement Azure Storage, SQL Databases, and Recovery Services
Implement an Azure Active Directory Discuss Azure AD, tools, App integration, and monitoring
Implement Virtual Networks Learn about Azure networking and cross-site connectivity
Design and Deploy ARM Templates Learn about ARM Templates and Deployment options
Summary Course summary including Exam Tips and Tricks



An Azure Load Balancer explicitly routes traffic among different Azure Virtual Machines. Load Balancers are very useful and they have a couple of algorithms for how they route traffic. The default method is Hash-based which uses a combination of the source and destination IPs, the source and destination ports and the protocol, typically TCP or UDP. The other method is Source IP Affinity mode which is a 2 or 3-tuple combination of the source and destination IPs and/or protocol.

The main concept here is something we call “stickiness” or how sticky does a client session sticks to a particular VM on the load balancer backend during a communication session. For example in Source IP Affinity mode, connections initiated from the same client machine destined for the load balancer will always go the same VM behind the load balancer since it’s based mainly on the source IP of the client, and the fixed destination IP Address of the load balancer in a 2-tuple setup.

Azure load balancers include Port Forwarding which allows you to do network address translation. For example in the older “Classic” deployment model your VMs were located behind what’s called a Cloud Service which has a built-in Load balancer. So if you were to connect over RDP, you would connect to a random configured port number on the Cloud Service which then does Network Address Translation to the proper IP destination and RDP port 3389 to help mask your RDP service from the outside world. In the ARM deployment model, we have the same thing, however, you just have to create the Load balancer yourself and configure inbound NAT rules to your backend VMs.

Also if you work with Virtual Machine Scale Sets, as you scale your VM instances servers are added or removed from your load balancer backend and NAT rules are automatically configured. Load balancer monitoring is available and configurable in the form of HTTP or TCP probes to help monitor the service.

About the Author

Learning paths2

Chris has over 15 years of experience working with top IT Enterprise businesses.  Having worked at Google helping to launch Gmail, YouTube, Maps and more and most recently at Microsoft working directly with Microsoft Azure for both Commercial and Public Sectors, Chris brings a wealth of knowledge and experience to the team in architecting complex solutions and advanced troubleshooting techniques.  He holds several Microsoft Certifications including Azure Certifications.

In his spare time, Chris enjoys movies, gaming, outdoor activities, and Brazilian Jiu-Jitsu.