Question 510
A partner user loses administrator approval but a long-running API token continues to authorize the previous permission level. Most decisive verification?
Explanation
Correct Answer
“Compare new permissions, active sessions, app policies and denied legacy actions” distinguishes sign-in from entitlement administration in a partner user loses administrator approval but a long-running API token continues to authorize the previous permission level It checks whether reconcile entitlement changes and verify effective session or token behavior after role removal.
Incorrect Answers
“Test revoked session, refresh-token rejection, user activity records and alternate devices” needs to be evaluated against A partner user loses administrator approval but a long-running API token continues to authorize the previous permission level. The relevant check is Compare new permissions, active sessions, app policies and denied legacy actions; Updating directory membership is not always equivalent to promptly revoking application-side access.
“Test state mismatch, invalid verifier, exposed-token handling and safe support logs” needs to be evaluated against A partner user loses administrator approval but a long-running API token continues to authorize the previous permission level. The relevant check is Compare new permissions, active sessions, app policies and denied legacy actions; Updating directory membership is not always equivalent to promptly revoking application-side access.
“Validate external client app policies, token grants, permission sets and denied requests” needs to be evaluated against A partner user loses administrator approval but a long-running API token continues to authorize the previous permission level. The relevant check is Compare new permissions, active sessions, app policies and denied legacy actions; Updating directory membership is not always equivalent to promptly revoking application-side access.