Salesforce Tableau CRM Einstein Discovery Consultant (SP24) Exam Guide
The Salesforce Certified CRM Analytics and Einstein Discovery Consultant credential validates the knowledge and performance skills needed to implement CRM Analytics and Einstein Discovery at enterprise level. It is intended for consultants who design, build, secure, deploy, and support analytics apps, datasets, dashboards, and stories, usually with practical experience across these domains. This guide helps you decide whether your preparation should focus first on data and administration, security and implementation, or dashboard design and discovery—and how to turn that choice into a hands-on study plan.
What this certification actually validates
This certification tests whether you can translate business requirements into governed CRM Analytics and Einstein Discovery solutions, not simply recognize product terminology. The work spans the data layer, permissions, dashboards, stories, deployment, performance, and user experience in Salesforce Lightning Experience.
Salesforce describes the credential as covering the design, building, and support of apps, datasets, dashboards, and stories in CRM Analytics and Einstein Discovery. The official guide also describes enterprise-level implementation knowledge and performance skills. That combination matters: a candidate may understand how to create a dashboard yet still be unprepared to secure it, move it between environments, or explain its output to business users.
The current official credential name is Salesforce Certified CRM Analytics and Einstein Discovery Consultant. Older Salesforce material used the name Salesforce Certified Einstein Analytics and Discovery Consultant and described related coverage such as data ingestion, security and access, and dashboard creation. If your catalogue or study notes use “Tableau CRM,” “Einstein Analytics,” or the older credential name, map those labels to the current credential page before relying on the material.
Who should use this guide before scheduling
Schedule only after you can distinguish configuration knowledge from implementation judgment. Salesforce states that the typical consultant has at least one year of experience across the CRM Analytics and Einstein Discovery domains, while the exam guide expects understanding of dataset management, permissions and security, advanced SAQL coding, and JSON for desktop and mobile dashboard creation.
The strongest fit is a consultant, administrator, analytics professional, or implementation specialist who has worked with Salesforce data and can reason about how a solution will be used in production. You do not need to treat the experience statement as a formal prerequisite unless Salesforce says so separately; use it as a readiness signal.
A candidate with only Trailhead familiarity should build a small working solution before scheduling. A candidate who already administers CRM Analytics should spend less time rereading introductory definitions and more time testing security, deployment, query behavior, dashboard performance, and mobile layouts. A candidate from a data background should deliberately close the Salesforce administration and sharing gaps rather than assuming SQL knowledge covers SAQL or CRM Analytics security.
What the exam format tells you about preparation
The official Salesforce exam guide describes 60 multiple-choice questions plus up to five unscored questions. That format rewards careful scenario analysis: read for the stated business objective, existing architecture, user permissions, and operational constraint before choosing a solution.
Do not treat the possible unscored questions as a separate study target or assume you can identify them. Prepare for every question as if it tests the credential’s stated implementation skills. When practicing, explain why the selected answer fits the scenario and why the alternatives would create a security, governance, usability, maintenance, or performance problem.
Salesforce officially supports two proctored delivery formats: online proctoring through Pearson OnVUE and in-person testing at a Pearson VUE testing center. Confirm current registration, identification, appointment, equipment, environment, and rescheduling requirements through the official Salesforce certification and Pearson VUE channels before booking. The supplied evidence does not establish a current exam price, duration, language list, passing score, or question weighting, so do not rely on those details from an unofficial catalogue.
How to read the skill coverage without inventing a blueprint
Treat the published capability descriptions as a connected implementation model rather than as isolated product features. The official guide names front-end abilities such as selecting visualizations, applying user-experience principles to dashboards, building SAQL, SOQL, and SQL queries, configuring template apps, improving dashboard performance, and converting layouts for mobile devices.
The same guide identifies administrative abilities including user provisioning, deployment between environments, governance of CRM Analytics assets, dataset security predicates and sharing inheritance, app permissions, and embedding dashboards in Salesforce pages or Experience Cloud. These topics interact in realistic scenarios. For example, a visually effective dashboard is not a complete solution if its dataset predicate exposes records to the wrong audience or if its deployment approach cannot be governed.
No verified domain percentages were supplied for this SP24 request. Avoid study plans based on bare percentages copied from an older guide or third-party question bank. Instead, use the official three-part preparation trail as the organizing framework: data layer and administration, security and implementation, and design and discovery.
Build a study environment before memorizing terms
A small implementation exercise gives you a better diagnostic than passive reading. Create or use an authorized Salesforce practice environment, define a business question, load an appropriate dataset, build a dashboard, test access with different users, and document what changes when the solution moves from development to a target environment.
Keep the exercise intentionally narrow. A useful sequence is: identify the source data and grain; inspect fields and relationships; decide whether the required transformation belongs in ingestion, a recipe, a query, or the dashboard; create a dataset; apply access controls; build a lens or dashboard; test filters and interactions; consider mobile presentation; and record deployment dependencies.
Do not use production data casually, and do not copy confidential customer information into personal notes or third-party practice tools. The goal is to practice design reasoning and configuration decisions using permitted data, not to reproduce live exam content.
Create a decision log alongside the build. For each choice, write the requirement, the selected mechanism, the security implication, the performance implication, and how you would validate it. This habit helps with questions where several answers sound technically possible but only one respects the full scenario.
Start with the data layer and administration
Begin with data lineage and dataset management because dashboard and discovery results are only as reliable as their source data and access model. Your first study pass should connect ingestion, transformation, dataset structure, user provisioning, app organization, and operational ownership.
Review how a source becomes usable for analysis: what is loaded, how fields are shaped, which relationships or joins are needed, and where a transformation should occur. Practice explaining the consequences of choosing a query-time operation instead of preparing the dataset earlier. The exam guide’s references to SAQL, SOQL, and SQL mean you should understand their roles and boundaries rather than merely recognize syntax.
Then examine administration as a lifecycle. Ask who can create, view, edit, share, deploy, and maintain each asset. Map users to permission sets or equivalent access mechanisms in the environment you are studying, and distinguish access to an app from access to the underlying data. Include ownership, folder or app organization, and the effect of changing an asset after deployment.
A practical checkpoint is to give two deliberately different users access to the same analytical experience and verify both the visible assets and the records returned. If you cannot predict the result before testing, security and administration should remain a priority.
Questions to ask about every dataset
What business grain does one row represent? Which fields are dimensions, measures, identifiers, dates, or derived values? Which source system owns the value? What happens to nulls, duplicates, late-arriving records, and changed relationships? Which users should see each record? These questions expose weaknesses that a field-list memorization exercise misses.
Make security and implementation a separate pass
Security deserves its own study block because a correct dashboard can still be an incorrect implementation. Focus on dataset security predicates, sharing inheritance, app permissions, user provisioning, governance, deployment between environments, and embedding in Salesforce pages or Experience Cloud.
For each access scenario, write the intended audience, the asset they can open, and the records they can see. Then identify the control responsible for each boundary. This prevents a common mistake: treating app visibility, dashboard visibility, dataset access, and row-level data access as interchangeable.
Study deployment as a controlled movement of a solution, not as a button to press. List the assets, dependencies, permissions, connections, and environment-specific settings that need review. Consider how you would validate the result after deployment and how you would handle a change without bypassing governance.
Embedding requires the same discipline. Ask where the dashboard appears, who can reach the containing page, what data the embedded user is entitled to view, and whether the user experience remains understandable in that context. A dashboard that works in an analyst’s app may need different navigation, filtering, or explanatory treatment when placed in a Salesforce page or Experience Cloud.
Security mistakes worth rehearsing
Do not infer record access from a user’s ability to open an app. Do not assume inherited sharing automatically matches every business rule. Do not test only with an administrator. Do not deploy without checking environment-specific references. For each mistake, create a short scenario and state the control that would prevent it.
Practice dashboard design as a business decision
Dashboard preparation should combine visual choice, interaction design, query behavior, performance, and device layout. The official guide specifically identifies visualization selection, UX principles, dashboard performance, template apps, and conversion for mobile devices as relevant front-end abilities.
Start every dashboard with the decision it must support. A trend, comparison, distribution, ranking, and exception view may require different visual forms. Select the visualization that makes the intended comparison easy, then remove elements that do not help the user act. Practice explaining why a chart is appropriate rather than memorizing a chart-to-term pairing.
Build interactions deliberately. Decide which filter should affect which widget, whether a selection creates a useful follow-up question, and how a user returns to the original view. Test empty results, unusually large values, long labels, missing dates, and multiple filter combinations. These cases reveal whether the design communicates a result or merely displays data.
For performance, look beyond cosmetic changes. Inspect the amount of data queried, the number of widgets, repeated queries, unnecessary transformations, and interaction chains. Then test whether a proposed improvement changes the user’s actual experience without weakening the required analysis.
Finally, inspect the mobile version as a separate experience. Rework layout and priority instead of assuming a desktop arrangement will remain usable on a smaller screen. The official guide identifies converting layouts for mobile devices, so include that task in your build checklist.
Template apps and reuse
When studying template apps, focus on configuration decisions and fit. Identify which parts are supplied by the template, which parts must be adapted to the organization’s data and process, and which assumptions could mislead users. Reuse is valuable only when the data model, security model, and business workflow remain valid.
Learn Einstein Discovery through the story lifecycle
Study Einstein Discovery as a process for turning a defined business outcome into an interpretable story and an actionable improvement, not as a collection of prediction terms. The official Einstein Discovery learning trail contains five badges and estimates approximately 2 hours and 50 minutes to complete.
Start by defining the outcome and the population. Check whether the available fields support the question and whether the data is suitable for the intended decision. Then examine the story’s insights, contributing factors, recommendations, and limitations. Ask what a business user should do differently as a result and how that action would be measured.
Keep the distinction between analytical evidence and operational advice clear. A factor associated with an outcome does not automatically prove causation, and a suggested improvement still needs business, governance, and data-quality review. Practice communicating an insight in plain language while preserving the conditions under which it applies.
Use the story-design badge as an applied exercise. Build a short explanation for a stakeholder: the outcome, the relevant population, the strongest useful insight, the recommended action, the risk of misinterpretation, and the metric that would show whether the action helped. This trains the communication and implementation judgment expected from a consultant.
A useful discovery review checklist
Before accepting a story, check outcome definition, field meaning, data coverage, unusual values, privacy, audience, recommended action, and follow-up measurement. If any of these is unclear, the problem is not solved by presenting the story more attractively. Return to the requirement or data design.
Use the official study trails in the right order
Salesforce’s preparation trail is a compact orientation, not a substitute for hands-on work. It contains three consultant-certification preparation badges covering data layer and administration, security and implementation, and design and discovery, with an official estimate of approximately 1 hour and 50 minutes for the three-step study path.
Complete the data layer and administration material first if your dataset lifecycle, queries, or asset ownership are uncertain. Follow with security and implementation so that permissions, deployment, governance, and embedding are studied before you judge a dashboard complete. Finish with design and discovery, then return to any weak area revealed by the exercises.
The trail describes scenario-based study and interactive flashcards. Use them for retrieval practice: answer before revealing the explanation, record why you were uncertain, and revisit the relevant product concept in a working environment. Flashcards should expose gaps; they should not become a substitute for building and testing.
The separate Einstein Discovery learning trail contains five badges and estimates approximately 2 hours and 50 minutes. Use it when discovery concepts are new or when your implementation experience is stronger in CRM Analytics than in story design. The study trail may include content available only in English, so confirm that the learning format works for you before making it your only preparation resource.
A practical four-phase roadmap
A staged roadmap works better than repeating the same practice questions. Use the first phase to establish the data and administration foundation, the second to test security and implementation, the third to build and critique dashboards and stories, and the final phase to simulate decision-making under exam conditions.
Phase one—baseline and data: read the current official credential description, list your experience against dataset management, SAQL, SOQL, SQL, provisioning, and asset governance, then build or inspect a permitted dataset. Write down every concept you can name but cannot demonstrate.
Phase two—security and lifecycle: create an access matrix, test more than one user profile or permission arrangement, review dataset predicates and sharing inheritance, and trace a solution from development to another environment in the manner supported by your organization. Add a deployment checklist covering dependencies and post-deployment validation.
Phase three—experience and discovery: design a dashboard around a concrete decision, select visualizations intentionally, test interactions and performance, inspect desktop and mobile layouts, and complete a discovery story exercise. Have someone challenge the assumptions, audience, and actionability of the result if possible.
Phase four—readiness: use scenario prompts that mix data, security, dashboard, and discovery concerns. For each answer, state the requirement, the controlling feature, the rejected alternatives, and the validation step. Stop adding new resources when your errors become specific and explainable. Spend the remaining time repairing those errors and checking official Salesforce information for changes before scheduling.
A short version for experienced consultants
If you already deliver CRM Analytics solutions, skip broad product tours and perform a gap audit. Can you explain row-level access, sharing inheritance, deployment governance, mobile conversion, query choices, performance trade-offs, and Einstein Discovery recommendations to a stakeholder? Any “not sure” answer becomes a targeted lab, not a reason to restart the entire curriculum.
How to use practice questions without learning the wrong lesson
Practice questions are useful when they test reasoning against authorized material; they are dangerous when they encourage memorizing answer patterns. No question bank can replace the official scope, and leaked questions or exam dumps cannot guarantee a pass or demonstrate implementation competence.
After each question, identify the decisive phrase. It may be a security requirement, a deployment boundary, a user-experience objective, a performance constraint, a data-shaping need, or a requirement to explain a discovery result. Then write the smallest product behavior that resolves that phrase.
Maintain an error register with four columns: topic, mistaken assumption, correct reasoning, and proof task. “Security” is too broad to be useful; “assumed app access grants row access” points to a concrete review. “SAQL weak” can become “cannot choose whether a transformation belongs in data preparation or query logic.”
Avoid studying from material that supplies unsupported claims about exact scores, current question pools, retirement, or exam timing. Cross-check credential names and delivery information against the official Salesforce pages supplied for this guide. Use third-party material only as a prompt for investigation, never as authority for a factual exam requirement.
Scheduling and delivery decisions
Choose the delivery format that fits your reliable testing environment, then verify the current rules before payment or appointment selection. Salesforce supports online proctoring through Pearson OnVUE and in-person testing at a Pearson VUE testing center.
For online delivery, assess your workspace, network stability, computer readiness, privacy, and ability to follow the proctoring process without interruption. For a testing center, consider travel, appointment availability, identification requirements, and the practical time needed to arrive. These are preparation recommendations, not additional Salesforce exam requirements; the official delivery page remains the authority for current procedures.
Do not schedule solely because you completed a Trailhead time estimate. Those estimates describe learning content, not a guarantee of readiness. Schedule when you can explain your architecture decisions, complete the relevant hands-on checks, and review mistakes without relying on memorized answer strings.
The supplied Trailhead material states that registering three or more unlocks $999 passes. Treat that as a Salesforce promotion or registration condition requiring confirmation on the linked official page, not as a general exam price or a promise that the offer applies to every candidate or appointment.
Maintenance and naming checks after certification
Certification maintenance is a separate responsibility from exam preparation. Check the current Salesforce maintenance instructions after earning the credential, especially when your credential appears under a newer name than older study resources.
Salesforce states that candidates who earned the CRM Analytics and Einstein Discovery Consultant certification on or before April 22, 2026 must complete the Spring ’26 maintenance badge by April 16, 2027, to maintain the certification. This condition is tied to the stated earning date and maintenance cycle; candidates with a different status should verify the applicable requirement in Salesforce’s official maintenance information.
Also update saved study links when Salesforce changes product terminology. The older official guide’s Einstein Analytics and Discovery name may still be useful for historical context, but the current credential page should control how you describe the certification and verify maintenance.
Final readiness test before booking
You are closer to ready when you can solve an unfamiliar implementation scenario by connecting requirement, data, access, experience, and validation—not when you can recite feature names. Use a final review to expose gaps that broad study sessions conceal.
Before scheduling, confirm that you can: describe dataset grain and lineage; choose appropriately among SAQL, SOQL, and SQL in context; explain user provisioning and app permissions; distinguish dataset security predicates from sharing inheritance; plan governed deployment between environments; select visualizations using a stated UX goal; identify dashboard performance risks; adapt a layout for mobile; configure a template app responsibly; embed a dashboard with its audience and access model in mind; and interpret an Einstein Discovery story without overstating its evidence.
For each capability, perform one short proof task or explain the exact steps you would take to validate it. If you can only define the term, keep studying. If you can configure it but cannot explain the security or maintenance consequence, keep studying. If your only evidence is a memorized practice answer, replace it with an authorized hands-on exercise.
Once the gaps are specific and your explanations are consistent, review the official credential, study, delivery, and maintenance pages one more time. Then select a delivery format, confirm current appointment rules, and schedule with a plan for the remaining review rather than waiting for perfect familiarity with every possible scenario.
Conclusion
Prepare for this certification as an implementation consultant, not as a terminology quiz taker. Build from data and administration, verify security and lifecycle decisions, design dashboards for real users and devices, and use Einstein Discovery to connect insight with action. The official Trailhead paths provide a useful sequence, while hands-on validation and an error register show whether the knowledge is usable. Confirm current Salesforce requirements before scheduling, and keep the official maintenance information bookmarked after you earn the credential.
Related exams
- ADM-201 exam — Salesforce Certified Administrator
- ADM-211 exam — Administration Essentials for Experienced Admin
- B2B-Commerce-Administrator exam — Salesforce Accredited B2B Commerce Administrator
- Certified-Advanced-Administrator exam — Salesforce Certified Advanced Administrator
- Certified-B2C-Commerce-Developer exam — Salesforce Certified B2C Commerce Developer
- Certified-Community-Cloud-Consultant exam — Salesforce Certified Community Cloud Consultant
