Tableau-CRM-and-Einstein-Discovery-Consultant Sample Questions Answers

To access Einstein Analytics (now known as Tableau CRM), having just an Einstein Analytics Platform license is not sufficient. Users also require specific permissions to use analytics functionalities. The critical permission is "Use Analytics," which should be granted via a permission set. Without this permission, users can't access or use Tableau CRM, even if they have the necessary license.

In Salesforce Tableau CRM, the limit on the number of queries that a user can execute per day is set to 50,000. This is designed to ensure optimal performance across the platform while providing sufficient capacity for users to carry out extensive data analysis throughout the day.

Before users can access Analytics in Salesforce, they need two things: an Analytics permission set license (PSL) and a permission set containing at least one Analytics user permission. The PSL enables access to the Analytics functionality at a license level, while the permission set defines what specific actions the user is authorized to perform within Analytics.

In Salesforce, access to data can be configured at several levels, including Organization, Records, and Objects. However, Page Layouts is not a level at which access to data is configured. Page Layouts determine the arrangement of fields, related lists, and other elements on a record's page but do not control data access or security settings. Access controls are managed through settings at other specified levels such as profiles, roles, and sharing rules. Reference: Salesforce Help - Data Security

To address the requirement where some users need to create their own dashboards and others only need to use them, the best practice is to:

• A: Create two permission sets with different system permissions. One permission set would grant capabilities necessary for creating and managing dashboards, likely including permissions like "Create Dashboard," "Edit Dashboard," etc. The other permission set would grant only "View" permissions, restricting users to dashboard usage without modification capabilities.

Based on the "Why it Happened" graphic: A. Germany performs lower than average but better when the product is Call Center. This interpretation is supported by the presence of the Call Center product in Germany as a factor that increases the probability of Opportunity Won, contrary to its general performance. D. Germany sells more Call Center product and that helps them increase their win rate. The graph indicates that Call Center products have a positive impact in Germany on the win rate, suggesting that the higher sales volume of this product helps improve overall performance in the region.These insights are derived from understanding the visualization in the context of what contributes positively and negatively to the outcomes, which is a key feature of Einstein Analytics. Reference: Einstein Discovery Insights

The maximum number of concurrent API Analytics calls per organization in Salesforce Tableau CRM is 200. This limit helps to ensure that the system can handle multiple API requests efficiently without degrading the performance for users across the organization.

The configuration wizard in Salesforce Tableau CRM Einstein Discovery asks questions about various measurements that are critical for understanding and analyzing customer interactions and service effectiveness, which include:

• A: Case duration
• B: Customer geography
• C: Customer satisfaction
• D: Case resolution
• E: All of the above

To build a table in a Sales Manager dashboard and include a summary as the first line in a compare table:

• A: Use the Show Summary option in the compare table. This feature automatically calculates and displays a summary row at the top of the compare table, providing an aggregated view of the data points included in the table.

In Salesforce Tableau CRM, selecting the correct root object when using the dataset builder is crucial because the root object determines what related objects can be added to the dataset. The root object sets the base or primary focus of your dataset, and its relationships define the scope of additional data that can be included through joins and links to other Salesforce objects. Selecting an inappropriate root object might restrict the range of data that can be effectively utilized or require complicated workarounds to incorporate necessary related data. Reference: Salesforce Help - Selecting the Right Root Object

Insights categorized as 'Unrelated' in Einstein Discovery are significant because they highlight factors or variables that, while not directly related to the primary variables of interest, may still influence the outcome through broader or global effects. These insights help in understanding the comprehensive landscape of the data, acknowledging that some influencing factors might be external or less obvious yet impactful. This broader view aids in a more holistic analysis and prevents oversight of potential influences outside the immediate dataset. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_edd_insights_unrelated.htm &type=5

An Analytics app in Salesforce is a collection of datasets, dashboards, lenses, and a dataflow. These components are bundled together within an app to provide a comprehensive analytics solution tailored to specific business needs or project requirements. The app facilitates organized access to related analytics assets, making it easier for users to navigate and utilize data for decision-making and insights. Reference: Salesforce Help - Understanding Analytics Apps

The appropriate action when Einstein Discovery surfaces an unexpected pattern is to determine if the pattern is a data issue or a new insight. This approach involves verifying the integrity and accuracy of the data, and understanding whether the pattern represents a meaningful insight into the business operations or an anomaly caused by data issues.

