Tableau TDA-C01 Practice Test Questions and Exam Dumps Part3 Q41-60

View Full Tableau TDA-C01 Exam Dumps and Practice Test Dumps

 

Question 41.

An analyst creates a view showing SUM(Sales) by Region. What determines the level of detail at which Tableau aggregates Sales in this view?

  1. The dimensions included in the view
    2. The number of records in the data source
    3. The workbook file size
    4. The extract refresh schedule

Correct Answer: 1

Explanation:

The dimensions present in a Tableau view define the level of detail at which measures are aggregated. If Region is the only dimension in the view, Tableau calculates SUM(Sales) separately for each region. Adding another dimension, such as Category, creates a finer level of detail and causes Tableau to calculate sales for each Region-Category combination. Measures are aggregated according to this dimensional structure unless a calculation explicitly changes the level, such as an LOD expression. Data-source size, workbook size, and extract refresh frequency do not determine the visualization’s aggregation granularity. Understanding the relationship between dimensions and aggregation is fundamental to building accurate Tableau views.

Question 42.

A field named Customer ID contains numbers, but the analyst wants Tableau to treat each ID as a category rather than perform mathematical aggregation. What should the analyst do?

  1. Convert Customer ID to a continuous measure
    2. Convert Customer ID to a dimension
    3. Create a forecast
    4. Add Customer ID to Tooltip only

Correct Answer: 2

Explanation:

Although Customer ID may contain numeric values, the numbers represent identifiers rather than quantities that should be summed or averaged. Converting Customer ID to a dimension tells Tableau to treat the values as categorical members. This allows the analyst to group, filter, label, and partition data by individual customers without meaningless numerical aggregation. Tableau’s initial field classification is based partly on data type, but analysts should change the role when the semantic meaning of the field differs from its technical storage format. A numerical ID is a common example of a field that should usually function as a dimension instead of a measure.

Question 43.

Which Tableau field type normally creates an axis when placed on Rows or Columns?

  1. Discrete dimension only
    2. Set
    3. Continuous field
    4. Group

Correct Answer: 3

Explanation:

Continuous fields generally create an axis representing a range of values when placed on the Rows or Columns shelf. Tableau displays continuous pills in green. For example, a continuous Sales measure can create a numeric axis, while a continuous date can create a timeline. Discrete fields, shown as blue pills, usually create headers representing distinct categories or date parts. Sets and groups can be used categorically but do not inherently define a continuous range. Knowing whether a field is discrete or continuous is important because it affects not only color and pill appearance but also the fundamental structure of the resulting visualization.

Question 44.

An analyst places a discrete YEAR(Order Date) field on Columns. What will Tableau typically display?

  1. One continuous timeline with every individual date
    2. A geographic map
    3. A histogram
    4. Separate headers for individual years

Correct Answer: 4

Explanation:

A discrete date part such as YEAR(Order Date) typically creates separate headers for each year represented in the data. The field appears as a blue pill and partitions the view into categorical year values such as 2023, 2024, and 2025. If the analyst instead uses a continuous year, Tableau displays an axis representing time continuously. This distinction can significantly change how a date-based visualization behaves. Discrete date parts are useful when the analyst wants independent categories, while continuous dates are generally more appropriate when emphasizing the progression of time across a continuous axis.

Question 45.

Which Tableau date level is typically best when an analyst wants to compare sales by individual calendar months without combining January from different years?

  1. A continuous or exact month-year date representation
    2. Discrete MONTH(Order Date) date part only
    3. WEEKDAY(Order Date)
    4. YEAR(Order Date) only

Correct Answer: 1

Explanation:

A month-year representation preserves both the month and year, allowing January 2025 and January 2026 to remain separate points in the analysis. A discrete MONTH date part alone often groups all January values together regardless of year, which is appropriate for seasonal comparison but not for chronological monthly analysis. Using a continuous month date or an equivalent month-year representation produces a sequence of individual months over time. The appropriate date configuration depends on whether the analyst wants seasonal comparisons or an actual timeline. Recognizing the difference between date parts and date values is important for avoiding misleading Tableau results.

Question 46.

An analyst wants to compare average sales per order rather than total sales. Which aggregation should be applied to the Sales measure?

  1. SUM
    2. AVG
    3. MIN
    4. COUNTD

Correct Answer: 2

Explanation:

Applying AVG to Sales calculates the arithmetic mean of the Sales values at the level of detail defined by the view. This can help analysts understand typical transaction or row-level sales values rather than overall volume. SUM would calculate total sales and answer a different question. MIN would return the smallest value, while COUNTD would count unique values rather than calculate an average. Analysts should ensure that the underlying data grain matches what they mean by “per order.” If one order contains multiple rows, a more sophisticated calculation may be necessary to calculate true order-level averages accurately.

Question 47.

Which Tableau function returns the number of distinct values in a field?

  1. COUNT()
    2. SUM()
    3. COUNTD()
    4. ATTR()

