In FortiAnalyzer's FormView, source and destination IP addresses from FortiGate devices are not resolving to a hostname. How can you resolve the source and destination IPs, without introducing any additional performance impact to FortiAnalyzer?

• A.Resolve IPs on FortiGate
• B.Configure # set resolve-ip enable in the system FortiView settings
• C.Resolve IPs on a per-ADOM basis to reduce delay on FortiView while IPs resolve
• D.Configure local DNS servers on FortiAnalyzer

Comment: *

Name: *

Email: *

Verification: *

By default, what happens when a log file reaches its maximum file size?

• A.FortiAnalyzer rolls the active log by renaming the file.
• B.FortiAnalyzer stops logging.
• C.FortiAnalyzer overwrites the log files.
• D.FortiAnalyzer forwards logs to syslog.

Comment: *

Name: *

Email: *

Verification: *

Logs are being deleted from one of your ADOMs earlier that the configured setting for archiving in your data policy. What is the most likely problem?

• A.The total disk space is insufficient and you need to add other disk.
• B.CPU resources are too high.
• C.The ADOM disk quota is set too low based on log rates.
• D.Logs in that ADOM are being forwarded in real-time to another FortiAnalyzer device.

Comment: *

Name: *

Email: *

Verification: *

If a hard disk fails on a FortiAnalyzer that supports software RAID, what should you do to bring the FortiAnalyzer back to functioning normally, without losing data?

• A.Hot swap the disk
• B.Replace the disk and rebuild the RAID manually
• C.Take no action if the RAID level supports a failed disk
• D.Shut down FortiAnalyzer and replace the disk

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

What does the data point at 14:55 tell you?

• A.Raw logs are reaching FortiAnalyzer faster than they can be indexed
• B.Logs are being dropped
• C.The sqlplugind daemon is behind in log indexing by two logs
• D.The received rate is almost at its maximum for this device

Comment: *

Name: *

Email: *

Verification: *