An administrator has been asked to configure a new QRadar console high availability (HA) deployment. Both the primary and secondary consoles have been installed with the QRadar software. What should…

Question

Options

• AAdd the secondary console to the deployment, and then create the HA host.
• BReinstall the QRadar software on the secondary console using an "HA Recovery Setup".
• CSelect "Secondary Host" on the wizard when adding the secondary host to the deployment.
• DCreate the HA host to add the secondary console to the deployment.

• A
  85% (40)
• B
  4% (2)
• C
  9% (4)
• D
  2% (1)

Explanation

Option A is correct because configuring QRadar console HA follows a two-step sequence: first you add the secondary console as a managed host in the deployment editor, and then you create the HA host by right-clicking the primary console - this is the documented IBM QRadar HA setup process.

Option B is wrong because no special "HA Recovery Setup" reinstallation is required; both consoles are installed with standard QRadar software before HA configuration begins. Option C is wrong because there is no "Secondary Host" wizard option when adding a host - the secondary system is added as a normal managed host first, with HA being configured as a separate subsequent step. Option D reverses the correct order - you cannot create the HA host before the secondary console exists in the deployment, so adding it to the deployment must come first.

Memory tip: Think "Add, then Activate" - you Add the secondary console to the deployment first, then Activate HA by creating the HA host. Order matters in QRadar HA: registration before redundancy.

No community discussion yet for this question.