ANALYTICS-CON-301 Practice Questions

Tableau Server maintains a revision history for published content, including data sources. The most efficient and least disruptive method to revert to a previous version is to use this built-in functionality. An authorized user can navigate to the data source's revision history, select the desired previous version, and use the "Restore" action. This single-click operation reverts the data source to the selected state while preserving its ID and all existing connections from dependent workbooks, thus minimizing the impact on end-users who will seamlessly connect to the restored version.

A. Restoring a server backup is a disaster recovery action that reverts the entire Tableau Server environment, impacting all users and content, not just a single data source.

B. Deleting and recreating the data source would break all dependent workbooks, requiring them to be manually reconnected, causing significant user disruption and downtime.

C. While downloading and republishing a previous version is technically possible, it is a multi-step, less direct process compared to the built-in "Restore" function, which is designed for this specific task.

1. Tableau Help

"Work with Content Revisions": This official documentation outlines the revision history feature. It states

"For both workbooks and data sources

you can look at the revision history and restore a previous version at any time." The procedure described is to open the revision history and

from the Actions menu for a specific revision

select Restore. This directly supports option D as the intended and most direct method.

2. Tableau Help

"Back Up and Restore": This documentation describes the server-wide backup and restore process (tsm backup and tsm restore). The scope of this operation is the entire repository

file store

and topology

confirming that it is not a suitable solution for reverting a single content item and would have maximum user impact

invalidating option A.

Tableau Catalog, a part of the Tableau Data Management offering, is designed to address issues of data trust and discovery. It provides a comprehensive view of the data environment, including lineage and impact analysis. By using Tableau Catalog, the client can trace the data from the database tables to the published data sources and finally to the visualizations. This allows them to compare the metadata of the seemingly identical data sources, identify subtle differences in joins, filters, or calculated fields, and understand exactly why they produce different results. This visibility is crucial for diagnosing inconsistencies and re-establishing trust in the data.

A. Tableau Prep Conductor: This tool is used to schedule, monitor, and manage Tableau Prep flows on a server. It automates data preparation but does not analyze or compare existing published data sources.

B. Ask Data: This is a natural language query feature that allows users to explore a single data source by asking questions. It is a data consumption tool, not a governance or lineage tool.

D. Tableau Resource Monitoring Tool: This tool monitors the health and performance of the Tableau Server environment, such as hardware utilization and job performance. It does not provide insight into data content or metadata.

1. Tableau Help

"About Tableau Catalog": "With Tableau Catalog

you get a complete view of the data in your Tableau environment... When everyone in your organization can see where data comes from and how it has been changed along the way

they have more confidence in the data." This document explicitly states that Catalog helps build data confidence by showing lineage.

2. Tableau Help

"Use Lineage to See the Impact of Changes": "Lineage traces your data from its original source... For data sources

you can see the upstream databases and tables... and the downstream workbooks

sheets

and dashboards that use the data source." This directly supports the use of Catalog to inspect the composition of data sources.

3. Tableau Help

"Tableau Prep Conductor": "Tableau Prep Conductor is part of the Data Management offering and is used to run your flows automatically on a schedule." This defines its role as an automation tool for data preparation flows

not an analysis tool for existing data sources.

4. Tableau Help

"What is Tableau Resource Monitoring Tool?": "Tableau Resource Monitoring Tool is a tool that provides agent-based monitoring of the health and performance of your Tableau Server cluster." This confirms its purpose is server administration

not data content analysis.

For optimal performance, data processing should be shifted from the query layer (dashboard) to the data preparation layer (Recipe or Dataflow). Aggregating daily data to a monthly level drastically reduces the number of rows in the dataset, which is the most significant factor for query speed. Pre-calculating the required monthly averages in the data layer ensures the dashboard only has to render results, not compute them on the fly. Filtering the data to only the necessary years (current and previous) further reduces the dataset size, adhering to the principle of loading only the data required for the analysis. This combined approach minimizes dataset size and query complexity, leading to the best possible performance.

A. Leaving data at the daily level forces the dashboard's query engine to process a large volume of rows to compute averages at runtime, which is highly inefficient and slow.

C. This option is good but incomplete. It fails to filter out older, unnecessary years, resulting in a larger dataset than required and, therefore, suboptimal performance.

D. This approach is fundamentally flawed as it provides incorrect data. Using the last day of the month is a snapshot, not a monthly average, failing to meet the business requirement.

1. Salesforce Help - CRM Analytics Data Preparation Guide - Aggregate Transformation: "Use the Aggregate transformation to roll up data to a coarser granularity. You can aggregate data to get the sum

