How do you configure a logging action that writes firewall logs to a file named "firewall.log"?

How do you configure a logging action that writes firewall logs to a file named "firewall.log"?

• A. /system logging action add name=file1 target=memory; /system logging add topics=firewall,info action=file1
• B. /system logging action add name=file1 target=file file-name=firewall.log; /system logging add topics=firewall,info action=file1
• C. /system logging action add name=file2 target=file file-name=firewall.log; /system logging add topics=firewall,info action=file2
• D. /system logging action add name=file1 target=file file-name=server.log; /system logging add topics=kernel,info action=file1

Answer: (B)

To write firewall events to a file, you need a logging action that uses a file backend and specifies the file name, then attach that action to a rule that captures firewall events. The key is setting the action’s target to file and providing the file-name as firewall.log, so the log output goes into that file. Then you create a log entry for the firewall category at the info level and link it to the action you just defined. This combination ensures that firewall-related messages are written to firewall.log rather than staying in memory or going to another destination. In practice, you define the action with: target=file and file-name=firewall.log, giving it a name like file1. Then you add a log rule that uses topics=firewall,info and action=file1. Other options either direct logs to memory, use a different target or file name, or log different topics, which would not produce the desired firewall.log file.

To write firewall events to a file, you need a logging action that uses a file backend and specifies the file name, then attach that action to a rule that captures firewall events. The key is setting the action’s target to file and providing the file-name as firewall.log, so the log output goes into that file. Then you create a log entry for the firewall category at the info level and link it to the action you just defined. This combination ensures that firewall-related messages are written to firewall.log rather than staying in memory or going to another destination.

In practice, you define the action with: target=file and file-name=firewall.log, giving it a name like file1. Then you add a log rule that uses topics=firewall,info and action=file1. Other options either direct logs to memory, use a different target or file name, or log different topics, which would not produce the desired firewall.log file.