Question 160
A university federates employee sign-in for Splunk. Observed: Users can authenticate locally but enterprise LDAP credentials fail because bind configuration targets the wrong directory endpoint. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Test users authenticate through LDAP and logs show successful directory lookup) to the original warning (Users can authenticate locally but enterprise LDAP credentials fail because bind configuration targets the wrong directory endpoint). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Browser redirects complete but Splunk rejects the assertion because the audience identifier is wrong. It does not detect the current warning: Users can authenticate locally but enterprise LDAP credentials fail because bind configuration targets the wrong directory endpoint. The necessary confirmation is: Test users authenticate through LDAP and logs show successful directory lookup.
This is an unrelated recovery test. It is connected to: Staff are assigned the power role in addition to the custom restricted role and gain excess commands. The present source situation requires: Test users authenticate through LDAP and logs show successful directory lookup.
The proposed check applies to: LDAP role mappings require an appropriate group search scope. The current failure was: Users can authenticate locally but enterprise LDAP credentials fail because bind configuration targets the wrong directory endpoint. Its validation must test: Test users authenticate through LDAP and logs show successful directory lookup.