Question 0430 — Salesforce as an Identity Provider
At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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 outbound callout credential mappings and principal permissions on a schedule. This recurring control addresses the observed problem: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. The measurable check is: Trace a test callout using the approved credential principal with no reusable password in application code or logs.
Incorrect Answers
Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Review outbound callout credential mappings and principal permissions on a schedule.
Rotate integration credentials and review non-interactive principal scope during service ownership changes. Review outbound callout credential mappings and principal permissions on a schedule.
Reapprove connected-app scope sets during each API integration feature expansion. Review outbound callout credential mappings and principal permissions on a schedule.