Salesforce Tableau Crm Einstein Discovery Consultant · Free Practice Question Medium
Question 17
An Einstein Consultant receives a new project from a client that wants to implement
Einstein Analytics. They do notcurrently have Einstein Analytics, but want guidance around
how to ensure that their users have correct access.
They have 1000 users with a small team of three people who will build datasets and
dashboards. An additional 15 people should be able to createdashboards. The remaining
users should only be able to view dashboards.
Which recommendation should the consultant give the client?
- A A. Create and assign Salesforce permission sets according to the three types of roles defined.
- B B. Assign the app permissions"viewer/' "editor," and "manager" to the three types of roles defined.
- C C. Create and assign three new Salesforce profiles according to the three types of roles defined.
- D D. Assign "Einstein Analytics Explorer" licenses to users that should only view
- E The dashboard, and assign "Einstein Analytics Developer" licenses to users that should be able to create datasets and dashboards.
Reveal correct answer
Correct answer: A
Explanation
For the scenario described, where the client is looking to implement Einstein Analytics with different levels of access for various user groups, the most appropriate recommendation would be: A. Create and assign Salesforce permission sets according to the three types of roles defined. Here's why this approach is suitable: Flexibility and Scalability: Permission sets in Salesforce are designed to give users access rights without changing their core profile. This approach offers flexibility, particularly in large organizations like the client's, with varied user needs. It allows for granular control over who can access what within Einstein Analytics. Three Distinct Roles: Given the three distinct roles described - a small team building datasets and dashboards, a larger group that can create dashboards, and a majority who only need view access - permission sets can be tailored to each group's specific needs. For example: For the small team (3 people) responsible for building datasets and dashboards, a permission set with full access to Einstein Analytics features (like creating and managing datasets, dashboards, apps, etc.) can be created. For the 15 users who need to create dashboards but not datasets, a more restricted permission set that allows dashboard creation and editing but not full dataset management can be assigned. For the remaining users, a permission set that only enables viewing of dashboards can be assigned. Avoiding Overuse of Profiles: Creating new Salesforce profiles (option C) for each role can lead to profile proliferation, making administration more complex. Profiles are more suited for defining a base level of access across the organization, while permission sets are ideal for layering additional access based on specific needs or roles. Licensing Considerations: While assigning specific licenses (option D) is a part of managing access, it doesn't fully address the different access levels required within Einstein Analytics. Licenses determine what features a user can access, but the permissions within those features are governed by permission sets and profiles. App Permissions: Although assigning app permissions (option B) like "viewer," "editor," and "manager" is a part of managing dashboard access within Einstein Analytics, this approach alone doesn't offer the comprehensive access control needed for different user groups as effectively as permission sets. So, creating and assigning tailored Salesforce permission sets to each of the three groups offers the most direct and effective way to ensure the correct level of access for each user in the context of Einstein Analytics implementation.Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
You must be logged in to post a comment.
