Analytics-Con-301 Salesforce Certified Tableau Consultant Exam Topics and Questions
These Salesforce Certified Tableau Consultant (Analytics-Con-301) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Analytics-Con-301 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Tableau Consultant certification exam.
Let's Practice Free Salesforce Analytics-Con-301 Questions Aligned with Official Exam Topics
This topic anchors the entire exam because it forces you to assess what already exists before you propose anything new. You're diagnosing the gap between current analytics and business goals, then mapping that gap to Tableau's architecture and feature set. The cost comes in two places: misjudging whether existing data structures can support the requirements, and recommending the wrong deployment model or upgrade path. β Mapping business needs to Tableau capabilities You start by connecting what the business wants to...
This topic anchors the entire exam because it forces you to assess what already exists before you propose anything new. You're diagnosing the gap between current analytics and business goals, then mapping that gap to Tableau's architecture and feature set. The cost comes in two places: misjudging whether existing data structures can support the requirements, and recommending the wrong deployment model or upgrade path.
β Mapping business needs to Tableau capabilities
You start by connecting what the business wants to what Tableau can deliver. That means translating vague requests into concrete features: dashboards, subscriptions, alerts, embedding, or mobile delivery. You also decide whether Tableau Server or Tableau Cloud fits the organization's security posture, compliance requirements, and IT constraints. Migration scenarios appear here too, so you need to know what triggers a move from on-premises to cloud and what that migration entails. Planning a Server upgrade requires you to assess version compatibility, downtime windows, and the sequence of steps that won't break existing content. The exam tests whether you can justify your recommendation with specifics, not just list features.
β Evaluating data structures and lineage
Once you understand the business need, you turn to the data itself. You evaluate whether the current structure supports the analytics requirements or whether it needs redesign. Lineage questions ask you to trace where data comes from, how it's transformed, and who owns each stage. Performance risks show up as poorly indexed tables, excessive joins, or row-level calculations that should live upstream. Enhancement opportunities might mean moving aggregations into the data warehouse or flattening hierarchies. The exam expects you to spot structural problems that will cause performance or maintenance pain later, and to recommend changes before anyone builds a workbook.
How Evaluate Current State is tested
At 22 percent, this topic appears in roughly one in five items. The weight reflects the diagnostic nature of consulting work: you can't design a solution until you've assessed what's already there. Items present a scenario with an existing Tableau environment and a set of business goals, then ask you to identify the gap or recommend the next step. You'll lose marks if you jump to a technical solution without considering the organization's constraints, or if you recommend Cloud when the scenario describes strict on-premises requirements. Another common trap is ignoring data lineage: the item describes a performance problem, and the answer lies upstream in the ETL process, not in Tableau itself. The exam rewards candidates who read the scenario for what's missing or misaligned, not just what's present.
The practice test gives you exposure to scenario-based items where the correct answer depends on reading constraints carefully. The PDF version lets you review those constraints at your own pace, marking the ones where you missed a detail that changed the recommendation.
The scenario below describes an existing analytics environment and asks you to identify the most appropriate next step.
An online sales company has a table data source that contains Order Date. Products ship on the first day of each month for all orders from the previous month.
The consultant needs to know the average number of days that a customer must wait before a product is shipped.
Which calculation should the consultant use?
Where the first topic assessed what exists, this one builds the data layer that will support every workbook downstream. You're deciding how data reaches Tableau, how it's secured, and at what level of detail it arrives. The challenge is that every choice here affects performance, security, and maintainability later. Row-level security is the most technically dense area, and aggregation strategy is where most candidates underestimate the impact of getting it wrong. β Data transformation strategy and granularity You start by...
Where the first topic assessed what exists, this one builds the data layer that will support every workbook downstream. You're deciding how data reaches Tableau, how it's secured, and at what level of detail it arrives. The challenge is that every choice here affects performance, security, and maintainability later. Row-level security is the most technically dense area, and aggregation strategy is where most candidates underestimate the impact of getting it wrong.
β Data transformation strategy and granularity
You start by deciding where transformation happens: in the source system, in Tableau Prep, or inside Tableau Desktop. The right answer depends on who maintains the pipeline, how often the logic changes, and whether other tools need the same transformed data. Minimum granularity matters because it determines how much data Tableau has to process. If the business needs monthly summaries but you're pulling daily rows, you're moving far more data than necessary and slowing every query. The exam expects you to specify the right level of detail and justify why that level supports the analytical requirements without over-fetching.
β Row-level security and entitlement structures
RLS is where this topic gets dense. You design a data structure that filters rows based on who's viewing the workbook, then implement it using entitlement tables, user functions, or group functions. The exam tests whether you know when to use each approach and what the trade-offs are. An entitlement table scales better than embedding logic in every data source, but it requires coordination with the data team. User functions are precise but harder to maintain. Group functions simplify administration but can leak data if group membership isn't tightly controlled. You'll also compare dynamic filters, initial SQL, and data source filters, each with different performance and security characteristics.
β Advanced connection methods
The final group covers connections that go beyond the standard connector list. Web Data Connectors let you pull from APIs that Tableau doesn't natively support. Custom SQL gives you control over the query Tableau sends, useful when you need to flatten a schema or apply a filter at the database level. ODBC handles legacy systems. Tableau Bridge extends Cloud's reach back to on-premises data. You need to know when each method is appropriate, what its limitations are, and how to configure it correctly. The exam also asks you to specify aggregation strategy across different Tableau products, because a data source built in Desktop behaves differently when published to Server or used in Prep.
How Plan and Prepare Data Connections is tested
This topic also carries 22 percent, matching the weight of Evaluate Current State. Items describe a data scenario with specific security, performance, or access requirements, then ask you to choose the connection method or RLS approach that fits. The traps are subtle: an item might describe a need for row-level security, and both entitlement tables and user functions appear as options, but only one scales to the number of users mentioned in the scenario. Another common mistake is recommending custom SQL when the performance problem actually lies in the aggregation level, not the query structure. The exam rewards candidates who match the technical method to the organizational context, not just the one that sounds most advanced. You'll also see items that ask you to identify what goes wrong when aggregation happens at the wrong stage, or when Bridge is misconfigured.
A full question bank helps you see the same RLS or aggregation concept tested from different angles, so you learn to recognize the pattern rather than memorizing one scenario. The timed mode lets you practice deciding quickly which connection method fits the constraints.
The scenario that follows requires you to choose a connection method based on the organization's data access and security requirements.
A client is considering migrating from Tableau Server to Tableau Cloud.
Which two elements are determining factors of whether the client should use Tableau Server or Tableau Cloud? Choose two.
This topic is the exam's center of gravity. At 40 per cent, it's twice the weight of any other section, and it demands the deepest technical knowledge. You're designing analytics for complex use cases, troubleshooting performance problems, and implementing calculations that combine multiple advanced techniques. The sub-topics span three distinct skill areas: advanced chart types and interactivity, performance optimization, and multi-step calculations. Each one can cost you marks if you don't know the mechanics in detail. β Advanced chart types...
This topic is the exam's center of gravity. At 40 percent, it's twice the weight of any other section, and it demands the deepest technical knowledge. You're designing analytics for complex use cases, troubleshooting performance problems, and implementing calculations that combine multiple advanced techniques. The sub-topics span three distinct skill areas: advanced chart types and interactivity, performance optimization, and multi-step calculations. Each one can cost you marks if you don't know the mechanics in detail.
β Advanced chart types and interactivity
You start with chart types that don't appear in the default Show Me menu: Sankey diagrams for flow analysis, chord charts for relationships, radar charts for multivariate comparison, tile maps for geographic density, and small multiples for comparative distributions. The exam tests when each type is appropriate and what data structure it requires. Data densification comes up when you need to fill gaps in a dataset so a chart renders correctly, often for date ranges or hierarchies with missing values. Interactivity means building dashboards where actions change what's visible: dynamic URL actions that construct links based on selected data, parameter actions that let a user click to change a calculation's input, and filter actions that cascade across sheets. The exam expects you to know how these techniques combine and what happens when they conflict.
β Performance optimization techniques
Performance is where most candidates lose marks because the causes are layered. You start by identifying resource-intensive queries, often by reading query logs or performance recordings. Caching on Tableau Server helps when the same query runs repeatedly, but you need to know what invalidates the cache and how to maximize hit rates. Calculations cause performance problems in predictable ways: string comparisons are slower than numeric ones, nested IF THEN statements multiply evaluation time, and LOD expressions can force Tableau to query the database multiple times. The exam tests whether you can spot which calculations belong upstream in the data warehouse rather than inside Tableau. Performance recordings show you where time is spent, but interpreting them requires you to distinguish between slow queries, slow rendering, and slow network transfers. Design elements matter too: a dashboard with fifteen sheets and twenty filters will struggle regardless of how efficient the queries are, and oversized images bloat the workbook file.
β Multi-step and nested calculations
The calculation sub-topics are the most technically demanding. You implement aggregations that include dimensions, which means wrapping a dimension in an aggregation function so it can appear alongside a measure. Advanced table calculations include window functions that look across a range of rows, nested table calculations where one calculation references another, and multi-directional calculations that move both across and down a table. Fiscal calendars require custom date functions because the fiscal year doesn't align with the calendar year. Nested LODs embed one LOD expression inside another, useful when you need to calculate at multiple grains in a single formula. The exam also tests combinations: a window function that references a LOD, or a table calculation that includes a parameter. Each layer adds complexity, and the order of operations determines whether the calculation works at all.
β Troubleshooting and order of operations
Troubleshooting ties everything together. The Tableau order of operations dictates the sequence in which filters, LODs, table calculations, and aggregations are applied. If you apply a dimension filter before an LOD calculation, the LOD sees the filtered data. If you apply it after, the LOD sees the full dataset. The exam tests whether you can predict the result of a calculation given the filter context, and whether you can fix a calculation that's returning the wrong result because it's in the wrong stage of the pipeline. Troubleshooting also means identifying why a workbook is slow, why a calculation returns null, or why a filter isn't behaving as expected. The scenarios are specific, and the answer often lies in understanding what Tableau is doing behind the scenes, not just what you see on the dashboard.
How Design and Troubleshoot Calculations and Workbooks is tested
At 40 percent, this topic dominates the exam. You'll see items that describe a performance problem and ask you to identify the cause, items that present a broken calculation and ask you to fix it, and items that require you to choose the right advanced technique for a scenario. The weight means you can't pass without deep knowledge of LODs, table calculations, and the order of operations. Traps include answers that sound plausible but apply the wrong technique: using a table calculation when the scenario requires an LOD, or recommending a filter change when the real problem is a string comparison inside a nested IF statement. Performance items often include distractors that address symptoms rather than causes, like adding more RAM when the problem is an inefficient calculation. The exam rewards candidates who can read a performance recording, identify the bottleneck, and recommend the change that will have the largest impact.
Volume matters most for this topic because the sub-topics are so varied. The practice test covers calculation troubleshooting, performance scenarios, and advanced chart selection across enough items that you'll spot where your knowledge has gaps. The demo version lets you try a few before committing.
The calculation scenario below asks you to identify why a workbook is returning unexpected results based on the order of operations.
The final topic shifts from building to managing. You're establishing the rules and processes that keep a Tableau environment reliable as it scales. Governance covers who can publish what, how data quality is maintained, and how content reaches its audience. The administrative views sub-topic is the most concrete, while governance strategy requires you to map organizational requirements to Tableau's permissions and certification features. β Governance strategy and data quality Governance starts with securing access to content. You map permissions, projects,...
The final topic shifts from building to managing. You're establishing the rules and processes that keep a Tableau environment reliable as it scales. Governance covers who can publish what, how data quality is maintained, and how content reaches its audience. The administrative views sub-topic is the most concrete, while governance strategy requires you to map organizational requirements to Tableau's permissions and certification features.
β Governance strategy and data quality
Governance starts with securing access to content. You map permissions, projects, and groups so users see only what they should, without creating so many rules that administration becomes unmanageable. Data quality strategy includes certifying trusted data sources so users know which ones are approved, minimizing proliferation by discouraging duplicates, and configuring data quality warnings when a data source has known issues. The exam tests whether you can recommend a strategy that balances control with usability. Too much restriction and users build shadow analytics outside Tableau. Too little and the environment fills with outdated or incorrect content. You also need to know which Tableau features enforce each part of the strategy: permissions, certifications, warnings, and project structures.
β Administrative views and content distribution
Administrative views give you insight into how the environment is used. You specify which view answers a given question: who's accessing which workbooks, what data sources are stale, where performance is degrading, or which content hasn't been viewed in months. The exam expects you to recommend the right view and data source for a scenario, not just list what's available. Content distribution covers the workbook lifecycle from build to maintenance. You decide whether to publish to Server or Cloud, how to test before deployment, how to distribute content via subscriptions or embedding, and how to maintain workbooks as requirements change. The exam tests whether your approach fits the organization's workflow, not just what's technically possible.
How Establish Governance and Support Published Content is tested
At 16 percent, this topic appears less often than the others, but the items are scenario-heavy. You'll see a description of an organization's governance requirements and be asked to map them to Tableau features, or a problem with content access and be asked to recommend the administrative view that would diagnose it. The traps are usually answers that solve a different problem: an item describes data quality concerns, and one option tightens permissions when the real answer is certifying data sources. Another common mistake is recommending a distribution method that doesn't fit the audience's needs, like embedding when the scenario describes users who need to explore data interactively. The exam rewards candidates who read the organizational context and choose the governance approach that scales without creating bottlenecks.
Governance items often hinge on knowing which administrative view or permission structure applies to a specific scenario. The practice test lets you check whether you're matching the right feature to the requirement, and the PDF format is useful for reviewing the governance concepts that span multiple items.
The governance scenario that follows asks you to recommend the administrative view that would provide the insight needed to address a specific operational issue.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Analytics-Con-301 Exam Questions π