Free Zscaler ZDTA Actual Exam Questions - Question 14 Discussion

It’s D for me too. Five minutes sounds like a standard default interval — not too fast to overload the system, but quick enough to spot problems fairly rapidly. One minute feels a bit overkill as a default, and 10 or 30 minutes might delay detecting issues. So, five minutes hits that sweet spot without being extreme.

Option B makes sense to me. Ten minutes strikes a balance between not hammering the system with too many requests and still getting reasonably current data. One or five minutes might be too frequent for a default setting, especially if you consider network load in larger environments. Thirty minutes seems too slow to catch issues quickly. So from a practical standpoint, B feels like a solid default timer for web probes.

D feels right to me. Five minutes is a good compromise—frequent enough to catch issues early, but not so often that it bogs down the system. One minute seems too aggressive for a default.

It’s A for me. Usually, the default timers for web probes are set pretty short to catch issues quickly without waiting too long. Five or ten minutes feels too slow if you want up-to-date info. One minute is a pretty standard quick interval for proactive monitoring. Also, since it’s an advanced setup, I’d expect it to be more responsive rather than less.

B tbh. Defaults that are too frequent can cause unnecessary load, so 10 minutes makes sense as a middle ground. Also, in my experience with similar setups, 10 minutes is a common default to balance freshness and system performance. The 1 or 5-minute options seem a bit aggressive for default timers unless it’s specifically for high-priority monitoring.

Probably A. I remember configuring something around 60 seconds as default in similar monitoring setups, so 1 minute feels like the standard quick check interval here.

I think it’s D too. Usually, these kinds of web probes aim for a balance between timely data and not overloading the system, and 5 minutes fits that well. Plus, 1 minute feels too frequent and 10 or 30 minutes might be too slow for default settings, so D makes the most sense here.

Maybe B since 10 minutes is often used to reduce overhead in default probe intervals.

A imo, 1 minute seems too fast for defaults but matches quick probe sends.

I’m pretty sure it’s D since 5 minutes is a common default for active monitoring. D

B imo, 10 minutes reduces unnecessary network load while still providing decent update frequency. Five minutes might be a bit aggressive for default settings in most setups.

B imo, 10 minutes sounds like a reasonable default to avoid too much network traffic, and it’s often a middle ground between quick updates and system load.

A/D? Seems like 1 minute (A) is too frequent for default settings, but 5 minutes (D) fits usual monitoring intervals better than 10 or 30. The system needs balance, so D still feels best.

D imo, it makes sense to send probes every 5 minutes to get timely data without overwhelming the system. The longer intervals like 10 or 30 minutes seem too slow for real-time monitoring.

I think the answer is C. One App Connector per data center should be enough as a minimum deployment.