The Salesforce Certified Tableau Consultant (Analytics-Con-301)

The business requirement is:

“Create a line graph that shows daily temperature fluctuations .”

The dataset provided contains:

Only 5 rows , one per month

Two aggregated columns: Avg High Temp and Avg Low Temp

No daily values in the dataset

Tableau’s documentation states that:

Tableau cannot generate artificial granularity that does not exist in the underlying data.

LOD calculations cannot create detail that isn’t present in the source. They can only roll up or fix existing grain; they cannot fabricate lower-grain data.

Pivoting only reshapes data; it does not create missing days or introduce new rows.

When the visualization requires detail that the dataset does not contain, the correct solution is to obtain data at the required level of granularity .

Because the dataset contains monthly averages , it is impossible to show day-to-day fluctuations without having the actual daily temperatures.

Therefore, the only way to support the business need is to request daily-level data from the data provider.

Why the other options are incorrect:

A. Pivot the data

Pivoting would convert the dataset from wide format to long format (e.g., “Avg High Temp” and “Avg Low Temp” into a single “Temperature Type” field).

This does not add daily rows , so the required daily line graph still cannot be built.

C. Create an LOD calculation

LOD expressions cannot create new lower-level detail.

They only aggregate or fix existing detail.

Because the dataset contains only monthly values , an LOD cannot generate daily temperatures.

Tableau granularity and data modeling guidance stating that detail must exist in the data to be visualized.

LOD expression documentation explaining that LODs cannot create lower granularity than the source data.

Pivoting documentation explaining pivots reshape fields but do not generate new rows or finer-grain data.

Comprehensive and Detailed Explanation From Exact Extract:

To combine Excel and SQL Server data in the same logical data model , Tableau offers two supported capabilities:

Relationships

Recommended modern method for combining tables from multiple sources.

Supports cross-database relationships between Excel and SQL Server.

Maintains separate physical layers but integrates data at query time.

Cross-Database Joins

Allows joining data from different databases in the physical layer .

Fully supported for Excel + MS SQL Server.

Useful when granular row-level merging is needed.

Why the other options are incorrect:

C. Data Blending

Legacy feature, used only when no direct combination is possible.

Tableau recommends relationships instead.

Produces separate queries and may lose row-level detail.

D. Union

Requires tables to have equivalent structure.

Cannot union Excel with SQL Server unless identical column structure exists.

Not appropriate for most mixed-source reporting.

Therefore, the correct techniques are Relationships and Cross-Database Joins .

Tableau data modeling documentation recommending Relationships for multi-source modeling.

Cross-database join support list including Excel + SQL Server.

When dashboards are published to Tableau Cloud , the function USERNAME() returns the user’s Tableau Cloud username , which is the email address associated with their Tableau Cloud account.

Tableau documentation states:

On Tableau Cloud, the value returned by USERNAME() is always the user’s email address .

Row-Level Security (RLS) is typically implemented using a comparison of USERNAME() to an email field in the data source.

For secure filtering, the field compared to USERNAME() must match the authentication identity exactly.

Looking at the provided table:

“Abbreviated Name” contains short custom codes like “SMiller,” which do not match Tableau Cloud usernames.

“Lower Case Name” contains names like “sean miller,” which also do not match Tableau Cloud usernames.

“Email” contains the full email address for each user, such as “Sean.Miller@superstore.com,” which is the only field that corresponds to what USERNAME() returns in Tableau Cloud.

Therefore, the correct field to reference is Email .

Tableau Cloud authentication documentation stating USERNAME() returns the user’s email address.

Row-Level Security setup guidance recommending the comparison USERNAME() = [Email Field].

Tableau security practices indicating only the email column will match USERNAME() values on Tableau Cloud.

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.

The correct calculation for classifying profit margins into categories based on specified thresholds involves the use of conditional statements that check ranges in a logical order:

Highly Profitable Classification : The first condition checks if the profit margin is 50% or more. This must use the " > = " operator to include exactly 50% as " Highly Profitable " .

Profitable Classification : The next condition checks if the profit margin is between 0% and 50%. Since any value falling at or above 50% is already classified, this condition only needs to check for values greater than or equal to 0%.

Unprofitable Classification : The final condition captures any remaining scenarios, which would only be values less than 0%.

To improve the performance of a Tableau workbook, it is best practice to streamline the data being used. This can be achieved by using filters to limit the data to only what is necessary for analysis, hiding fields that are not being used to reduce the complexity of the data model, and aggregating values to simplify the data and reduce the number of rows that need to be processed. These steps can help reduce the load on the server and improve the speed of the workbook.

To track which data sources are used most frequently across a site in Tableau Cloud, the client should use the GraphiQL engine and the Metadata API. The GraphiQL engine allows for interactive exploration of the metadata, making it easier to construct and test queries 1 . The Metadata API provides access to metadata and lineage of external assets used by the content published to Tableau Cloud, which is essential for tracking data source usage 2 .

The Explorer (can publish) site role in Tableau is designed for users who need to access, edit, and create visualizations based on published data sources, even when they are outside the company network. This role allows users to perform web editing and save their work, making it suitable for sales users who need these capabilities. It is also a cost-effective option as it does not require the full capabilities and associated costs of the Creator license.

The discrepancy between the count of workbooks in the Connected Workbooks tab and the lineage count in Tableau Catalog can occur because of user permissions. In Tableau Data Management, the visibility of connected workbooks is subject to the permissions set by administrators. If a user does not have permission to view certain workbooks, they will not see them listed in the Connected Workbooks tab, even though these workbooks are part of the data source’s lineage and are counted in Tableau Catalog.