Question 200
A telecommunications provider limits admin API access. Observed: Read-only analysts can invoke privileged REST endpoints because a custom role includes excessive capabilities. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The denied privileged API call is logged and ordinary search functions still work) to the original warning (Read-only analysts can invoke privileged REST endpoints because a custom role includes excessive capabilities). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: Every analyst inherits the admin role because an LDAP group mapping is too broad. The present source situation requires: The denied privileged API call is logged and ordinary search functions still work.
That gate watches a different case: Emergency credentials use the same SAML-only path as normal accounts and fail during IdP outage. It does not detect the current warning: Read-only analysts can invoke privileged REST endpoints because a custom role includes excessive capabilities. The necessary confirmation is: The denied privileged API call is logged and ordinary search functions still work.
The proposed check applies to: Default index selection influences query scope and can expose unintended data. The current failure was: Read-only analysts can invoke privileged REST endpoints because a custom role includes excessive capabilities. Its validation must test: The denied privileged API call is logged and ordinary search functions still work.