View all questions & answers for the NSE 5 - FortiAnalyzer 7.4 Analyst Exam Materials exam
Question 52 Discussion
Comments
Selected Answers: B, C
can take some time to generate. If you find reports are taking too long to generate, there are a few steps you
can take to troubleshoot:
• Run diagnostics on your report and view the report summary at the end of the report. Look at the hcache
time to see how long it took to build.
• Check your log rates to get an idea of log volumes.
• Check the insert rate, receive rate, and the log insert lag. They can tell you the rate at which raw logs are
reaching FortiAnalyzer (receive rate) and the rate at which they are indexed by the SQL database (insert
rate) by the sqlplugind daemon. The log insert lag time tells you how many seconds the database is behind
in processing the logs.
• Enable auto-cache in the report settings to boost the reporting performance and reduce report generation
time. Scheduled reports have auto-cache enabled already.
ChatGPT a dit :
Merci pour cet extrait officiel de la documentation Fortinet — il confirme clairement que la bonne réponse à la question est :
❓ Which two steps can you take to troubleshoot slow report generation?
(Choose two answers)
✅ Réponses correctes :
B. Review report diagnostics
C. Enable auto-cache and run the reports again
📚 Justification à partir de la documentation que tu as fournie :
✅ B. Review report diagnostics
"Run diagnostics on your report and view the report summary at the end of the report. Look at the hcache time to see how long it took to build."
→ Cela confirme que l’analyse des diagnostics du rapport est essentielle pour identifier les lenteurs.
✅ C. Enable auto-cache and run the reports again
"Enable auto-cache in the report settings to boost the reporting performance and reduce report generation time."
→ L’auto-cache permet de réutiliser les données indexées au lieu d’analyser les logs bruts à chaque fois, ce qui améliore fortement les performances.
❌ Pourquoi les autres réponses sont incorrectes :
A. Increase the ADOM reports quota
Cela n’accélère pas la génération des rapports.
Ça permet juste d’augmenter l’espace disque disponible pour stocker les rapports.
D. Remove old reports from the hcache
Effacer la hcache ralentit la génération future des rapports qui pourraient réutiliser les données mises en cache.
✅ Réponse finale confirmée :
B. Review report diagnostics
C. Enable auto-cache and run the reports again
If your network has a high volume of devices sending logs to FortiAnalyzer as well as high log volume, reports
can take some time to generate. If you find reports are taking too long to generate, there are a few steps you
can take to troubleshoot:
• Run diagnostics on your report and view the report summary at the end of the report. Look at the hcache
time to see how long it took to build.
• Check your log rates to get an idea of log volumes.
• Check the insert rate, receive rate, and the log insert lag. They can tell you the rate at which raw logs are
reaching FortiAnalyzer (receive rate) and the rate at which they are indexed by the SQL database (insert
rate) by the sqlplugind daemon. The log insert lag time tells you how many seconds the database is behind
in processing the logs.
• Enable auto-cache in the report settings to boost the reporting performance and reduce report generation
time. Scheduled reports have auto-cache enabled already.
ChatGPT a dit :
Merci pour cet extrait officiel de la documentation Fortinet — il confirme clairement que la bonne réponse à la question est :
❓ Which two steps can you take to troubleshoot slow report generation?
(Choose two answers)
✅ Réponses correctes :
B. Review report diagnostics
C. Enable auto-cache and run the reports again
📚 Justification à partir de la documentation que tu as fournie :
✅ B. Review report diagnostics
"Run diagnostics on your report and view the report summary at the end of the report. Look at the hcache time to see how long it took to build."
→ Cela confirme que l’analyse des diagnostics du rapport est essentielle pour identifier les lenteurs.
✅ C. Enable auto-cache and run the reports again
"Enable auto-cache in the report settings to boost the reporting performance and reduce report generation time."
→ L’auto-cache permet de réutiliser les données indexées au lieu d’analyser les logs bruts à chaque fois, ce qui améliore fortement les performances.
❌ Pourquoi les autres réponses sont incorrectes :
A. Increase the ADOM reports quota
Cela n’accélère pas la génération des rapports.
Ça permet juste d’augmenter l’espace disque disponible pour stocker les rapports.
D. Remove old reports from the hcache
Effacer la hcache ralentit la génération future des rapports qui pourraient réutiliser les données mises en cache.
✅ Réponse finale confirmée :
B. Review report diagnostics
C. Enable auto-cache and run the reports again
Run diagnostics on your report and view the report summary at the end of the report. Look at the hcache
time to see how long it took to build.
• Check your log rates to get an idea of log volumes.
• Check the insert rate, receive rate, and the log insert lag. They can tell you the rate at which raw logs are
reaching FortiAnalyzer (receive rate) and the rate at which they are indexed by the SQL database (insert
rate) by the sqlplugind daemon. The log insert lag time tells you how many seconds the database is behind
in processing the logs.
• Enable auto-cache in the report settings to boost the reporting performance and reduce report generation
time. Scheduled reports have auto-cache enabled already. page 181
You discover that a few reports are taking a long time to generate. Which two steps can you take to troubleshoot? (Choose two answers)
Brave-Dump Clients Votes