Analytics-Con-301 Salesforce Certified Tableau Consultant Exam Topics and Questions

This topic accounts for just over a fifth of the exam, and it puts you in the role of the person who walks into an organisation and has to work out what they already have, what they need, and what can be salvaged. You are mapping existing analytics to future requirements, assessing data structures for performance and lineage, and deciding whether the deployment model or platform version needs to change.

– Translating business needs into Tableau capabilities

You need to connect what stakeholders say they want with what Tableau can actually deliver, then express analytical requirements in terms that make sense within the platform. That means understanding the difference between a vague ask for 'better reporting' and a concrete requirement that maps to a specific feature set. The exam expects you to know when current analytics can be adapted and when they need to be rebuilt, and to recognise whether the business need is best served by Server, Cloud, or a migration between the two. You will also need to recommend and plan upgrades to Tableau Server, which means understanding version dependencies, downtime windows, and the order in which components must be updated. The weight here is on matching capability to need, not on selling features.

– Evaluating data structures and their fitness for purpose

The second half of this topic is about the data itself. You are assessing current structures to see whether they support what the business is trying to do, tracing lineage to understand where data comes from and what transformations it has been through, and identifying performance risks or opportunities for enhancement. The exam will test whether you can look at a data model and spot the problem: the grain is wrong, the joins are expensive, the structure does not support the required level of aggregation, or the source is too stale to be useful. You are also expected to know when a structure can be optimised in place and when it needs to be rebuilt upstream. The focus is on diagnosis, not on the mechanics of fixing every issue within Tableau itself.

How Evaluate Current State is tested

At 22 percent, this topic generates around one question in every five. Items typically present a scenario in which an organisation has an existing Tableau deployment or a set of analytics requirements, and you must decide what to assess, what to recommend, or what risk to flag. The scenario will describe the current state in enough detail that you can identify a mismatch between structure and need, or between platform choice and business constraint. Candidates lose marks when they recommend a feature without checking whether the underlying data supports it, or when they fail to recognise that a performance problem originates in the data model rather than in the visualisation. Another common trap is recommending Server when Cloud is the better fit, or vice versa, because the scenario includes a constraint (such as data residency or low IT resource) that rules one out. Read the scenario for what is already in place and what is missing, then match your answer to the gap.

Where the first topic was about assessing what exists, this one is about preparing the data layer so that workbooks can be built on solid foundations. The weight is identical at 22 percent, and the focus shifts to transformation strategy, row-level security, connection methods, and aggregation decisions. You are choosing where transformation happens, designing entitlement structures, and working out which connection approach fits the data source and the deployment model.

– Transformation and granularity

You need to decide where transformation should happen: in the source system, in Tableau Prep, or in a custom SQL connection. Each choice has trade-offs in terms of maintainability, performance, and who can change the logic later. The exam expects you to recommend a strategy that fits the organisation's skill base and infrastructure, and to specify the minimum level of granularity required so that the data source can support every intended visualisation without forcing users to go back upstream. If the grain is too coarse, some analyses become impossible. If it is too fine, performance suffers and extract sizes balloon. The right answer depends on what the business needs to slice by, and on how much aggregation can safely happen before the data reaches Tableau.

– Row-level security design and implementation

Row-level security is a recurring theme in this topic. You need to design the data structure that supports it, implement an entitlement table, and choose between different RLS approaches depending on the scenario. The exam will test whether you understand the difference between user functions and group functions, and when each is appropriate. It will also test whether you can compare RLS methods: entitlement tables versus data source filters, or dynamic filters built into custom SQL. Each approach has different implications for maintenance, performance, and the number of data sources you end up managing. The focus is on choosing the right method for the constraints in the scenario, and on recognising when an entitlement table is the only scalable option.

– Advanced connection methods and aggregation strategy

The final group covers connection mechanics. You need to know when to use Web Data Connectors, web extract APIs, custom SQL, or ODBC, and when Tableau Bridge is required to connect Cloud to on-premises data. The exam expects you to match the connection method to the data source type, the deployment model, and the refresh requirements. You also need to specify the aggregation level and strategy across Tableau Desktop, Prep, Cloud, and Server, which means understanding where aggregation happens in the pipeline and what the performance cost is at each stage. The right strategy depends on whether the data source is live or extract, how often it refreshes, and whether users need to drill to row-level detail or can work with pre-aggregated data.

How Plan and Prepare Data Connections is tested

This topic also accounts for 22 percent, so expect a similar number of items. Scenarios describe a data source, a deployment model, and a set of requirements, then ask you to choose the connection method, the transformation strategy, or the RLS approach. The detail in the scenario will include the type of data source, whether it is on-premises or cloud-based, who needs access, and what level of detail users require. Candidates lose marks when they recommend custom SQL without checking whether the organisation has the skills to maintain it, or when they design an RLS structure that works for ten users but does not scale to a thousand. Another common mistake is choosing a connection method that requires Tableau Bridge but missing the fact that the scenario specifies Cloud with no on-premises infrastructure. Read for the constraints first, then eliminate the options that do not fit.

At 40 percent, this topic is the centre of gravity for the exam. It covers advanced chart types, the order of operations, dashboard interactivity, performance optimisation, and every flavour of calculation you are likely to encounter. The breadth is significant: you need to know when to use a Sankey diagram, how to troubleshoot a nested LOD expression, and how to interpret a performance recording. The exam assumes you have built complex workbooks under production constraints and had to fix them when they broke.

– Advanced analytics and chart selection

