Question 220
A charity runs authentication through LDAP over TLS. Observed: The directory bind fails because the certificate chain is not trusted on the Splunk server. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Directory connectivity succeeds with certificate validation enabled) to the original warning (The directory bind fails because the certificate chain is not trusted on the Splunk server). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Unrecognized identity mappings should fail closed rather than grant elevated privileges. The current failure was: The directory bind fails because the certificate chain is not trusted on the Splunk server. Its validation must test: Directory connectivity succeeds with certificate validation enabled.
This is an unrelated recovery test. It is connected to: Splunk accepts a SAML response from the wrong identity provider after stale trust metadata is left active. The present source situation requires: Directory connectivity succeeds with certificate validation enabled.
That gate watches a different case: Staff are assigned the power role in addition to the custom restricted role and gain excess commands. It does not detect the current warning: The directory bind fails because the certificate chain is not trusted on the Splunk server. The necessary confirmation is: Directory connectivity succeeds with certificate validation enabled.