Save changes to existing dashboards, lenses, and datasets in the app (saving dashboards requires the appropriate permission set license and permission) available in Editor and Manager*##**##*

In Salesforce Tableau CRM, the number of concurrent queries that a user can execute is capped at 20. This limit is designed to manage the load on the analytics platform effectively, ensuring stable and responsive performance across the user base.

To optimize data loads by extracting Salesforce objects ahead of time, the correct construct to use is "Data Sync (Replication)." This feature in Salesforce Einstein Analytics allows for the periodic refresh of datasets from Salesforce objects without needing to rerun the entire dataflow. This optimization helps in managing large datasets more efficiently by keeping the data up-to-date with less processing time and system load.

In the configuration wizard of Tableau CRM apps, required fields or questions without default values are typically indicated by the system to guide the setup process. By proceeding with the configuration ("Looks good, next"), the wizard will highlight any mandatory questions that have not been answered, usually by marking them in red. This visual cue allows users to easily identify and address the required inputs that are missing defaults, ensuring that essential configurations are not overlooked during setup. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_apps_configure.htm &type=5

In Tableau CRM, recipes allow users to create new datasets from various sources. The sources that can be utilized include:

• A. Existing datasets: Recipes can combine or transform data from datasets that have been previously created or imported into Tableau CRM.
• B. Records from a Salesforce object: Direct extraction of data from Salesforce objects into a new dataset via a recipe is supported, allowing users to leverage live Salesforce data for further analysis.

In Tableau CRM, a Compare Table allows you to segment data into different groupings for comparison. You can have up to four groupings in a Compare Table. This feature enables users to analyze and visualize data by comparing different segments side by side within the same table, facilitating a clearer understanding of how various groups perform against each other across multiple metrics. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_dashboard_widgets_compare_table.htm &type=5

=========================

To create a results binding in Salesforce Einstein Analytics that enables a table from one dataset to be filtered based on the results of a chart from another dataset, follow these steps:

• A. Look up the API name of the filtering field: This is necessary to understand and reference the specific field in the dataset that you want to use for filtering.
• B. Look up the API name of the source field: You need to identify the field in the source dataset (the one used by the chart) that will provide the filtering criteria.
• C. Find source and target step names: Identifying the source (chart) and target (table) step names in the dashboard is crucial for configuring the binding correctly. These names are used in the binding syntax to define where the source data is coming from and where it should apply.

The correct operation to use with the Analytics External Data API to upload monthly target data, which includes replacing existing entries with new data each month, is:

• C: Overwrite. This operation ensures that each upload replaces the existing dataset entirely, which is necessary for scenarios where the target data changes every month, and historical precision needs to be maintained.

In Salesforce Tableau CRM, with data sync enabled, the maximum number of dataflow definitions an organization can have is 25. This limit is designed to balance the need for comprehensive data operations with system performance and manageability.

For accessing Tableau CRM data from remote applications or websites, the following methods are recommended:

• B Lightning Out enables Salesforce components, including Tableau CRM dashboards, to be embedded into external web applications, maintaining their interactive capabilities and security.

For a Tableau CRM dashboard that utilizes data sync for replication:

The issue of the VP of Sales seeing "No results found" while others can view data in the dataset suggests a problem with access permissions. Two likely causes are: A) The VP’s Salesforce profile may lack read permissions on some crucial fields of the Opportunity__c custom object, which could prevent viewing data where those fields are essential. B) Security predicates at the dataset level might be set up in a way that restricts data visibility for the VP, perhaps due to specific conditions that exclude higher hierarchy levels.

The Tableau CRM Dashboard Inspector tool is designed to help optimize and troubleshoot dashboard performance by providing:

• A. Recommendations on how to improve the performance: It offers actionable suggestions to enhance dashboard efficiency.
• B. The total time required to run all queries: It aggregates the execution times of all queries involved in the dashboard, giving an overview of the dashboard’s performance.
• D. View all queries and the time it took to run each one: It allows detailed inspection of each query’s execution time, helping identify potential bottlenecks.

Among the listed options, which is not a method for controlling record-level access in Salesforce:

• A: Profiles. While profiles control what a user can do broadly within the Salesforce platform (such as read, create, edit, and delete permissions on objects), they do not directly control record-level access. Record-level access is specifically managed through Sharing Rules, Organization-Wide Defaults, and Role Hierarchy.

