156-582 · Question #4
You tested the connection from source to destination and you are not able to find logs in your Security Management. What is the best possible reason?
The correct answer is C. The logging blade was not enabled on Security Gateway. If logs are not appearing in the Security Management despite successful traffic flow, the most likely reason is that the logging blade is not enabled on the Security Gateway. Without enabling the logging functionality, the gateway will not send logs to the Security Management…
Question
You tested the connection from source to destination and you are not able to find logs in your Security Management. What is the best possible reason?
Options
- AThe FWM process crashed on Security Management, therefore logging will not work.
- BThere is not enough storage in Security Management, so the logs can't be stored.
- CThe logging blade was not enabled on Security Gateway.
- DThe gateway is logging locally.
How the community answered
(33 responses)- A12% (4)
- B6% (2)
- C79% (26)
- D3% (1)
Explanation
If logs are not appearing in the Security Management despite successful traffic flow, the most likely reason is that the logging blade is not enabled on the Security Gateway. Without enabling the logging functionality, the gateway will not send logs to the Security Management Server, even though the traffic itself is passing through successfully.
Topics
Community Discussion
No community discussion yet for this question.