Question 250
A customer service SaaS platform provisions roles through automation. Observed: An API job grants a default broad role when the identity department supplies an unknown group. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: An unknown test group receives no elevated access and triggers a provisioning alert. It provides case-specific verification that the observed behavior (An API job grants a default broad role when the identity department supplies an unknown group) has changed appropriately.
Incorrect Answers
The proposed signal relates to: Splunk accepts a SAML response from the wrong identity provider after stale trust metadata is left active. The evidence for this Splunk source case must instead show: An unknown test group receives no elevated access and triggers a provisioning alert.
The distractor measures “Test users authenticate through LDAP and logs show successful directory lookup”. This verifies a separate correction, “Correct LDAP connection and bind search configuration according to the directory design”, for the fault “Users can authenticate locally but enterprise LDAP credentials fail because bind configuration targets the wrong directory endpoint” and the cause “LDAP search and bind settings determine whether external identities can be resolved”. The stated fault, however, is “An API job grants a default broad role when the identity department supplies an unknown group”, which points to “Unrecognized identity mappings should fail closed rather than grant elevated privileges”. Check “An unknown test group receives no elevated access and triggers a provisioning alert” after “Require an allowlisted role map and flag unmapped groups for manual resolution” to determine whether this incident was resolved.
This result checks another issue, for which the observed symptom is: The directory bind fails because the certificate chain is not trusted on the Splunk server. It does not verify recovery for this situation: An API job grants a default broad role when the identity department supplies an unknown group. The relevant success check is: An unknown test group receives no elevated access and triggers a provisioning alert.