Question 680
During handover, the following concern is raised: A consultant points Splunk to the directory but leaves user and group search bases mismatched. Which evidence would demonstrate proper control?
Explanation
Correct Answer
A representative user authenticates and receives exactly the intended Splunk roles from directory groups. This outcome directly confirms the control associated with directory authentication and role resolution depend on correct queries and mapping rules rather than connectivity alone. The original concern was: A consultant points Splunk to the directory but leaves user and group search bases mismatched. The required implementation is: Validate LDAP bind, user search base, group search base, and group-to-role mappings separately.
Incorrect Answers
That result would support a successful identity check does not grant capabilities or unrestricted data access without appropriate role mapping. in a scenario such as An integration supplies successful LDAP passwords but users receive unintended access to security indexes. The present case should be validated according to directory authentication and role resolution depend on correct queries and mapping rules rather than connectivity alone.
That result would support LDAP filter and base settings must include intended principals without accidentally broadening access to unrelated accounts. in a scenario such as A customer has two directory trees and the Splunk LDAP search only covers one of them. The present case should be validated according to directory authentication and role resolution depend on correct queries and mapping rules rather than connectivity alone.
The alternative observation measures a separate technical dependency: A Splunk installation has LDAP, SAML, and local accounts but the architecture document never explains which principal types use which method. The current incident requires evidence tied to directory authentication and role resolution depend on correct queries and mapping rules rather than connectivity alone.