Exam AZ-104 topic 2 question 26 discussion

Correct Answer: A and E A: The customer sites are connected through VPNs, so an internal load balancer is enough. B: The customer sites are connected through VPNs, so there's no need for a public load balancer, an internal load balancer is enough. C: A CDN does not provide load balancing for applications, so it not relevant for this situation. D: Traffic manager is a DNS based solution to direct users' requests to the nearest (typically) instance and does not provide load balancing for this situation. E: Azure Application Gateway is a valid option, as it provides load balancing in addition to routing and security functions

i would say A and E is the correct answer.

Exhausting Az104 exam Never coming back to this

Public Load Balancer cannot be used here as the connections must use a VPN (ie private ip addresses on Azure) Application Gateway is not on option. a lob application is not a web app (even some old web app can be lob application.) the first (and most natural) answer is an internal load balancer. The second is traffic manager. You can configure a traffic manager with for example a routing method weighted and then add to your TM an external endpoint with a private IP address

Line of business app can be anything custom written, it never mentioned web app. App Gateway uses http and https, so it may not work, ergo internal and external load balancers are the answer by process of elimination.

The question never stated this is a web app, therefore the only plausible answers are internal or public load balancer. Web app only support http(s)

Wouldn't pick the public one so....

You know what is complicated? Azure Application Gateway is used specific for HTTP/HTTPS based requests, in its setup, when you create the routing rule, there is an option that force you to select the Protocol either HTTP or HTTPS, there is a port option, but those are for custom ports, fact is, it is based on HTTP/S. This question does not specify if the line-of-business app is HTTP/S based, a WebApp. A public balancer here would be a more broad option to attend all scenarios, however, yes, it would have a cost for public IP and would be unecessary since we already got VPNs setup. This is one of those scenarios that I would comment on the question, stating that is poorly worded. No doubt on Internal LB, but cant decide here between AAG/PLB.

Two possible Azure services that can be used to spread connections to App1 across all virtual machines are: A. An internal load balancer: This service can be used to distribute network traffic to virtual machines that are part of an availability set or a virtual machine scale set. It works by forwarding incoming traffic to healthy virtual machines in the backend pool. Since App1 runs on multiple virtual machines, an internal load balancer can be used to distribute the traffic evenly among them. E. An Azure Application Gateway: This service is a layer 7 load balancer that can distribute traffic based on different criteria, such as URL path or host header. It can also perform SSL offloading, web application firewall, and other features that can enhance the performance and security of web applications. Since App1 is a line-of-business app, it's likely that it runs over HTTP or HTTPS, which makes an Azure Application Gateway a suitable solution for load balancing.

Two possible Azure services that can be used to spread connections to App1 across all virtual machines are: A. an internal load balancer: An internal load balancer can be used to distribute traffic among the virtual machines running App1. It can distribute traffic based on various algorithms such as round-robin, least connections, and IP hash. The internal load balancer is a layer 4 (Transport Layer) load balancer that can distribute traffic within a virtual network. E. an Azure Application Gateway: An Azure Application Gateway is a layer 7 (Application Layer) load balancer that can distribute traffic based on various criteria such as URL path, host headers, and cookie. It can also perform SSL offloading, session affinity, and URL-based routing. It is typically used to route traffic to different backend services based on the incoming request's contents. It is a more advanced option than the internal load balancer but requires a public IP address.

A & E are correct

No doubt about it AE

I used free version access for this site and it helped me pass the exam. Some questions that I had on the exams, I took the exam more than once, are not available under the free tier access, but 80% of the questions came from here. I do recommend investing a bit of money and getting full access to this site. I didn't memorise answers but analysed them and studied as Microsoft does tweak them a bit. This Q was on the exam and the answer isA, E.

Two possible Azure services that can be used to spread connections to App1 across all virtual machines are: A. An internal load balancer: This can be used to distribute incoming traffic to virtual machines in a backend pool based on various routing rules and health probes. It is a Layer 4 (TCP/UDP) load balancer that is used for internal traffic within a virtual network. E. An Azure Application Gateway: This can be used to route incoming traffic to virtual machines based on various routing rules, including URL path-based routing, cookie-based session affinity, and SSL offloading. It is a Layer 7 (HTTP/HTTPS) load balancer that can be used for both internal and external traffic. Both of these services can be used to distribute incoming traffic across multiple virtual machines, improving availability and scalability of App1.

Correct Answer: A and E Given that the application is a webapp.

A & E is the correct answer

Quote from Microsoft's documentation: Azure provides a suite of fully managed load-balancing solutions for your scenarios: * If you are looking to do DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination ("SSL offload"), per-HTTP/HTTPS request or application-layer processing, review Traffic Manager. * If you want to load balance between your servers in a region at the application layer, review Application Gateway. * If you need to optimize global routing of your web traffic and optimize top-tier end-user performance and reliability through quick global failover, see Front Door.