Question 260
The Splunk Enterprise administrator is asked to explain: An enterprise wants central credentials but Splunk still uses local passwords for every employee. Which statement captures the underlying mechanism?
Explanation
Correct Answer
The controlling mechanism is that LDAP integration delegates identity checks while Splunk roles still govern platform capabilities. Resolve the problem by configure supported LDAP authentication and map directory groups to least-privilege Splunk roles. Then validate with: A directory test user signs in with the expected role, and revoked directory access is denied.
Incorrect Answers
The option would apply to “An LDAP directory becomes temporarily unavailable and the organization assumes all login pathways should be disabled manually”. Authentication provider outages require controlled failover or break-glass planning, not ad hoc permission changes. This question instead requires “LDAP integration delegates identity checks while Splunk roles still govern platform capabilities”.
The related but distinct situation is “A Splunk LDAP integration fails only for users in nested groups, and administrators propose hard-coding new local accounts”. Directory group lookup and role assignment failures are distinct from user password failures. For the stated problem, “LDAP integration delegates identity checks while Splunk roles still govern platform capabilities” addresses the central condition.
This alternative addresses the separate case “A password-policy review treats the Splunk local user database as the authoritative directory for all SSO accounts”. Federated authentication policies are managed with the identity provider and are not identical to local credentials. The deciding requirement here is “LDAP integration delegates identity checks while Splunk roles still govern platform capabilities”.