Question 220
In a managed firewall deployment, the team observes: The firewall reports a high session count near platform limits after a new internet application rollout. Investigation has shown: Inspect session table utilization, application counts, timeouts and model capacity. Which corrective action best addresses that evidence?
Explanation
Correct Answer
The appropriate response is to reduce excessive sessions or scale capacity with suitable protocol-specific policy controls. The case begins with the firewall reports a high session count near platform limits after a new internet application rollout. The diagnostic basis is to inspect session table utilization, application counts, timeouts and model capacity. This action addresses the mechanism revealed by that check rather than changing a different security feature or expanding access. A convincing post-change check would show that new legitimate sessions establish at peak load without resource-exhaustion resets.
Incorrect Answers
This action addresses the separate condition that traffic logs are unexpectedly sparse after changing profiles, but device statistics show sessions and threat processing still occurring. Its role is to repair the confirmed log pipeline problem while retaining the expected inspection policies. The current incident instead concerns the firewall reports a high session count near platform limits after a new internet application rollout. After the specified diagnostic evidence, the supported change is to reduce excessive sessions or scale capacity with suitable protocol-specific policy controls. The proposed alternative need not resolve that underlying fault.
Restore the management DNS, route or cloud connectivity path without disrupting healthy user forwarding. This assesses the management DNS, route or cloud connectivity path without disrupting healthy user forwarding; it does not determine the reported condition—the firewall reports a high session count near platform limits after a new internet application rollout.
Repair the proven link or transceiver mismatch before tuning Security policy. The case-specific requirement is reducing excessive sessions or scale capacity with suitable protocol-specific policy controls, which that option does not establish.