In Einstein Discovery stories, insights show how different variables, or combinations of variables, explain the variation of the outcome variable. The outcome variable is the target variable whose behavior and influencing factors are being analyzed and predicted by the model. Insights in the story will help understand how each explanatory variable and their interactions impact the outcome, which is central to predictive analytics and machine learning in Einstein Discovery. Reference: Salesforce Help - Einstein Discovery Insights

When you configure the story, you tell Einstein Discovery to maximize/minimize the variable. The variable is 'outcome variable' in your story

Before users can access Tableau CRM (Einstein Analytics), they must be assigned specific permissions. These include: A. An Analytics permission set license (PSL), which grants the user the license to use Analytics. B. A permission set configured with Analytics user permissions, which detail what aspects of Analytics the user can access. This setup ensures that both the licensing and access rights are correctly aligned to user roles and needs within the organization. It is essential to configure both aspects to enable functional and compliant use of the platform. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_security.htm &type=5

The scenario described where Yasmine cannot see any rows in the Seed Bank Orders dataset while Hadiqa can, likely indicates that the dataset's security predicate was set up to restrict data visibility based on user roles or attributes. Security predicates in Salesforce Tableau CRM are used to implement row-level security, ensuring that users only see data pertinent to their role or permissions within the organization. This security setup is crucial for maintaining data privacy and compliance. Reference: Salesforce Help - Row-Level Security

In statistical terms, the standard deviation measures the amount of variation or dispersion in a set of values. A higher standard deviation indicates that the values are more spread out from the mean (average). Among the options provided, a standard deviation of 16 suggests the highest degree of spread away from the average compared to the other values.

When discrepancies arise between the aggregate sum in a dataset and manual calculations in Salesforce, common issues include: C. Differences involving formula fields. Formula fields in Salesforce are calculated dynamically and may not always be calculated during data sync if they depend on other fields that aren't triggered by record updates. D. Differences involving trigger-updated fields. Fields that are updated by triggers might not have their latest values captured if the triggers were executed after the data was replicated. These scenarios can cause inconsistencies in data reflected in Einstein Analytics compared to what is stored directly in Salesforce. Reference: Salesforce Documentation on Data Sync and Replication

Regarding Einstein Analytics Encryption, the true statements are:

• A: When Einstein Analytics Encryption is enabled, all newly registered datasets are encrypted at rest. This ensures that any data stored within the platform is secured against unauthorized access, protecting sensitive information.
• C: The customer's org must have a Shield Platform Encryption tenant secret. This requirement is necessary for enabling encryption capabilities within Salesforce, which includes Einstein Analytics, ensuring data security complies with organizational and regulatory standards.

Assigning any Analytics permission set to users in a Salesforce org does not automatically assign the Analytics Platform permission set license. The license must be explicitly assigned to users before they can utilize the features enabled by the permission sets. This ensures that only authorized users have access to powerful analytics capabilities.

For Benito to build and edit a dashboard using the Seed Bank dataset in the Einstein Analytics app, the admin needs to do the following two things:

• Grant Benito access to the specific app that contains the Seed Bank dataset. This ensures he can access the necessary dataset within the confines of the designated app.
• Assign him a permission set that includes the "Create and Edit Analytics Dashboards" permission. This permission is crucial for enabling Benito to not only view but also create and modify dashboards within the app.

This dual requirement ensures both data accessibility and the ability to perform required operations on the dashboard. Reference: Salesforce Help - Permission Sets

On the Edit Field Attributes page when uploading a CSV file to Analytics (Tableau CRM), you can perform several modifications to ensure the data is properly formatted and structured for analysis:

• Change a field's name: Adjust the names of fields to match your analytics schema or to make them more understandable.
• Change a field's format: Modify the format especially for date, number, or any specific custom format required for your analysis.
• Change a field's type: Alter the data type (e.g., from string to integer or vice versa) to suit the data operations you plan to perform. These capabilities allow for the customization and preparation of data directly within the platform, streamlining the process from data upload to insight generation. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_datasets_upload.htm&type=5

To address the issue of stages appearing in alphabetical order rather than sales cycle order in a funnel chart, a consultant can:

• Use a dataflow to rename the stages with a preceding number (A): This method involves preprocessing the data to append a numerical prefix to each stage name, thus forcing a specific order in the visualization.
• Use a dataset XMD to rename stages (D): The Extended Metadata (XMD) of a dataset allows for the customization of how data is displayed, including defining custom labels for dimensions which can enforce a particular order in the visualization.

