Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might have
more than one correct solution, while others might not have a correct solution.
After you answer a question in this sections, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You develop an enterprise application that will be used only by the employees of a company. The application is
not Internet-facing. You deploy instances of the application to Azure datacenters on two continents.
You must implement a load balancing solution that meets the following requirements:
Provide network-level distribution of traffic across all instances of the application.
Support HTTP and HTTPS protocols.
Manage all inbound and outbound connections.
Any back-end virtual machine (VM) must be able to service requests from the same user or client session.
Solution: You implement Traffic Manager and Application Gateway.
Does the solution meet the goal?
A.
Yes
B.
No
Explanation:
Application Gateway works at the application layer (Layer 7 in the OSI network reference stack). It acts as areverse-proxy service, terminating the client connection and forwarding requests to back-end endpoints. It
supports the HTTP, HTTPS, and WebSockets protocols.
Application Gateway is useful for applications that require requests from the same user/client session to reach
the same back-end virtual machine. Examples of these applications would be shopping cart applications and
web mail servers.
Traffic Manager works at the DNS level. It uses DNS responses to direct end-user traffic to globally distributed
endpoints. Clients then connect to those endpoints directly.
Microsoft Azure Traffic Manager allows you to control the distribution of user traffic for service endpoints in
different datacenters
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview