Salesforce Certified Tableau Consultant Analytics-Con-301 Exam Questions

Answer : A, D

Comprehensive and Detailed Explanation From Exact Extract:

Quick filters are one of the most expensive features in Tableau because they require queries to populate value lists and dynamic recalculations when filters change.

According to Tableau performance documentation:

1. Add an ''Apply'' Button

This prevents Tableau from re-running queries every time the user selects a filter value.

Queries are executed once when the user presses Apply.

This is a documented best practice for filter-heavy dashboards.

2. Replace Quick Filters with Filter Actions

Filter actions are far more efficient because:

They leverage the existing view context

They do not require separate filter UI queries

They avoid the overhead of quick filter value lists

Tableau recommends using filter actions instead of multiple quick filters for better performance.

Why the other options are incorrect:

B . Add filters to Context: Context filters make downstream filters faster, but do not reduce quick filter processing cost; they can even increase extract size and slow down the dashboard.

C . Only Relevant Values: This actually slows performance because Tableau must re-evaluate the entire data set to determine relevancy every time filters update.

Thus, A and D are the correct performance-improvement approaches.

Tableau Performance Checklist recommending Apply button for multi-select filters.

Performance documentation advising the use of Filter Actions over multiple quick filters.

Filtering best practices explaining the cost of Only Relevant Values.

Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

The requirement is:

Compute total sales per customer, not per transaction.

Then compute the average of those customer totals, grouped by region.

Tableau documentation states that FIXED LOD expressions are used to calculate values at a specific level of granularity regardless of the view.

To solve the business need:

Step 1:

Calculate total customer sales for each Customer ID within each Region:

{ FIXED [Customer ID], [Region] : SUM([Sales Amount]) }

This produces one number per customer per region.

Step 2:

Compute the average of those totals:

AVG( { FIXED [Customer ID], [Region] : SUM([Sales Amount]) } )

This yields:

Average total customer sales by region

This is exactly option C.

Why the other options are incorrect:

A . EXCLUDE Region: Would combine regions and incorrectly calculate overall totals.

B . FIXED Region: AVG(Sales Amount): Computes average of line-level sales, not customer totals.

D . FIXED Customer ID + Region: AVG(Sales Amount): Averages individual transactions, not customer totals.

Only option C matches the required two-step logic.

LOD Expressions: FIXED for computing customer-level aggregates.

Nested LOD usage for first calculating customer totals, then averaging them at a higher level.

Tableau guidance: SUM inside FIXED for per-customer totals, AVG outside for averaging customers.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Tableau's row-level security (RLS) is applied at the data source level so that all users who connect to the data source---whether through Tableau Desktop, Server, or Cloud---see only the data they are permitted to see.

According to Tableau documentation:

A Data Source Filter is the correct method for enforcing consistent row-level security for all users.

When a Data Source Filter is applied before publishing, it becomes part of the data source's metadata and is applied every time any user connects to the published source.

This ensures that users creating new workbooks in Tableau Desktop are governed by the same RLS as users viewing published dashboards.

Context filters and extract filters do not provide secure RLS:

A Context Filter only applies inside the workbook where it is created. It does not enforce security in Tableau Desktop when the data source is reused.

An Extract Filter physically removes rows from the extract but does not enforce role-based filtering or dynamic RLS.

''Apply Filter to All Using Related Data Sources'' affects workbook behavior, not published data source security.

A Data Source Filter applied prior to publishing is Tableau's documented approach for secure, reusable row-level security.

Row-Level Security implementation guidance describing Data Source Filters as the foundation of secure RLS.

Tableau Server publishing workflow indicating that Data Source Filters travel with the published source.

Documentation on why Context and Extract Filters do not enforce user-dependent row-level security.

Answer : D

To minimize the impact on users when reverting to a previous version of a published data source in Tableau Server, the consultant should use the built-in revision history feature. By selecting a previous version from the revision history and clicking 'Restore', the data source will revert to that version without the need for a full server backup restoration or manual recreation of the data source. This process is quick and has the least amount of disruption to users.

Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Tableau Catalog provides multiple features for communicating data quality and freshness.

