Free Salesforce Analytics-Con-301 Exam Dumps July 2026

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.

To shape the data in the 'US Population Estimates' data source and enter the total number of records into the 'Total Records' parameter in Tableau Desktop, follow these steps:

Open the CC Workbook and Access the Worksheet:

From the desktop, double-click on the CC workbook to open it in Tableau Desktop.

Navigate to the Population worksheet by selecting its tab at the bottom of the window.

Format and Shape the Data:

Ensure the data types match those specified in the requirements: Sex, Origin, Race as strings; Year, Age, Population as whole numbers.

To verify or change the data type, click on the dropdown arrow next to each field name in the Data pane and select 'Change Data Type' if necessary.

Calculate Total Number of Records:

Create a new calculated field named 'Total Records'. To do this, right-click in the Data pane and select 'Create Calculated Field'.

Enter the formula COUNT([Record ID]) or SUM([Number of Records]) depending on how the data source identifies each row uniquely.

Drag this new calculated field onto the worksheet to display the total number of records.

Enter the Value into the Total Records Parameter:

Locate the 'Total Records' parameter in the Data pane. Right-click on the parameter and select 'Edit'.

Manually enter the number displayed from the calculated field into the parameter, ensuring accuracy to meet the data shaping requirement.

Save Your Changes:

From the File menu, click 'Save' to ensure all your changes are stored.

Tableau Desktop Guide: Provides detailed instructions on managing data types, creating calculated fields, and updating parameters.

Tableau Data Shaping Techniques: Outlines effective methods for manipulating and structuring data for analysis.

This process will ensure the data in the 'US Population Estimates' is accurately shaped according to the specified format and that the total number of records is correctly calculated and entered into the designated parameter. This thorough approach ensures data integrity and accuracy in reporting.

To complete the Pareto chart in the 'City Pareto' worksheet of your Tableau Desktop and add reference lines to illustrate how the data compares to the Pareto principle, follow these steps:

Open the CC Workbook and Access the Worksheet:

From the desktop, double-click on the CC workbook to open it in Tableau Desktop.

Navigate to the City Pareto worksheet by selecting its tab at the bottom of the window.

Construct the Pareto Chart:

Ensure that sales data is aggregated by city. If not, drag the 'City' dimension to the Columns shelf and the 'Sales' measure to the Rows shelf.

Sort the sales data in descending order to properly align the cities according to their sales contribution.

To create a running total of sales, right-click on the 'Sales' measure on the Rows shelf, select 'Quick Table Calculation', and choose 'Running Total'.

Drag the 'Number of Records' field to the Rows shelf next to the Sales running total. Right-click on it, select 'Quick Table Calculation', and choose 'Running Total'. Set its calculation to 'Percent of Total' from the 'Edit Table Calculation' option to represent the percentage of cities.

Add Reference Lines for the Pareto Principle:

Click on the Analytics tab in the sidebar.

Drag a 'Reference Line' element and drop it onto the chart area.

Set the Reference Line for the Sales axis at 80% to represent the typical Pareto cutoff where 80% of effects come from 20% of causes.

Add another Reference Line on the axis representing the percentage of cities, set at 20%, to visually assess the Pareto principle.

Adjust the Appearance of the Chart:

Format the reference lines by right-clicking on them, selecting 'Edit', and choosing a distinct style or color to make them stand out.

Ensure the chart is clear and labels are appropriately adjusted for easy understanding of the data visualization.

Save Your Changes:

From the File menu, click 'Save' to ensure all your changes are stored.

Tableau Help: Offers detailed guidance on creating Pareto charts and adding reference lines.

Tableau Visualization Best Practices: Provides tips on effectively displaying cumulative data and principles such as Pareto.

By following these steps, you will have successfully enhanced the City Pareto worksheet to include a complete Pareto chart with reference lines that illustrate how the sales data compares to the Pareto principle, making it easier to analyze and communicate the distribution of sales across cities.

Comprehensive and Detailed Explanation From Exact Extract:

Tableau's recommended content governance model for Server and Cloud emphasizes project-based separation between development (''sandbox'') content and certified, production-ready content.

Key points from Tableau governance guidance:

Organizations should define sandbox projects where creators can freely publish and iterate on workbooks and data sources.

Once content is reviewed and validated, it is promoted into ''production'' projects that are designated for trusted content for viewers.

This model allows self-service authoring while keeping tight control over what is exposed to broad viewer audiences.

Option A exactly reflects this model: sandbox projects for ad hoc content, and production projects for validated content.

Option B uses separate sites and the Content Migration Tool, which is heavier to manage and usually reserved for cross-environment moves (such as dev to prod), not necessary for basic project-level governance in a single Tableau Cloud site.

Option C relies on Personal Space. Tableau recommends Personal Space for private drafts, not as the main promotion path, and it is not the primary governance pattern for viewer-facing content.

Option D restricts data source viewing but does not provide a full governance strategy for managing ad hoc versus production dashboards.

Therefore, the correct strategy is sandbox projects plus production projects, which is option A.

Tableau governance whitepapers describing sandbox versus production projects as a best-practice pattern.

Tableau Cloud site administration guidance recommending project structure for self-service and controlled promotion of content.

Comprehensive and Detailed Explanation From Exact Extract:

Key details from the scenario:

The dashboard is on a command center screen.

The environment cannot access the internet.

The data source is real-time (live).

The dashboard must keep itself refreshed automatically.

No human interaction should be required.

From Tableau's documentation:

Dashboard Extension API

