IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 7 of 30
Universal Containers (UC) would like its community users to be able to register and log in with Linkedin or Facebook Credentials. UC wants users to clearly see Facebook &Linkedin Icons when they register and login. What are the two recommended actions UC can take to achieve this Functionality? Choose 2 answers
Full set: 248 questionsTo enable social sign-on with providers like Facebook and LinkedIn for a Salesforce Community, two key configurations are required. First, the authentication providers must be enabled and selected within the community's administration settings. This action makes the corresponding login buttons (icons) visible on the login and registration pages. Second, a registration handler is needed to manage the user provisioning process. When a user logs in for the first time via a social provider, this Apex class logic creates a new user record or links the social account to an existing one, ensuring proper user setup and data mapping.
C. The Federation ID field is primarily used for mapping users in SAML-based Single Sign-On, not for OAuth/OpenID Connect-based social sign-on, which uses a different linking mechanism.
D. Creating custom buttons and a custom Visualforce page is unnecessary and not recommended. Salesforce provides a standard, declarative feature to add social login buttons to the community login page.
1. Salesforce Help Documentation, "Add the Social Login Buttons to Your Login Page": This document details the process for making social login options visible. It states, "From Experience Workspaces, select Administration | Login & Registration. Under Login, you see the auth providers that you created. Select the ones that you want to appear on the community’s login page." This directly supports option A.
2. Salesforce Apex Developer Guide, Auth.RegistrationHandler Interface: This guide explains the role of the registration handler. It states, "Create an Apex class that implements the Auth.RegistrationHandler interface. The class, called the registration handler, handles the heavy lifting of creating Salesforce users, updating users, and linking to existing users, accounts, and contacts." This supports the necessity of a handler (option B) for managing user creation and linking during social sign-on.
3. Salesforce Identity and Access Management Architecture, B2C Scenarios (Architect.salesforce.com): In discussions of social sign-on patterns, the architecture guides emphasize the use of built-in Authentication Providers and the Registration Handler for custom logic, reinforcing that options A and B are the standard, recommended components for this solution. The guides do not recommend using Federation ID (option C) for this OAuth-based flow.
Keep practicing
Take the free IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice questions
- Question 2Universal Containers (UC) is planning to deploy a custom mobile app that will allow users…
- Question 3Universal containers (UC) is setting up Delegated Authentication to allow employees to lo…
- Question 4Universal Containers (UC) wants to use Salesforce for sales orders and a legacy of system…
- Question 5Universal containers (UC) is successfully using Delegated Authentication for their salesf…
- Question 6Universal Containers (UC) plans to use a SAML-based third-party IdP serving both of the S…
- Question 8Universal containers (UC) has an e-commerce website while customers can buy products, mak…
