Question 0360 — Salesforce as an Identity Provider
At fictional Meadow Point Software 36B, the team managing relying application federation reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Reapprove connected-app scope sets during each API integration feature expansion. This recurring control addresses the observed problem: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. The measurable check is: Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
Incorrect Answers
Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Reapprove connected-app scope sets during each API integration feature expansion.
Reconcile registered apps, scopes and named owners to the enterprise application inventory. Reapprove connected-app scope sets during each API integration feature expansion.
Rehearse My Domain issuer and metadata rollovers with every external service provider. Reapprove connected-app scope sets during each API integration feature expansion.