Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Experience Cloud Consultant Topic 2 Question 77 Discussion

Actual exam question for Salesforce's Experience Cloud Consultant exam
Question #: 77
Topic #: 2
[All Experience Cloud Consultant Questions]

Cloud Kicks (CK) has built a site using Salesforce Experience Builder. The CTO of CK wants to give customers the ability to log in to the site using their Google credentials. CK also wants to access customers' basic Google profile data when they log in so the company can serve content that matches customers' interests.

Mow should the Experience Cloud consultant implement this?

Show Suggested Answer Hide Answer
Suggested Answer: C

This option allows CK to use Google as an external identity provider and enable customers to log in to the site using their Google credentials. CK can also access customers' basic profile data, such as name, email, and picture, by specifying the scopes and attributes in the authentication provider settings. CK can also use the authentication provider to configure single sign-on (SSO) and just-in-time (JIT) provisioning for the site.


Contribute your Thoughts:

Aleta
3 months ago
Haha, the CTO must be really eager to get those customer profiles! I'd go with Option C, but I'd also ask about the data privacy implications.
upvoted 0 times
...
Clay
3 months ago
I think Option A is the easiest solution, but it might not give you as much flexibility in terms of accessing the customer data. Option C seems like the most robust approach.
upvoted 0 times
Clarence
1 months ago
A) Option A is easier to set up, but Option C provides more robust access to customer data.
upvoted 0 times
...
Chu
2 months ago
C) Create an Authentication Provider by choosing Google as the provider type and add relevant parameters to access the customers' basic profile data.
upvoted 0 times
...
Larae
2 months ago
A) Set up a login flow for communities that accepts the customers' Google credentials and matches with the credentials stored on the user records in Salesforce.
upvoted 0 times
...
...
Cassandra
3 months ago
I'm not sure about option C. I think option A could also work well by setting up a login flow for communities that accepts Google credentials and matches with user records in Salesforce.
upvoted 0 times
...
Rima
3 months ago
I agree with Teresita. Option C sounds like the most efficient solution for integrating Google credentials and accessing customer data.
upvoted 0 times
...
Diane
3 months ago
Hmm, I'm leaning towards Option D. Using Lightning components and the Google REST API seems like a more flexible solution that gives you more control over the user experience.
upvoted 0 times
...
Teresita
3 months ago
I think option C is the best choice. Creating an Authentication Provider with Google as the provider type seems like the most straightforward way to access customers' basic profile data.
upvoted 0 times
...
Pansy
3 months ago
Option C is the way to go! Creating an Authentication Provider with Google is the most straightforward approach to implement the required functionality.
upvoted 0 times
Kandis
1 months ago
C) Create an Authentication Provider by choosing Google as the provider type and add relevant parameters to access the customers' basic profile data.
upvoted 0 times
...
Alverta
2 months ago
A) Set up a login flow for communities that accepts the customers' Google credentials and matches with the credentials stored on the user records in Salesforce.
upvoted 0 times
...
Lyndia
2 months ago
C) Create an Authentication Provider by choosing Google as the provider type and add relevant parameters to access the customers' basic profile data.
upvoted 0 times
...
Raul
3 months ago
A) Set up a login flow for communities that accepts the customers' Google credentials and matches with the credentials stored on the user records in Salesforce.
upvoted 0 times
...
Maybelle
3 months ago
C) Create an Authentication Provider by choosing Google as the provider type and add relevant parameters to access the customers' basic profile data.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77