The CRM Analytics consultant at Universal Containers notices that some users have access to sensitive data and dashboards they should not have access to in the Manager's app.
How should the consultant fix the problem?
Answer : C
To address issues with unauthorized access to sensitive data and dashboards, the best practice is to create separate apps, datasets, and dashboards for different user groups and then manage their sharing settings appropriately. This allows you to maintain data security while ensuring that users only access the data and insights that are relevant to their roles. In this scenario, applying separate apps for managers with defined sharing rules will prevent users who shouldn't have access from seeing sensitive data. Reference: Managing Data Access and Sharing in CRM Analytics
Universal Containers has a dashboard for sales managers. They need to visualize the percentage of their opportunities in the pipeline in a Gauge chart. They want to customize the chart to keep track if they are below or beyond the target.

Which widget parameters should a consultant use?
Answer : C
In the scenario described, the sales managers at Universal Containers require a Gauge chart that not only shows the current percentage of opportunities in their pipeline but also indicates whether they are below or beyond their set targets. The appropriate widget parameters to achieve this visualization in Salesforce CRM Analytics (formerly known as Einstein Analytics) are:
Reference Line: This parameter is crucial for defining a specific target value on the gauge chart. It visually marks a point that represents the target goal, providing an immediate visual cue as to whether the current percentage is below or above this point.
Markers: Markers are used to represent and highlight specific values on the gauge chart. They can be utilized to emphasize the current percentage level of the pipeline, making it instantly visible how close or far the current value is from the reference line or target.
Conditional Formatting: This feature allows the chart to change color or style based on whether the current values meet, exceed, or fall below the target. It is a critical visual tool for quickly communicating performance against targets. Conditional formatting can be set to alter the appearance of the gauge's fill color based on whether the values are above, equal to, or below the reference line, thereby providing an intuitive visual representation of performance relative to targets.
The combination of these three parameters enables a highly effective visualization for sales managers to monitor their performance against key metrics and targets directly on their dashboards. This setup is aligned with Salesforce's best practices for creating meaningful and actionable insights within CRM dashboards, ensuring that users can easily interpret and react to the data presented.
For more details on configuring these parameters, you can refer to Salesforce documentation and specific Trailhead modules that cover dashboard creation and customization:
Wave Analytics Explorer
Building Lenses, Dashboards, and Apps in CRM Analytics
These resources provide in-depth training and examples to help users effectively use Salesforce CRM Analytics for a wide range of data visualization needs.
A versioning feature allows CRM Analytics users to be added as Publishers and make changes separately while a 'Live' version is still being used by other users. Once the changes are complete, the user can then set their updated version as the Live version.
Which CRM Analytics item is this leveraged for?
Answer : A
In CRM Analytics, the versioning feature described is typically leveraged for Apps. This feature allows:
Parallel Development: Users can work on changes in a separate version without affecting the live version being accessed by others.
Controlled Publishing: Once changes are finalized, the user can then promote their version to be the new live version, ensuring seamless updates without disrupting ongoing usage.
Collaborative Workflows: Facilitates teamwork by allowing multiple users to propose and test changes in a controlled environment before making those changes live.
This approach ensures that CRM Analytics apps remain dynamic and can evolve over time while maintaining stability and continuity for end-users.
Universal Containers (UC) builds three Einstein Discovery models in Salesforce to predict and maximize its revenue per customer. The models are for every region UC has a business: EMEA, AMER, and APAC.
How should a consultant help UC deploy the three Einstein models to Salesforce?
Answer : B
In deploying Einstein Discovery models that are tailored to different regions (EMEA, AMER, and APAC), the best approach is to segment the account data by region and apply the specific model designed for each segment. This method ensures the following:
Relevance and Accuracy: Each model can be specialized to understand and predict based on regional dynamics, which may differ significantly across geographies in terms of market behavior, customer preferences, and economic conditions.
Efficiency: Deploying region-specific models avoids the dilution of predictive power that might occur if a single model were used across all regions, which could lead to less accurate predictions.
Scalability: This approach is scalable as UC can further refine each model as more regional data becomes available or as regional market conditions evolve.
Universal Containers' CRM Analytics team is building a dashboard with two widgets.
1. List widget associated to the query "Type_2" and grouped by the dimension "Type" (multi-selection)
2. Donut chart widget associated to the query "Step_pie_3" and grouped by the dimension "Type"
The team wants to use bindings/interactions so any selection in the List widget will filter the Donut chart. The queries use different datasets,
and users should be able to choose more than one Type (multi-selection).
What is the right syntax for the binding/interaction?
A)

B)

C)

Answer : A
For the given requirement where a selection in a list widget needs to filter data displayed on a donut chart, and considering the list allows for multi-selection of the 'Type', the correct binding/interaction would be to use a syntax that captures the multi-select aspect and passes it appropriately. The right syntax, as indicated in Option A, looks like this:
'{{column(Type_2.selection, [\'Type\']).asObject()}}'
This syntax ensures:
Multi-selection: The column() function in combination with .asObject() ensures that multiple selected values from the 'Type_2' query can be passed as an object, which the donut chart can utilize to filter its content.
Correct Data Type Handling: By using .asObject(), the binding ensures the data passed between widgets maintains the correct structure expected by the CRM Analytics dashboard, thereby ensuring accurate filtering.
Cloud Kicks (CK) has a dashboard that is still showing 10 former account managers. CK has since expanded, and some have moved from their former roles. CK wants the dashboard to reflect current account managers and stay up to date as new team members join.
How should the CRM Analytics developer accomplish this?
Answer : A
The Repeater Widget in CRM Analytics allows dynamic updates to be reflected on the dashboard automatically as data flows are updated. This means that as new account managers join or existing account managers change roles, the data in the widget will automatically reflect the latest information without manual updates. This is the most efficient way to keep the dashboard up-to-date with the current list of account managers.
CRM Analytics team is asked to build a Service Analytics dashboard for the service agents.
What are the main "Deep Design Thinking" principles the team should keep in mind during the discovery sessions?
Answer : A