Correct Answer: 3

Explanation:

COUNTD() calculates the number of distinct values in a field. For example, COUNTD([Customer ID]) can determine how many unique customers appear at the current level of detail. This differs from COUNT(), which counts non-null records or values and can count the same customer multiple times. SUM() adds numeric values, while ATTR() returns a value only when all underlying records share the same value and otherwise displays an asterisk. Distinct counting is commonly used for customer counts, order counts, product counts, and other analyses where repeated occurrences of the same identifier should only be counted once.

Question 48.

What does the ATTR() aggregation return when all underlying records for a mark have the same value?

  1. The average value
    2. Null
    3. The number of records
    4. That common value

Correct Answer: 4

Explanation:

ATTR() returns the field value when all underlying records associated with a mark contain the same value. If multiple different values are present, Tableau typically displays an asterisk to indicate that the value is not unique at the current level of detail. ATTR is frequently encountered when dimensions from secondary sources or additional fields are included in aggregated views. It helps avoid unintentionally adding another dimension to the visualization’s level of detail. It does not calculate an average or count. Instead, it answers whether a single consistent value represents all underlying records for that mark.

Question 49.

An analyst wants to find customers whose total sales exceed $50,000. Which type of filter is most appropriate after Sales has been aggregated by Customer?

  1. Measure filter on SUM(Sales)
    2. Extract filter on Customer Name only
    3. Data source filter on all records
    4. Geographic filter

Correct Answer: 1

Explanation:

A measure filter can restrict marks according to an aggregated measure such as SUM(Sales). If the view contains Customer Name and SUM(Sales), the analyst can apply a measure filter that retains customers whose total sales exceed $50,000. A simple dimension filter on Customer Name would require manually selecting members rather than evaluating their aggregated performance. Extract and data source filters operate earlier and generally restrict source rows rather than directly evaluating the final customer-level aggregate in the view. Measure filters are therefore appropriate when the filtering condition depends on aggregated quantitative results.

Question 50.

Which filter type limits the rows included in a Tableau extract when the extract is created?

  1. Table calculation filter
    2. Extract filter
    3. Highlight action
    4. Measure Names filter

Correct Answer: 2

Explanation:

An extract filter restricts the data stored in a Tableau extract. For example, an analyst could create an extract containing only the most recent several years or a specific business region. Because excluded rows are not stored in the extract, extract filters can reduce extract size and potentially improve performance. They are evaluated much earlier than worksheet-level filters. A table calculation filter acts on values after table calculations have been computed, while highlight actions affect dashboard interaction rather than source data. Extract filters should be designed carefully because data excluded during extract creation will not be available to worksheet analysis unless the extract is recreated or refreshed with different settings.

Question 51.

Which Tableau filter can be used to restrict data from a connection for all worksheets that use the relevant data source?

  1. Data source filter
    2. Tooltip filter
    3. Pages filter
    4. Trend filter

Correct Answer: 1

Explanation:

A data source filter limits the data available from a particular Tableau data source and can affect all worksheets that depend on that source. It is useful when a workbook should consistently operate on a restricted subset, such as a specific geographic territory or business unit. Because the filter applies at the data-source level, analysts do not need to repeat the same worksheet filter across every view. Extract filters operate specifically during extract creation, while ordinary worksheet filters are generally applied within individual analyses unless explicitly shared. Data source filters can therefore help maintain consistent scope across a workbook.

Question 52.

An analyst applies a table calculation filter to a view. At what general stage does that filter operate?

  1. Before data source filters
    2. Before context filters
    3. Before dimension filters
    4. After the table calculation has been computed

Correct Answer: 4

Explanation:

Table calculation filters operate late in Tableau’s order of operations. Tableau first performs the underlying aggregation and computes the relevant table calculation. The table calculation filter then hides marks based on those calculated results rather than removing underlying source rows before the calculation occurs. This distinction explains why a table calculation filter can produce results that differ significantly from an ordinary dimension filter. Understanding filter order is essential when building Top N calculations, percent-of-total analyses, LOD expressions, and complex dashboards because changing the filter type can change which records participate in intermediate calculations.

Question 53.

Which LOD expression type calculates at dimensions explicitly named in the expression, largely independent of dimensions currently in the view?

  1. FIXED
    2. INCLUDE
    3. EXCLUDE
    4. WINDOW

Correct Answer: 1

Explanation:

A FIXED level-of-detail expression calculates an aggregation using the dimensions explicitly listed inside the expression. For example, { FIXED [Customer ID] : SUM([Sales]) } computes total sales for each customer regardless of many additional dimensions displayed in the view. FIXED expressions are especially useful when the analyst requires a consistent level of aggregation that should not automatically change with the visualization’s granularity. They interact with filters according to Tableau’s order of operations, so context filters can affect them differently from standard dimension filters. INCLUDE and EXCLUDE adjust the view’s detail relative to currently displayed dimensions instead.

Question 54.

