C1000-026 · Question #15
An ip_context_menu.xml plug-in was created to assist in finding additional details for selected lP addresses. Where must this file be placed so the plug-in can be used?
The correct answer is C. /opt/qradar/conf. Option C (/opt/qradar/conf) is correct because IBM QRadar looks in the conf directory for custom XML configuration files, including context menu plugins like ip_context_menu.xml. This directory is where QRadar reads plugin definitions that extend the UI's right-click context…
Question
An ip_context_menu.xml plug-in was created to assist in finding additional details for selected lP addresses. Where must this file be placed so the plug-in can be used?
Options
- A/opt/qradar/init
- B/opt/qradar/bi n
- C/opt/qradar/conf
- D/opt/qradar/webplugins
How the community answered
(25 responses)- A4% (1)
- B16% (4)
- C72% (18)
- D8% (2)
Explanation
Option C (/opt/qradar/conf) is correct because IBM QRadar looks in the conf directory for custom XML configuration files, including context menu plugins like ip_context_menu.xml. This directory is where QRadar reads plugin definitions that extend the UI's right-click context menu functionality for IP addresses.
Why the distractors are wrong:
- A (
/opt/qradar/init) - This directory contains initialization/startup scripts, not plugin configuration files. - B (
/opt/qradar/bin) - This holds QRadar executables and binaries, not XML configuration files. - D (
/opt/qradar/webplugins) - While this sounds plausible for UI extensions, it is not the correct path QRadar scans for context menu XML definitions; this directory serves a different purpose in the QRadar architecture.
Memory tip: Think "conf = configuration" - XML files configure how QRadar behaves (like adding menu items), so they belong in the conf directory, not in runtime (bin), startup (init), or the broader web plugin directory.
Topics
Community Discussion
No community discussion yet for this question.