You are expected to recommend chart types that go beyond bar and line: Sankey, chord, radar, tile map, small multiples, and data densification techniques. The exam tests whether you can match the chart type to the analytical need, which means understanding what each type reveals and when it obscures the answer. A Sankey works for flow, but not for ranking. Small multiples work when comparison across categories is the point, but they fail when the audience needs a single aggregated view. You also need to plan and implement interactivity using dynamic URL actions, parameter actions, and filter actions. The focus is on building dashboards that let users explore without overwhelming them with controls, and on recognising when interactivity adds value versus when it just adds complexity.

– Order of operations and calculation troubleshooting

The Tableau order of operations determines when filters apply, when LOD expressions evaluate, and when table calculations run. The exam expects you to identify the effect of this order on a calculation, and to troubleshoot issues when the result is not what the user expected. A common trap is a filter that excludes rows before an LOD expression can see them, or a table calculation that produces the wrong result because the partitioning is applied too late. You need to know the sequence cold: extract filters, data source filters, context filters, dimension filters, measure filters, table calculations. When a calculation breaks, the order of operations is usually the reason. The exam will describe a scenario in which a calculation returns an unexpected result, and you must identify which stage in the order is causing the problem.

– Performance optimisation and query efficiency

Performance is a major theme. You need to identify and resolve resource-intensive queries, maximise caching on Tableau Server, and recognise when a calculation should be moved upstream of Tableau. The exam will test whether you can interpret a performance recording and pinpoint the bottleneck: a slow query, an expensive calculation, or a design choice such as too many sheets or filters. String comparisons, IF THEN statements, and LOD expressions are all common culprits, and you need to know which optimisation tactic applies to each. Sometimes the fix is rewriting the calculation. Sometimes it is changing the data source. Sometimes it is reducing the number of marks or simplifying the dashboard. The exam expects you to diagnose the cause and recommend the most effective fix, not just the easiest one.

– Implementing and combining advanced calculations

The final group covers the mechanics of building calculations that include multiple steps, aggregations that include dimensions, advanced table calculations, fiscal calendars, and nested LODs. You are expected to implement window calculations, multi-directional table calculations, and combinations of advanced techniques, then troubleshoot them when they produce the wrong answer. The exam assumes you can read a calculation and understand what it does, identify where it breaks, and fix it without trial and error. Nested LODs are particularly fertile ground for errors: the inner LOD might be scoped incorrectly, or the outer aggregation might not match the intended grain. The focus is on precision, not on guessing your way to a working formula.

How Design and Troubleshoot Calculations and Workbooks is tested

This topic generates two out of every five items, so expect a substantial number of scenarios involving calculations, performance, or chart selection. The scenarios are detailed: they describe a workbook, a calculation, or a performance recording, then ask you to identify the problem or recommend the fix. Candidates lose marks when they recommend a chart type without checking whether the data structure supports it, or when they misdiagnose a performance issue because they did not read the recording carefully. Another common mistake is assuming that a slow dashboard needs a faster server, when the real problem is an expensive LOD expression that should be moved upstream. The order of operations is tested directly and indirectly: directly when the scenario asks you to identify the stage causing the issue, indirectly when a calculation behaves unexpectedly and you need to know why. Read the scenario for the symptoms, then trace back to the root cause before choosing your answer.

The final topic shifts from building and fixing workbooks to managing the environment in which they are published, secured, and maintained. At 16 percent it is the lightest of the four, but it covers the operational concerns that determine whether a Tableau deployment scales or collapses under its own weight. You are mapping governance requirements to platform features, recommending access and data quality strategies, using administrative views to gain operational insight, and designing the content lifecycle from build to maintenance.

– Governance strategy and data quality

You need to map an organisation's governance requirements to Tableau features, then recommend strategies for securing access and ensuring data quality. That means understanding the difference between project-level permissions, content permissions, and data source permissions, and knowing when each is the right control. Data quality strategy includes certifying data sources so users know what to trust, minimising proliferation so the environment does not fill with stale or duplicate content, and configuring data quality warnings when a source has known issues. The exam expects you to recognise when a governance requirement can be met with native Tableau features and when it needs an external process or tool. The focus is on designing a strategy that fits the organisation's risk tolerance and operational capacity, not on describing every governance feature in the platform.

– Administrative views and content distribution

Administrative views provide insight into usage, performance, and content health, and you need to know which view answers which question. The exam will test whether you can specify when an administrative view is required, and recommend the appropriate view and data source for a given scenario. For example, if the question is which workbooks are consuming the most server resources, you need the view that shows query load. If the question is which content is unused and can be archived, you need the view that tracks access. Content distribution is the other half of this group: you are mapping publishing requirements to Tableau features, which means understanding the difference between publishing a workbook, publishing a data source, and using subscriptions or alerts. You also need to recommend an approach for the workbook lifecycle, covering building, testing, deployment, distribution, and maintenance. The lifecycle question is about process, not features: who builds, who tests, who approves, and how updates are managed once the workbook is in production.

How Establish Governance and Support Published Content is tested

At 16 percent, this topic generates roughly one question in every six. Scenarios describe an organisation's governance needs, operational constraints, or content management challenges, then ask you to recommend the strategy or identify the correct administrative view. The detail will include the size of the user base, the sensitivity of the data, the maturity of the existing governance process, and the operational capacity of the team. Candidates lose marks when they recommend a governance strategy that is too complex for the organisation to maintain, or when they choose an administrative view that does not answer the question in the scenario. Another common mistake is recommending project-level permissions when content-level permissions are required, or vice versa. The lifecycle question is often missed because candidates focus on the build phase and ignore testing, deployment, or maintenance. Read the scenario for what the organisation can sustain, then choose the answer that fits their capacity and constraints.