average

count

minimum

or maximum of a measure column... Aggregating data can significantly reduce the number of rows in your dataset

which can improve query performance." This supports moving calculations to the data layer and aggregating to the monthly level.

2. Salesforce Help - CRM Analytics Data Preparation Guide - Filter Transformation: "Use the Filter transformation to remove rows that you don’t need in your dataset... For better performance

filter data early in the recipe to reduce the number of rows processed by subsequent transformations." This supports limiting the data to the current and previous years.

3. Salesforce Help - Optimize CRM Analytics Dashboards - Work with Your Datasets: "The number one factor for dashboard performance is the number of rows your queries must process... To reduce the number of rows in your datasets

use a filter transformation in a recipe to remove unneeded data. If you don’t need granular-level data

such as at the second or minute

roll it up." This reference holistically supports the combined strategy in option B.

To create a custom dashboard tracking data source usage in Tableau Cloud, there are two primary methods. The first is to use the Admin Insights project, which is available to site administrators. It contains pre-built, curated data sources, including Site Content, that provide metadata about workbooks, views, and data sources, allowing for the creation of custom administrative views. The second method is to programmatically query the metadata using the Tableau Metadata API. This API allows for detailed, custom queries to discover content and understand the relationships between assets, such as which dashboards are using specific data sources.

B. Query metadata through the GraphiQL engine.

GraphiQL is an in-browser tool used to explore and execute queries against the Metadata API. It is a means of using the API, not a distinct method itself. Option C is more fundamental.

D. Download metadata through Tableau Catalog.

Tableau Catalog is a feature for data discovery and lineage analysis. While it uses the underlying metadata, it does not provide a direct function to download this data for building custom dashboards. The Metadata API is the correct tool for that task.

1. Tableau Cloud Help

"Use Admin Insights to Create Custom Views": This document explains that "Admin Insights provides a curated data source that gives you a snapshot of your site's data... You can use the Admin Insights data sources to create your own custom views..." It specifically lists the "Site Content" (TS Content) data source which "Includes data on workbooks

views

data sources

and their users." This directly supports using this data source to track usage.

2. Tableau Cloud Help

"Tableau Metadata API": This official documentation states

"With the Tableau Metadata API

you can discover and query for all of the content on a Tableau... Cloud site... For example

you can use the Metadata API to... Find all the workbooks that connect to a specific data source." This confirms the API's purpose for accessing the necessary metadata.

3. Tableau Cloud Help

"Metadata API Introduction": This section clarifies the relationship between the API and tools like GraphiQL. It describes the API as the service that allows you to "query for metadata about the content" and GraphiQL as an "interactive

in-browser development environment (IDE)" for using the API. This supports the distinction that the API (Option C) is the method

while GraphiQL (Option B) is a tool.

To calculate a region's percentage of total sales, the formula must divide the sales for that specific region by the grand total sales across all regions. The calculation must be independent of any dimension filters applied to the view.

The expression {FIXED [Region]:sum([Sales])}/{FIXED :SUM([Sales])} achieves this.

The numerator, {FIXED [Region]:sum([Sales])}, calculates the total sales for each distinct region.

The denominator, {FIXED :SUM([Sales])}, calculates the grand total sales across the entire dataset.

Because FIXED Level of Detail (LOD) expressions are computed before regular dimension filters, the denominator remains constant even when the view is filtered to a single region. This ensures the percentage is always calculated against the true grand total.

A. {FIXED [Region]:[Sales]}/{FIXED: SUM([Sales])}

This option is syntactically incorrect. The numerator {FIXED [Region]:[Sales]} is missing a required aggregation function, such as SUM(), before the measure [Sales].

B. {FIXED [Region]:sum([Sales])}

This expression only calculates the total sales for each region. It does not perform the division needed to compute a percentage of the overall total.

D. {FIXED [Region]:sum([Sales])}/SUM([Sales]}

The denominator, SUM([Sales]), is a regular aggregation that is calculated after dimension filters are applied. When the view is filtered to a single region, SUM([Sales]) will only represent that region's sales, making the numerator and denominator equal and incorrectly resulting in 100%.

---

1. Tableau Official Documentation

"Create Level of Detail Expressions in Tableau": This document explains the syntax and behavior of LOD expressions. It states

"FIXED level of detail expressions compute a value using the specified dimensions

without reference to the dimensions in the view." It also clarifies the order of operations