Tableau's Extension API allows developers to create custom extensions that can automate refreshing a live dashboard at intervals.

The extension is hosted on the company's internal web server, which solves the ''no internet access'' limitation.

This is the only method in the listed options that:

Works offline

Can auto-refresh the dashboard

Supports a ''screen-based'' live monitoring use case

Uses the existing live connection (no need for extracts)

Thus, A is correct.

Why the other options are wrong:

B. Schedule a Prep Flow

Prep flows do not refresh dashboards.

They only refresh prepared data sources.

The dashboard still won't auto-update unless reopened.

C. Download an extension from Tableau Exchange

Tableau Exchange requires internet access, which the company does not have.

Also, ''sandboxed extensions'' cannot refresh the dashboard at timed intervals.

D. Use extracts and scheduled extract refresh

Extracts require:

A Tableau Server / Cloud schedule

Internet access for Cloud

And extracts are not real-timeThis contradicts the requirement for real-time data and an offline environment.

Comprehensive and Detailed Explanation From Exact Extract:

The key detail of the question:

''filter out particular categories, but wants the percent of total calculation to remain steady even as they filter items in or out.''

This means the percent of total must ignore filters.

Table calculations always operate after filters, except table calc filters like 'Filter on Table Calculation,' and after dimension filters, so filtering categories directly will change the denominator.

Tableau's documented solution for ''percent of total that does not change with filtering'' is:

Use a FIXED LOD to define the stable denominator

A FIXED LOD expression ''freezes'' the aggregation level and is unaffected by dimension filters unless explicitly added to context.

This allows the consultant to compute:

{ FIXED : SUM([Sales]) }

or

{ FIXED [Category] : SUM([Sales]) }

Then percent of total becomes:

SUM([Sales]) / { FIXED : SUM([Sales]) }

The FIXED LOD stores the total before filters are applied, ensuring the percent remains steady.

This is exactly what Tableau documentation explains under:

Level of Detail Expressions

LODs and Order of Operations

Using LODs to create filter-independent calculations

Thus, D is correct.

Why the other answers are wrong:

A. Context Filter

Context filters run before FIXED LODs but after raw data.

If Category is put into context, LOD totals would be reduced.

Table calculation totals still change because table calcs run near the bottom of the pipeline.

B. Data Source Filter

Data source filters remove rows before all table calculations and LODs.

This would make the percent of total incorrect, because filtered-out categories would physically be gone.

C. Aggregate Expression

An aggregate field alone does not solve the issue because it still respects dimension filters.

To record the performance of the Property Transactions dashboard in the NYC Property Transactions.twbx workbook and analyze it using a bar chart, follow these detailed steps:

Open the NYC Property Transactions Workbook:

From the desktop, double-click the NYC Property Transactions.twbx workbook to open it in Tableau Desktop.

Start Performance Recording:

Before doing anything else, navigate to the 'Help' menu in Tableau Desktop.

Select 'Settings and Performance', then choose 'Start Performance Recording'.

Open the Property Transactions Dashboard and Reset Filters:

Navigate to the Property Transactions dashboard within the workbook.

Reset all filters to show all values. This usually involves selecting the dropdown on each filter and choosing 'All' or using a 'Reset' button if available.

Stop the Performance Recording:

Go back to the 'Help' menu.

Choose 'Settings and Performance', then select 'Stop Performance Recording'.

Tableau will automatically open a new tab displaying the performance recording results.

Save the Performance Recording:

In the performance recording results tab, go to the 'File' menu.

Click 'Save As' and navigate to the C:\CC\Data\ directory.

Save the file, ensuring it is stored in the desired location.

Create a New Worksheet for Performance Analysis:

Return to the NYC Property Transactions workbook and create a new worksheet by clicking on the 'New Worksheet' icon.

Drag the 'Command Name' field to the Columns shelf.

Drag the 'Elapsed Time' field to the Rows shelf.

Ensure that the 'Worksheet' field is also included in the analysis to break down the time by individual sheets within the dashboard.

Choose 'Bar Chart' from the 'Show Me' options to display the data as a bar chart.

Customize and Finalize the Bar Chart:

Adjust the axes and labels to clearly display the information.

Format the chart to enhance readability, applying color coding or sorting as needed to emphasize sheets with longer load times.

Save Your Work:

Once the new worksheet and the performance recording are complete, ensure all work is saved.

Navigate to the 'File' menu and click 'Save', confirming that changes are stored in the workbook.

References:

Tableau Help Documentation: Provides guidance on how to start and stop performance recordings and analyze them.

Tableau Visualization Techniques: Offers tips on creating effective bar charts for performance data.

By following these steps, you have successfully recorded and analyzed the performance of the Property Transactions dashboard, providing valuable insights into how each component of the dashboard contributes to the overall load time. This analysis is crucial for optimizing dashboard performance and ensuring efficient data visualization.

Topic 3, Knowledge-Based Section B

To flag orders with sales higher than the regional average, the correct calculated field would compare the sum of sales for each order against the average sales of all orders within the same region:

Correct Formula: { FIXED [Order ID] : SUM([Sales]) } > { FIXED [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) }

This calculation uses a Level of Detail (LOD) expression:

The left part of the formula { FIXED [Order ID] : SUM([Sales]) } calculates the total sales for each individual order.

The right part { FIXED [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) } calculates the average sales per order within each region.

The > operator is used to compare these two values to determine if the sales for each order exceed the regional average.

References This formula utilizes Tableau's LOD expressions to perform complex comparisons across different dimensions of the data, as explained in Tableau's official training materials on LOD calculations.