Question 750
A Splunk platform team observes this behavior: A privileged Splunk user account has password-only authentication although the organization requires a second factor. Which technical principle best explains the issue?
Explanation
Correct Answer
Multifactor authentication adds a verification step that should cover privileged sign-ins without locking out support staff. This explains why the administrator should evaluate and enable a supported MFA or federated MFA approach with the identity team and tested recovery access. A direct test would be: A test administrator must supply the approved second factor and the break-glass process is documented.
Incorrect Answers
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 “Multifactor authentication adds a verification step that should cover privileged sign-ins without locking out support staff”.
This alternative addresses the separate case “A security team turns on new MFA enforcement without enrollment instructions or emergency access design”. Unplanned factor enforcement can lock out the people required to restore an instance. The deciding requirement here is “Multifactor authentication adds a verification step that should cover privileged sign-ins without locking out support staff”.
The option would apply to “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. This question instead requires “Multifactor authentication adds a verification step that should cover privileged sign-ins without locking out support staff”.