An administrator modified a configuration setting in the Global System Notifications using the QRadar Console Admin tab. What is the last step to apply changes?

Question

Options

• AReload Web Server
• BRestart Services
• CRe-login to QRadar console
• DDeploy Changes

• B
  4% (1)
• C
  4% (1)
• D
  92% (22)

Explanation

Deploy Changes (D) is correct because QRadar uses a staged configuration model - changes made in the Admin tab are queued but not active until you explicitly click Deploy Changes, which pushes the updated configuration out to all managed hosts and components in the deployment.

• A (Reload Web Server) is wrong because reloading the web server only refreshes the UI layer; it does not propagate configuration changes to the QRadar pipeline or managed hosts.
• B (Restart Services) is wrong because while restarting services can resolve some issues, it is not the proper mechanism for applying Admin tab configuration changes and could cause unnecessary downtime.
• C (Re-login) is wrong because logging out and back in only refreshes your session - it has no effect on system-level configuration deployment.

Memory tip: Think of the Admin tab as a "draft" editor - every change you make is a draft until you hit Deploy Changes, which is QRadar's equivalent of "publish." If you skip Deploy, your changes exist only on paper.

No community discussion yet for this question.