Salesforce-Platform-Identity-and-Access-Management-Architect Practice Test
Salesforce Spring 25 Release 255 Questions
Northern Trail Outfitters (NTO) is planning to roll out a partner portal for its distributors using Experience Cloud. NTO would like to use an external identity provider (idP) and for partners to register for access to the portal. Each partner should be allowed to register only once to avoid duplicate accounts with Salesforce.
What should a identity architect recommend to create partners?
A. On successful creation of Partners using Self Registration page in Experience Cloud, create identity in Ping.
B. Create a custom page m Experience Cloud to self register partner with Experience Cloud and Ping identity store.
C. Create a custom web page in the Portal and create users in the IdP and Experience Cloud using published APIs.
D. Allow partners to register through the IdP and create partner users in Salesforce through an API.
B. Create a custom page m Experience Cloud to self register partner with Experience Cloud and Ping identity store.
Explanation:
To create partners using an external identity provider (IdP) and avoid duplicate accounts with Salesforce, the identity architect should recommend creating a custom page in Experience Cloud to self register partner with Experience Cloud and Ping identity store. Ping is an IdP that supports OpenID Connect protocol, which allows users to sign in with an external identity provider and access Salesforce resources. By creating a custom page in Experience Cloud, the identity architect can use a custom registration handler to link the partner’s Ping identity with their Salesforce identity and prevent duplicate accounts. The custom page can also provide a seamless user experience for the partners.
Reference:
OpenID Connect Authentication Providers, Social Sign-On with OpenID Connect, Create a Custom Registration Handler