QuestionQ5

Configuration

An engineer creates a new rule while configuring an Access Control Policy. After the policy is deployed, the rule does not work as expected, and its associated hit counters remain at zero. What is causing this error?

  • A An incorrect application signature was used in the rule.
  • B The wrong source interface for Snort was selected in the rule.
  • C The rule was not enabled after being created.
  • D Logging is not enabled for the rule.
Explanation

Access-control rules match traffic based on their configured source and destination security zones, which correspond to the interfaces through which traffic enters and exits the device. Selecting the wrong source interface prevents the intended traffic from matching the rule, so the rule does not take effect and its hit counter remains zero. Logging settings do not determine rule hit counts.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!