Which LOD expression type is most appropriate when a calculation should operate at a finer level of detail than the current visualization?

  1. FIXED only
    2. INCLUDE
    3. EXCLUDE
    4. RANK

Correct Answer: 2

Explanation:

An INCLUDE LOD expression adds specified dimensions to the calculation’s level of detail, allowing Tableau to calculate at a finer granularity than what is currently displayed. For example, if a view shows Region but an analyst needs to calculate a value at the Customer level within each region, an INCLUDE expression can incorporate Customer into the calculation and then aggregate the result back to the view level. EXCLUDE does the opposite by removing dimensions from the calculation. FIXED defines an independent granularity explicitly. INCLUDE is therefore particularly useful when hidden lower-level detail must participate in the calculation.

Question 55.

Which LOD expression should an analyst use when a dimension displayed in the view should be ignored by a particular calculation?

  1. FIXED only
    2. INCLUDE
    3. EXCLUDE
    4. INDEX

Correct Answer: 3

Explanation:

An EXCLUDE level-of-detail expression removes one or more dimensions from the level of detail used for the calculation. Suppose Category and Sub-Category are displayed in a view, but the analyst wants a sales total at the Category level while still displaying individual Sub-Categories. An EXCLUDE expression can remove Sub-Category from the calculation’s granularity. INCLUDE adds dimensions rather than removing them, while FIXED establishes an explicitly defined level. EXCLUDE expressions are particularly useful for comparing detailed marks against a broader parent-level total without restructuring the entire visualization.

Question 56.

An analyst wants to rank products by SUM(Sales) within the current Tableau view. Which feature is best suited to this requirement?

  1. Bin
    2. Data source filter
    3. Relationship
    4. Rank table calculation

Correct Answer: 4

Explanation:

A Rank table calculation assigns an ordering to marks based on an aggregated measure such as SUM(Sales). This allows products to be ranked from highest to lowest within the current partition of the visualization. The analyst must check the Compute Using configuration because the ranking depends on how Tableau addresses and partitions the marks. For example, products might be ranked across the entire table or independently within each category. Bins group numeric values into ranges, relationships define data-model behavior, and data source filters restrict available records. Ranking displayed aggregated results is a classic use of table calculations.

Question 57.

Which quick table calculation would show how Sales changed from the immediately preceding month?

  1. Difference
    2. Percent of Total
    3. Running Total
    4. Rank

Correct Answer: 1

Explanation:

The Difference table calculation compares the current mark with another mark, commonly the immediately previous mark in the chosen addressing direction. In a monthly sales visualization, applying Difference to Sales can show the absolute increase or decrease from the prior month. If the analyst wants a proportional change instead, a Percent Difference calculation may be more appropriate. Running Total accumulates values over time, Percent of Total calculates contribution to a partition, and Rank orders marks. As with all table calculations, the analyst should verify that Tableau is computing across the Month dimension in the intended order.

Question 58.

An analyst wants to emphasize values above and below an average by displaying the average across the visualization. Which analytics object should be added?

  1. Forecast
    2. Reference line
    3. Set control
    4. Story point

Correct Answer: 2

Explanation:

A reference line can display a benchmark such as an average, median, constant target, or parameter-driven value across a visualization. Adding an average reference line makes it easy for viewers to compare each mark against the overall or pane-level average. Tableau lets the analyst choose the line’s scope, formatting, and label. A forecast projects future time-series values, while set controls let users change membership in supported sets. A story point is part of a presentation sequence. When a visual benchmark should be drawn directly on an axis-based chart, a reference line is typically the appropriate feature.

Question 59.

Which Tableau dashboard action allows selecting a mark to update the value of a parameter?

  1. URL action
    2. Filter action
    3. Parameter action
    4. Highlight action

Correct Answer: 3

Explanation:

A parameter action changes a parameter value based on user interaction with marks in a worksheet. For example, selecting a product can write its value into a parameter, which can then drive calculations, titles, reference lines, or other dashboard behavior. This enables more advanced interactions than a standard filter action because the selected value can be reused throughout parameter-dependent logic. Filter actions restrict target data, highlight actions emphasize related marks, and URL actions open external resources. Parameter actions are particularly useful for dynamic comparisons, metric switching, user-selected benchmarks, and other interactive calculations.

Question 60.

A dashboard should open an external customer-management web page when a user clicks a customer mark. Which Tableau action is most appropriate?

  1. Highlight action
    2. Filter action
    3. Set action
    4. URL action

Correct Answer: 4

Explanation:

A URL action allows a Tableau dashboard or worksheet to open an external webpage based on user interaction with a mark. Field values can be inserted into the URL, enabling context-sensitive navigation. For example, selecting a customer could open that customer’s record in a CRM system by passing the Customer ID in the URL. Filter actions modify the data shown in target sheets, highlight actions emphasize related marks, and set actions modify set membership. When the desired outcome is navigation from Tableau to an external web resource, a URL action is the appropriate feature.