An administrator needs to add, delete and modify user accounts. When deleting a user, what dependency checks are carried out?

Question

Options

• ACustom Rules, Historical Correlation Profiles, Security Profiles
• BCustom Rules, Report and Search Criteria, Security Roles
• CCustom Rules, Security Profiles, Report and Search Criteria
• DCustom Rules, Report and Search Criteria, Historical Correlation Profiles

• A
  10% (5)
• B
  2% (1)
• C
  4% (2)
• D
  84% (43)

Explanation

Option D is correct because when deleting a user account in systems like IBM QRadar, the platform performs dependency checks specifically against Custom Rules, Report and Search Criteria, and Historical Correlation Profiles - all artifacts that may reference or be owned by that user, which would break or become orphaned if the account were deleted without resolution.

Why the distractors fail:

• A includes Security Profiles instead of Report and Search Criteria - Security Profiles are assigned to users, not dependent on them, so they don't trigger a dependency warning at deletion.
• B includes Security Roles instead of Historical Correlation Profiles - Security Roles are permissions structures, not user-linked analytical artifacts.
• C swaps out Historical Correlation Profiles for Security Profiles - again, Security Profiles are not checked as dependencies during deletion.

Memory tip: Think "What did this user create or contribute to analytically?" - Custom Rules they wrote, Searches/Reports they saved, and Correlation Profiles built from their history. Security Profiles and Roles are assigned to users (and simply unassign on deletion), not dependent on them, so they're never in the dependency check list.

No community discussion yet for this question.