Question 230
During a Splunk platform review, the team reports: At a payment services team during an approved staging exercise, reviewers observe the following: An enterprise wants central credentials but Splunk still uses local passwords for every employee. What should the administrator do first?
Explanation
Correct Answer
Configure supported LDAP authentication and map directory groups to least-privilege Splunk roles. It is preferable to the other interventions because LDAP integration delegates identity checks while Splunk roles still govern platform capabilities. The operational acceptance evidence is A directory test user signs in with the expected role, and revoked directory access is denied.
Incorrect Answers
This addresses an LDAP directory becomes temporarily unavailable and the organization assumes all login pathways should be disabled manually. rather than the stated case. The narrower corrective action is Configure supported LDAP authentication and map directory groups to least-privilege Splunk roles.
That action is aimed at another operational symptom: A Splunk LDAP integration fails only for users in nested groups, and administrators propose hard-coding new local accounts. The reported issue instead depends on this requirement: LDAP integration delegates identity checks while Splunk roles still govern platform capabilities. The expected validation is A directory test user signs in with the expected role, and revoked directory access is denied.
The option would apply to “At a retail distribution site during an endpoint rollout, reviewers observe the following: A privileged Splunk user account has password-only authentication although the organization requires a second factor”. Evaluate and enable a supported MFA or federated MFA approach with the identity team and tested recovery access. This question instead requires “Configure supported LDAP authentication and map directory groups to least-privilege Splunk roles”.