Question 10
What does this observation indicate about a Splunk Enterprise deployment? A consultant revokes a capability required by a service report but fails to assess downstream reports.
Explanation
Correct Answer
Authorization changes can disrupt existing dependent workloads even when the new policy is correct. This technical distinction is illustrated by: A consultant revokes a capability required by a service report but fails to assess downstream reports. The recommended operational decision is: Regression-test saved searches, knowledge objects, and scheduled jobs after role changes. Evidence should show: Approved dashboards and reports continue under the intended execution context while removed privileges stay inaccessible.
Incorrect Answers
This statement maps to A customer wants all Splunk components to delegate UI authentication to a directory but has not decided how authorization roles map. The consultant should distinguish that context from the present one, because authorization changes can disrupt existing dependent workloads even when the new policy is correct.
That explanation belongs to another deployment context: A newly created role combines two parent roles and unexpectedly inherits a sensitive feature. Its underlying rule is: Inherited capabilities and index grants can expand effective access beyond the intended role definition. The current case instead illustrates: Authorization changes can disrupt existing dependent workloads even when the new policy is correct.
That explanation belongs to another deployment context: A SAML assertion is accepted but the returned groups do not match authorized Splunk roles. Its underlying rule is: Federation proves identity through trusted assertions, while permissions rely on explicit mapping of the intended attributes. The current case instead illustrates: Authorization changes can disrupt existing dependent workloads even when the new policy is correct.