where FIXED LODs are calculated before dimension filters. This supports why {FIXED : SUM([Sales])} correctly calculates the grand total irrespective of the Region filter.

2. Tableau Official Documentation

"Tableau's Order of Operations": This resource provides a diagram showing that Dimension Filters are applied after FIXED LOD calculations. This is the core principle that makes option C work and option D fail. The SUM([Sales]) in option D is subject to the dimension filter

while the {FIXED} calculation in option C is not.

3. Salesforce Help

"Create Complex Calculated Expressions": While the syntax is from Tableau

the concept applies to CRM Analytics. This documentation discusses creating advanced formulas. The principle of fixing a calculation to a specific level of grouping (or to the entire dataset) to avoid being affected by other filters or groupings in the visualization is a fundamental concept covered. The {FIXED} syntax is a direct way to implement this principle.

The discrepancy arises because Tableau Catalog's lineage view is permission-aware, while the "Connected Workbooks" tab is not, in the same way. The lineage tool in Tableau Catalog only displays downstream assets, such as workbooks, that the current user has permission to view. In contrast, the "Connected Workbooks" tab on a data source page lists all workbooks connected to it, assuming the user has permission to see the data source itself. Therefore, if a user has permission to view the data source but not some of the workbooks connected to it, the count in the lineage view will be lower than the count in the "Connected Workbooks" tab.

A. Some workbooks have been connected to the data source, but do not use any fields from it.

This is incorrect. Both the Connected Workbooks tab and Catalog lineage track the connection at the workbook level, regardless of whether specific fields are used in a visualization.

B. Some workbooks have not been viewed by enough users yet.

This is incorrect. Tableau Catalog's indexing and lineage display are based on published content and user permissions, not on the popularity or view count of the content.

D. Some Creators have connected to the data source in Tableau Desktop but have not yet published a workbook.

This is incorrect. Both Tableau Catalog and the Connected Workbooks tab only operate on content that has been published to Tableau Server or Tableau Cloud. Local, unpublished connections are not tracked.

1. Tableau Help - Use Lineage to See the Impact of Changes: "Lineage is permission-aware. You only see the items you have permission to see. For more information about permissions

see Permissions." This statement directly supports the correct answer by confirming that the lineage view is filtered by user permissions.

2. Tableau Help - About Tableau Catalog: "With Tableau Catalog

you can see the metadata for content that is published to your Tableau Server or Tableau Cloud site... When users explore Catalog

they can see metadata about the assets they have permissions to see..." This reinforces that Catalog's visibility is governed by the user's permissions on each asset.

The most effective and recommended approach is to build a single dashboard and utilize the built-in device layout feature. This allows a consultant to create customized layouts for desktop, tablet, and phone experiences within one dashboard asset. By tailoring the arrangement and visibility of components for each specific layout and using a fixed size for predictability, the consultant can ensure an optimal and consistent user experience across all devices. This method centralizes maintenance, as any change to the underlying data or queries only needs to be done once.

B. Build one dashboard and fix the size of the dashboard.

A single fixed-size dashboard will not adapt to different screen sizes, resulting in scrollbars or poorly utilized space, which degrades the user experience on most devices.

C. Build one dashboard and set the size to Automatic.

Automatic sizing can cause unpredictable resizing and distortion of dashboard components, especially when viewed on screens with vastly different aspect ratios, leading to a poor user experience.

D. Build one dashboard for each type of device and fix thesize of the layouts.

This approach is highly inefficient. Managing three separate dashboards creates a significant maintenance overhead, as any update must be replicated across all three versions.

1. Salesforce Help Documentation

"Optimize Dashboards for Different Devices": This document explicitly states

"Create layouts for the different devices that your users have. You can create a single dashboard and then add layouts that are optimized for viewing on desktops

tablets

and phones... Each layout can have its own widgets

with their own customizations." This directly supports creating one dashboard with multiple

specific layouts.

2. Tableau Help Documentation

"Create Dashboard Layouts for Different Device Types": (The underlying technology for CRM Analytics dashboards). This guide details the process: "You can design

customize

and publish a single dashboard that includes unique layouts for desktop computers

tablets

and phones... When you publish a dashboard with device layouts

people who view it... see a layout optimized for their screen." This confirms that a single dashboard with multiple layouts is the intended and optimal method.

3. Tableau Help Documentation

"Size and Lay Out Your Dashboard": This document contrasts different sizing options. It explains that a "Fixed" size provides control

which is essential for device-specific layouts

while "Automatic" sizing "can cause views to be resized or scrunched in unexpected ways