Data Quality Warnings (DQWs) are part of Catalog's metadata management system and are specifically designed to inform users about data issues, including when data is stale.

There are two visibility levels:

1. Standard Visibility Data Quality Warning

Appears subtly in metadata panels.

Intended for non-critical issues.

Does not guarantee the message will be seen by dashboard viewers.

2. High Visibility Data Quality Warning

Designed for urgent, critical, and highly visible alerts.

Displays a prominent warning indicator directly on connected dashboards, data sources, and workbooks.

Tableau documentation states high-visibility warnings are used when users must be alerted, such as:

Stale data

Incomplete refreshes

Data outages

Because the question emphasizes:

''important to alert dashboard viewers when data has not been refreshed''

A standard warning is not strong enough, but a High Visibility Data Quality Warning is explicitly designed for this scenario.

Evaluation of the choices:

A . Standard Visibility Data Quality Warning --- Not sufficient

It does not force dashboard users to notice the warning.

B . High Visibility Data Quality Warning --- Correct

This option is specifically meant to notify users of critical freshness issues, making it the perfect match for the requirement.

C . Certified Data Source --- Incorrect

Certification communicates trustworthiness, not freshness or alerts.

D . Lineage --- Incorrect

Lineage shows data relationships and dependencies, not refresh warnings.

Conclusion

To alert viewers about stale data in hourly-refreshed dashboards, the consultant must use a High Visibility Data Quality Warning.

Reference From Tableau Catalog Documentation

Description of Data Quality Warnings and their visibility levels.

Definition of High Visibility DQWs as critical alerts shown to dashboard viewers.

Catalog guidelines for stale data detection and communication.

Answer : B

The calculation {FIXED [Customer ID], [Region]: COUNTD([Order ID])} is the correct one to use for this scenario. This Level of Detail (LOD) expression will calculate the distinct count of orders for each customer within each region, which is then averaged per month. This approach ensures that the average number of orders per customer is accurately calculated for each region and then broken down by month, aligning with the client's expectations.

The initial calculation provided by the client likely overestimates the average number of orders per customer per month by region due to improper granularity control. The revised calculation must take into account both the customer and the region to correctly aggregate the data:

FIXED Level of Detail Expression: This calculation uses a FIXED expression to count distinct order IDs for each customer within each region. This ensures that the count of orders is correctly grouped by both customer ID and region, addressing potential duplication or misaggregation issues.

Accurate Aggregation: By specifying both [Customer ID] and [Region] in the FIXED expression, the calculation prevents the overcounting of orders that may appear if only customer ID was considered, especially when a customer could be ordering from multiple regions.

Level of Detail Expressions in Tableau: These expressions allow you to specify the level of granularity you need for your calculations, independent of the visualization's level of detail, thus offering precise control over data aggregation.

Answer : A, C

Comprehensive and Detailed Explanation From Exact Extract:

The performance degradation originates from string parsing inside Tableau ('last word of Full Name') and then feeding that calculated field into another row-level IF-THEN calculation.

This creates:

Nested calculations

High per-row evaluation load

Slow extract query performance or slow live query generation

Tableau documentation recommends two best-practice approaches:

Solution 1: Precompute the ''Last Name'' field upstream (Option C)

When the parsing is performed in:

The database

ETL/ELT pipelines

Tableau Prep

then Tableau Desktop receives a clean field with no runtime computation needed.

This significantly reduces row-level calculation burden.

Solution 2: Replace Quick Filters with Action Filters (Option A)

Quick filters are expensive because Tableau:

Runs additional queries to populate filter controls

Re-queries every time the filter changes

Action Filters run directly from the visualization and are far more performant.

This improves the overall dashboard performance without changing logic.

Why the other options are incorrect:

B . Calculate ''Last Name'' inside the IF THEN calculation

This makes the expression even more complex --- worse performance.

D . Change to a CASE statement

CASE does not improve performance when the heavy part of the logic is the string parsing, not the IF-THEN structure.

Thus, A and C are the correct performance-improving choices.

Performance guidance recommending upstream computation of string fields

Filter optimization best practices encouraging Action Filters over Quick Filters

Extract runtime cost reduction strategies