* template-info.json manages all elements of your template, including metadata information about the template, the Analytics objects that define dashboards and lenses, and the other files that are part of the template.* ui.json manages the configuration wizard that drives app creation. It defines the number of wizard pages, the order of wizard questions, and any messages you want the user to see.* variables.json contains all template variables, including text for wizard questions and specifications for the answers. Variables also define conditional questions. For example, you may want some questions to appear in the wizard only if an org contains certain data. Or you might want to add more specific questions based on the answers to more general wizard questions.* template-to-app-rules.json defines the rules the template follows. For example, you could define a rule that specifies that if an org doesn’t use certain Salesforce objects, the app won’t refer to them in dashboards or include them in the dataflow. Rules also define how variables are handled. For example, if the wizard asks which fields to include in filters for accounts, template-to-app-rules.json determines how that choice is reflected in dashboards.

For a dashboard that needs to visualize Closed Won opportunities by different time groupings (month, quarter, year) using a single chart, the appropriate action is: D. Use selection binding to update the grouping in the chart. This method allows the chart to dynamically change the grouping based on user selection, effectively switching between month, quarter, or year views within the same visual representation. Reference: Salesforce Documentation on Dynamic Dashboards

To delete activities in Dataset A related to users in Dataset B, the consultant can use a combination of dataflow transformations: "augment" and "filter." First, augment Dataset A with Dataset B using "userID" to combine the datasets based on user association. Then, apply a filter to retain only those records in Dataset A that do not have a corresponding entry in Dataset B.

In Salesforce Tableau CRM Einstein Discovery:

• B is correct because in the Story Settings, the consultant can view and evaluate the strength of each predictor field, helping to determine which fields are most influential in the model.

To ensure a user can view dashboards within a designated app without the ability to create and save lenses, the correct action is to assign the Viewer role to the user. This role allows the user to access and interact with the dashboards and apps but restricts the ability to modify, create, or save anything within the app, aligning perfectly with the requirement specified.

The best practice for handling user roles and permissions in Einstein Analytics is to create and assign Salesforce permission sets tailored to the distinct types of user roles. In this scenario, the consultant should recommend creating permission sets for:

• Dataset and dashboard builders (3 users),
• Dashboard creators (15 users),
• Dashboard viewers (982 users).

This approach allows for fine-grained control over access rights and ensures that each user has the appropriate level of permissions based on their responsibilities. Salesforce permission sets are a flexible and scalable way to manage access and can be tailored to the specific needs of any organization.

Outliers in a dataset can significantly impact the results of a machine learning model, including those built by Einstein Discovery.expand_more Here's why changing binning methods is often the best approach:

• Outliers and Machine Learning: Outliers are extreme values that fall far outside the typical range of data.expand_more They can distort statistical summaries and skew the model's understanding of relationships within the data.
• Binning: Binning is the process of dividing continuous numerical data into discrete groups or bins.expand_more In Einstein Discovery, binning affects how data is visualized and analyzed.
• Fixed-width Binning: With fixed-width binning, you define equal-sized intervals for grouping data points. This can help mitigate the impact of outliers by spreading their influence across a wider range, reducing their effect on individual bins and the overall model.

Why other options are less ideal:

• A. Remove the outlier rows: While removing outliers can be effective, it risks discarding potentially valuable information. It's best used only when outliers are definitively incorrect.
• B. Nothing, because the field is not the outcome variable: Even predictor variables (inputs) with outliers can negatively impact the model. Outliers distort relationships the model is trying to learn.expand_more
• D. Remove the field because it has bad data: This is too drastic unless the whole field is unreliable. Binning adjustments are often enough to address outlier issues.

The REST API URL where a consultant can find current template apps in Salesforce Tableau CRM (formerly Einstein Analytics) is "/services/data/vXX.X/wave/templates". This endpoint is specifically designed for interacting with template apps, allowing consultants to extend, customize, or retrieve information about available templates.

Two benefits of designing using the "Progressive Disclosure" principle are:

• A: Improved ease of use for end users. By only displaying essential information initially and allowing users to access more detailed data as needed, dashboards become less cluttered and more user-friendly.
• D: Better dashboard performance. This design principle can also lead to better performance as less data is processed and rendered initially, speeding up load times and responsiveness.