When you move a FortiGate device from one ADOM to a new ADOM, what is the purpose of rebuilding the new ADOM database?

Question

Options

• ATo migrate the archive logs to the new ADOM
• BTo run reports on the device's analytics logs in the new ADOM
• CTo remove the device's analytics logs from the old ADOM
• DTo reset the disk quota enforcement to default

• A
  11% (2)
• B
  84% (16)
• D
  5% (1)

Explanation

When a FortiGate is moved to a new ADOM in FortiAnalyzer, its analytics logs (the compressed, indexed log data used for reporting) are not automatically available in the new ADOM - rebuilding the new ADOM's database indexes those analytics logs so that reports can be generated against that device's data in its new home. Option A is wrong because archive logs (raw, uncompressed logs stored for retention/compliance) are a separate log tier and are not migrated via a database rebuild. Option C is wrong because the rebuild operation acts on the new ADOM, not the old one - removing or cleaning up the old ADOM's data is a distinct, unrelated action. Option D is wrong because disk quota enforcement is a storage management setting, completely unrelated to the log-indexing purpose of a database rebuild.

Memory tip: Think "Rebuild = Ready to Report." The rebuild makes the device's analytics logs readable (reportable) inside the new ADOM - without it, the new ADOM has the device but can't run reports on its history.

No community discussion yet for this question.