Question 0080 — Identity Management Concepts
At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Review token lifetimes, revocation propagation and incident runbooks across all connected applications. This recurring control addresses the observed problem: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. The measurable check is: Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.
Incorrect Answers
Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.
Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.
Reconcile permission assignments to authoritative role events on a recurring least-privilege review. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.