Question 960
A Splunk platform team observes this behavior: An LDAP directory becomes temporarily unavailable and the organization assumes all login pathways should be disabled manually. Which technical principle best explains the issue?
Explanation
Correct Answer
Authentication provider outages require controlled failover or break-glass planning, not ad hoc permission changes. This explains why the administrator should check the configured authentication behavior and documented recovery procedures without bypassing access controls. A direct test would be: A rehearsal shows only authorized recovery identities can administer the instance during the outage.
Incorrect Answers
The option would apply to “An enterprise wants central credentials but Splunk still uses local passwords for every employee”. The controlling mechanism is that LDAP integration delegates identity checks while Splunk roles still govern platform capabilities. This question instead requires “Authentication provider outages require controlled failover or break-glass planning, not ad hoc permission changes”.
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, “Authentication provider outages require controlled failover or break-glass planning, not ad hoc permission changes” addresses the central condition.
This option serves the scenario “An administrator assumes that enabling MFA at a corporate identity provider automatically covers every local Splunk account”. Federated MFA does not necessarily enforce a second factor for independent local authentication paths. The present scenario is distinguished by “Authentication provider outages require controlled failover or break-glass planning, not ad hoc permission changes”.