For question 8 , download request can be easily routed using path based routing through App Gateway . Something like add a rule /downloads/* and route them to dedicated VMs. How ATM becomes more correct option ?
@Ravindu Perera The health probe attempts to check the configured health probe port every 15 seconds by default. The minimum probe interval is 5 seconds. The total duration of all intervals cannot exceed 120 seconds. Reference: docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview
In question 2, A private load balancer is also known as the internal load balancer, I searched this on MS and in MS also this is mentioned, please correct me if I'm wrong
@idlir Accoding to the document HTTP status codes of 200 through 399 are considered healthy. Let me know what you think?! Ref doc here: docs.microsoft.com/en-us/azure/application-gateway/application-gateway-backend-health-troubleshooting
@@AGuideToCloud I stumbled over this as well, because 200 is a success status code, while 400 and above are error codes (ref: en.wikipedia.org/wiki/List_of_HTTP_status_codes). So the only thing really is this formality of calling it "HTTP 200 error". If you said "HTTP 200 status", everything would be fine without room for discussion.
At 5:45 you say every 15 seconds but am pretty sure it's every 5 seconds. 😃
For question 8 , download request can be easily routed using path based routing through App Gateway . Something like add a rule /downloads/* and route them to dedicated VMs. How ATM becomes more correct option ?
@deep mehrotra Thanks for sharing!
@@AGuideToCloud I agree with Deep, I think App Gateway is the correct answer.
Thanks for confirming!
At 5:34 Can you clarify why it is wrong? The default interval is 30 Seconds. Isn't it?
@Ravindu Perera The health probe attempts to check the configured health probe port every 15 seconds by default. The minimum probe interval is 5 seconds. The total duration of all intervals cannot exceed 120 seconds.
Reference: docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview
why in question 3 we cant use application gateway?? It can loadbalance and supports auto scailing so best will be that right??
minimize complexity requirement lends to ALB
Thamks You Mr susanth for this nice course, But from where we can download the the Material explained in thses videos!?!
In question 2,
A private load balancer is also known as the internal load balancer,
I searched this on MS and in MS also this is mentioned,
please correct me if I'm wrong
Thanks
Welcome
Question Nr.4
The instance is healthy if it responds with an HTTP 200 ERROR -> that is also false
@idlir Accoding to the document HTTP status codes of 200 through 399 are considered healthy.
Let me know what you think?!
Ref doc here: docs.microsoft.com/en-us/azure/application-gateway/application-gateway-backend-health-troubleshooting
@@AGuideToCloud So you mean that the "200 error" is not affecting the probe health?
Correct as per the documentation!
@@AGuideToCloud I stumbled over this as well, because 200 is a success status code, while 400 and above are error codes (ref: en.wikipedia.org/wiki/List_of_HTTP_status_codes). So the only thing really is this formality of calling it "HTTP 200 error". If you said "HTTP 200 status", everything would be fine without room for discussion.
@@AGuideToCloud the first thing is...http return 200 is "OK", not failure or error