A QRadar deployment professional was asked to plan a system migration from an on-premises, appliance-based environment to an AWS environment. As part of this transition, the Ariel data must be moved to the new logical appliances and must be searchable by using the existing mechanisms (for example, to filter by log source).
Which approach can the deployment professional use to migrate the configuration after the VM is built (and before the Ariel data is restored)?
To ensure a seamless migration of the QRadar system to an AWS environment while maintaining searchable Ariel data, the QRadar configuration backup and restore process should be utilized. This approach preserves all configurations, including the necessary database IDs, ensuring that the data remains searchable in the new environment with existing mechanisms such as filtering by log source.
B seems most likely to me. CMT will not preserve database IDs and therefore data will not be searchable on new system. Config backup/restore will preserve the IDs