Question 0260 — Accepting Third-Party Identity in Salesforce
At fictional Meadow Point Software 26B, the team managing Experience Cloud customer authentication reports: The partner lifecycle team wants an HR-driven provision-before-login flow, but the portal architect proposes JIT exclusively without support for timely deprovisioning. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Audit partner joiner-mover-leaver synchronization against the source directory. This recurring control addresses the observed problem: The partner lifecycle team wants an HR-driven provision-before-login flow, but the portal architect proposes JIT exclusively without support for timely deprovisioning. The measurable check is: Simulate join, change and terminate events, measuring Salesforce account-state convergence against agreed controls.
Incorrect Answers
Monitor creation errors, duplicate identities, and provisioning-role grants during partner growth. Audit partner joiner-mover-leaver synchronization against the source directory.
Run full SP-initiated login and destination validation after reverse-proxy or gateway changes. Audit partner joiner-mover-leaver synchronization against the source directory.
Include suspended and terminated users in JIT handler negative testing. Audit partner joiner-mover-leaver synchronization against the source directory.