Exam 300-710 topic 1 question 56 discussion

I believe this question is mis-worded and is referring to a restart of the SNORT process, rather than the Device. Basically, it appears to be saying that if you adjust a file policy in the ACP, then the device that has interfaces in zones referenced in that ACP will have its SNORT process restarted. https://www.cisco.com/c/en/us/td/docs/security/firepower/623/configuration/guide/fpmc-config-guide-v623/policy_management.html "Note that access control rules that deploy these file policy configurations to security zones or tunnel zones cause a restart only when your configuration meets the following conditions: Source or destination security zones in your access control rule must match the security zones associated with interfaces on the target devices. Unless the destination zone in you access control rule is any, a source tunnel zone in the rule must match a tunnel zone assigned to a tunnel rule in the prefilter policy."

nterruptions to Traffic Flow and Inspection During Deploy When you deploy, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations restarts the Snort process, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the target device handles traffic. See Snort® Restart Traffic Behavior and Configurations that Restart the Snort Process When Deployed or Activated.

A. Source or destination security zones in the access control rule matches the security zones that are associated with interfaces on the target devices. The reason for the device to restart is that the source or destination security zones in the access control rule matches the security zones that are associated with interfaces on the target devices. This can cause a routing loop that can overload the device and cause it to restart. When configuring file policies and access control rules in Cisco FMC, it is important to ensure that the source and destination security zones do not match the security zones associated with interfaces on the target devices. This can be done by reviewing the zone assignments and making any necessary changes to prevent the routing loop. The other options listed are not the reason for the device to restart in this scenario. B and D relate to tunnel zones and tunnel rules, which are not mentioned in the scenario. C relates to source and destination security zones in a source tunnel zone, which is not directly relevant to the scenario.

Note that access control rules that deploy these file policy configurations to security zones or tunnel zones cause a restart only when your configuration meets the following conditions: Source or destination security zones in your access control rule must match the security zones associated with interfaces on the target devices. Unless the destination zone in you access control rule is any, a source tunnel zone in the rule must match a tunnel zone assigned to a tunnel rule in the prefilter policy