diff --git a/articles/application-gateway/application-gateway-faq.md b/articles/application-gateway/application-gateway-faq.md
index 6ace1f3550af8..8c07c91c3fa7b 100644
--- a/articles/application-gateway/application-gateway-faq.md
+++ b/articles/application-gateway/application-gateway-faq.md
@@ -82,6 +82,7 @@ Yes, Application Gateway inserts x-forwarded-for, x-forwarded-proto, and x-forwa
 
 New Application Gateway deployments can take up to 20 minutes to provision. Changes to instance size/count are not disruptive, and the gateway remains active during this time.
 
+
 ## Configuration
 
 **Q. Is Application Gateway always deployed in a virtual network?**
@@ -130,6 +131,11 @@ Micro service architecture is supported. You would need multiple http settings c
 
 Custom probes do not support wildcard or regex on response data. 
 
+**Q. How can I determine the number of probes per interval to expect?**
+
+Multiply the number of servers in the backend pool/s by the number of rules. Eg. 2 servers in the backend with 2 rules will give you 4 probes per interval (2x2=4). A larger deployment may require adjusting the interval beyond 30 seconds. For example, 20 servers in the backend with 20 rules will give you 400 probes per interval.
+
+
 **Q. How are rules processed?**
 
 Rules are processed in the order they are configured. It is recommended that multi-site rules are configured before basic rules to reduce the chance that traffic is routed to the inappropriate backend as the basic rule would match traffic based on port prior to the multi-site rule being evaluated.