" making it unsuitable for delivering the best user experience.

The core problem is data densification—creating rows for dates that are missing in the source data. The key constraint is that the user cannot modify the source data warehouse. Tableau Prep is the ideal tool for this scenario. It is a data preparation tool that can connect to the source, generate the missing daily rows using its "New Rows" feature, and then output a new, complete data source (like a Hyper extract). This new source can then be used in Tableau Desktop for visualization, effectively solving the problem without altering the original database.

A. Creating a temporary table is a database-level modification, which the prompt explicitly states the business unit cannot perform.

B. Visualizing nulls in Tableau Desktop creates visual placeholders on an axis but does not generate new data rows to be used for analysis.

C. This option directly violates the constraint that the client does not have the ability to modify the data warehouse structure.

1. Tableau Prep Builder Help

"Generate Missing Rows to Fill in Gaps in Your Data": This official documentation directly addresses the scenario. It states

"Starting in Tableau Prep Builder version 2021.1.3

you can generate new rows for your data set to fill in the gaps in your sequential data

like date and time or integers." This describes the exact functionality needed to solve the client's problem.

Source: Tableau Help

Salesforce. (Accessed under the topic "Clean and Shape Data" > "Generate Missing Rows to Fill in Gaps in Your Data").

2. Tableau Desktop and Web Authoring Help

"Show or Hide Missing Values or Empty Rows and Columns": This document explains the "Show Missing Values" feature in Tableau Desktop. It clarifies that this is a display option for continuous date or bin fields on an axis

which helps visualize gaps but does not create a new

densified data source as Tableau Prep does. This makes it a less robust solution than preparing the data correctly upstream.

Source: Tableau Help

Salesforce. (Accessed under the topic "Build Charts and Analyze Data" > "Format at the Worksheet Level" > "Show or Hide Missing Values or Empty Rows and Columns").

The simulation requires performing a series of actions where the final step, entering the total record count, depends on the specific data file. The correct procedure is as follows:

1. On the Data Source page, verify the data types. Click the icon next to each field name and select the correct type as specified in the image (e.g., String for Sex, Number (whole) for Year).
2. Navigate to the Population worksheet.
3. In the Data pane, locate the measure named US Population Estimates(Count).
4. Drag this US Population Estimates(Count) field onto the Text mark. The view will update to show a single number, which is the total record count.
5. In the Data pane, right-click the Total Records parameter and select Show Parameter.
6. Enter the number from step 4 into the Total Records parameter card that appears in the view.
7. Click File > Save.

Tableau Help (Official Documentation). Data Types.

Section: "Change the data type for a field in the Data Source page"

Relevance: Confirms the procedure for Step 1, which is to click the data type icon on the Data Source page grid and select the correct type (e.g., "String", "Number (whole)") from the drop-down menu.

Tableau Help (Official Documentation). Relate Your Data.

Section: "Options for validating relationships and the data model"

Relevance: Confirms the procedure for Step 3 and 4. It states: "Every table includes a count of its records, as a field named TableName(Count)... To see the count for a table, drag its Count field into the view."

Tableau Help (Official Documentation). Create Parameters.

Section: "Show a parameter control in the viz"

Relevance: Confirms the procedure for Step 5 and 6. To show the parameter control card, "right-click (Control-click) the parameter in the Data pane and select Show Parameter." The value can then be entered into this card.

To display a cumulative percentage line, a multi-step table calculation is required. The primary Running Total calculation computes the cumulative sum of sales across the products. The secondary Percent of Total calculation then converts these cumulative sums into a percentage of the overall total. This result is placed on a second axis (Dual Axis), changed to a line mark, and synchronized with the primary axis to overlay the cumulative percentage line onto the original chart. This technique is a standard method for creating a Pareto chart to visualize cumulative contribution.

1. Salesforce

Tableau Desktop and Web Authoring Help. (2024). "Create a Pareto Chart". This official documentation provides the exact step-by-step instructions to add a running total percent of total line to a chart using a secondary table calculation and a dual axis

as required by the simulation.

2. Salesforce

Tableau Desktop and Web Authoring Help. (2024). "Transform Values with Table Calculations". Section: "Types of table calculations". This document defines the core functions used in the solution

specifically explaining the Running Total and Percent of Total table calculations.

3. Salesforce

Tableau Desktop and Web Authoring Help. (2024). "Build a Combination Chart with a Dual Axis". This document explains the concept and procedure for using dual axes to combine multiple measures with different mark types (e.g.

bars and lines) in a single view

which is a key part of the required solution.