Exam NSE7_PBC-6.4 topic 1 question 9 discussion

It is less than 10 seconds. First it is ACTIVE ACTIVE configuration, so Azure Load balancer as soon as detect the failure mark the device as unhealthy. I´d recommend you mark this question and send do feedback in the exam if you face it. FINALLY if you check the LAB recorded in the oficial NSE course from Fortinet Portal, the instructor does test the LOAD BALANCE and clearly states that the Fortigate machine ACTIVE ACTIVE HA becomes unhealty in less than 10 seconds in case of failure, of if the official instructors says that recorded who am I to disagree ?

A. Less than 10 seconds

Answer A In my opinion, the question is related to Azure "take an action" https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview -If your application produces a time-out response just before the next probe arrives, the detection of the events will take 5 seconds plus the duration of the application time-out when the probe arrives. You can assume the detection to take slightly over 5 seconds. -If your application produces a time-out response just after the next probe arrives, the detection of the events won't begin until the probe arrives and times out, plus another 5 seconds. You can assume the detection to take just under 10 seconds. Assume the reaction to a time-out response will take a minimum of 5 seconds and a maximum of 10 seconds to react to the change.

https://github.com/fortinet/azure-templates/blob/main/FortiGate/Active-Active-ELB-ILB/azuredeploy.json#L580 its an a-a architecture and the default TCP probe is 5x2 ( every 5 seconds X 2 Intervals for failover)

Any manipulation of UDRs or public IP addresses for active-passive solutions take 30 seconds to be applied after failover is initiated, whereas Azure load balancers can send probes as often as every five seconds and will stop forwarding traffic after two failures

"A" is the best answer. From 6 to 10 seconds... https://docs.fortinet.com/document/fortigate-public-cloud/6.0.0/use-case-high-availability-for-fortigate-on-azure/224311/basic-concepts Remembering: FortiGate Scenario (HA Active/Active)

HA Failover: * 30 seconds -- 2 minutes is Active -Passive * less 10 seconds is Active - Active I think is A.

Another tricky question, option B would look the best fit hier, Azure official documentation under HTTP/HTTPS probe. it says that how much time would it take to mark a fortigate vm down, here is assuming that we are probing the vm over its http/https server. https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview

B. https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview

B, 30 seconds. The default health monitoring tests the three servers every 30 seconds for a healthy HTTP response with a 30 second timeout for each request. https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-probe-overview

B. 30 seconds