{"id":23332,"date":"2026-09-28T05:07:29","date_gmt":"2026-09-28T05:07:29","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23332"},"modified":"2026-09-28T05:07:29","modified_gmt":"2026-09-28T05:07:29","slug":"tableau-tda-c01-practice-test-questions-and-exam-dumps-part7-q121-140","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/tableau-tda-c01-practice-test-questions-and-exam-dumps-part7-q121-140\/","title":{"rendered":"Tableau TDA-C01 Practice Test Questions and Exam Dumps Part7 Q121-140"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/tda-c01-exam-dumps\"><b>Tableau TDA-C01 Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<p><b>Question 121.<\/b><\/p>\n<p><b>An analyst wants to show sales for the top 10 customers within a selected Region rather than the top 10 customers across the entire data source. What should the analyst do?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Add the Region filter to context before applying the Top 10 Customer filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Convert Customer Name to a measure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Apply the Top 10 filter before adding Region anywhere in the workbook<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Use a highlight action instead of filtering<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Tableau&#8217;s order of operations determines how different filters interact. A standard Top N dimension filter may be evaluated before an ordinary dimension filter, which can cause Tableau to determine the top customers across the broader dataset rather than within the selected Region. Adding Region to context creates a filtered subset first. The Top 10 Customer filter is then evaluated against that context, returning the top customers specifically within the selected region. Context filters are therefore useful when one filter must establish the dataset on which another filter operates. They should be used deliberately because they can also influence workbook performance and the behavior of other calculations.<\/span><\/p>\n<p><b>Question 122.<\/b><\/p>\n<p><b>Which Tableau filter generally operates after context filters but before measure filters?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Table calculation filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Dimension filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Forecast filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Reference line filter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">In Tableau&#8217;s general order of operations, context filters are evaluated before standard dimension filters. Measure filters are applied later because they operate on aggregated measure values after the dimensional grouping has been established. This ordering is important in analyses involving Top N filters, FIXED LOD calculations, and aggregated measures. For example, turning a dimension filter into a context filter can change the data that a later dimension filter considers. Table calculation filters operate much later, after table calculations have been computed. Understanding these stages helps analysts diagnose cases where a filter appears to produce unexpected results even though the filter conditions themselves seem correct.<\/span><\/p>\n<p><b>Question 123.<\/b><\/p>\n<p><b>An analyst wants to calculate total Sales for each Customer before any ordinary dimension filters are applied, while still allowing context filters to affect the result. Which calculation is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Running Total<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> INCLUDE LOD<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">{ FIXED [Customer ID] : SUM([Sales]) }<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">WINDOW_SUM(SUM([Sales]))<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A FIXED level-of-detail expression computes its result at the dimensions explicitly specified in the expression rather than simply following the view&#8217;s current dimensionality. FIXED LOD expressions are evaluated after context filters but before ordinary dimension filters in Tableau&#8217;s order of operations. Therefore, <\/span><span style=\"font-weight: 400;\">{ FIXED [Customer ID] : SUM([Sales]) }<\/span><span style=\"font-weight: 400;\"> can calculate customer-level sales totals that remain independent of many dimensions and ordinary filters later added to the view. INCLUDE and table calculations are evaluated differently. This behavior makes FIXED calculations especially useful when analysts need a stable denominator, customer lifetime metric, or entity-level total that should not automatically change with ordinary worksheet filtering.<\/span><\/p>\n<p><b>Question 124.<\/b><\/p>\n<p><b>Which Tableau LOD expression is best when an analyst wants to calculate customer-level Sales even though Customer is not displayed in the visualization?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> EXCLUDE<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> FIXED only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Table calculation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> INCLUDE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An INCLUDE LOD expression adds a specified dimension to the level of detail used for the calculation even when that dimension is not present in the visualization. For example, <\/span><span style=\"font-weight: 400;\">{ INCLUDE [Customer ID] : SUM([Sales]) }<\/span><span style=\"font-weight: 400;\"> can calculate values at the Customer level and then aggregate those results back to the broader level displayed in the view. This is useful for metrics such as average customer sales by Region when Customer itself is not visible. EXCLUDE removes a dimension from the calculation, whereas FIXED explicitly defines a calculation level that is more independent of the view. INCLUDE is specifically designed to introduce finer granularity into a calculation.<\/span><\/p>\n<p><b>Question 125.<\/b><\/p>\n<p><b>An analyst displays Category and Sub-Category but wants a calculation that returns total Sales for the Category, ignoring Sub-Category. Which approach is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Use an EXCLUDE LOD expression that excludes Sub-Category<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Create a bin from Sub-Category<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Convert Sales to a dimension<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Apply a table calculation filter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">EXCLUDE LOD expressions remove selected dimensions from the level of detail used by a calculation. If both Category and Sub-Category are visible, an expression such as <\/span><span style=\"font-weight: 400;\">{ EXCLUDE [Sub-Category] : SUM([Sales]) }<\/span><span style=\"font-weight: 400;\"> calculates Sales at the broader Category level while still allowing Sub-Category marks to remain displayed. This makes it useful for comparisons between a detailed value and its parent-level total. Bins are designed for numeric ranges and do not change calculation granularity. Converting Sales to a dimension would alter its analytical role, and a table calculation filter would affect displayed marks rather than defining the desired aggregation level.<\/span><\/p>\n<p><b>Question 126.<\/b><\/p>\n<p><b>A worksheet shows Sales by Month. Which table calculation would display the cumulative Sales amount through each month?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Percent Difference<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Running Total<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Rank<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Percent of Total<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Running Total accumulates the measure as Tableau moves through the marks according to the calculation&#8217;s addressing direction. If Month is ordered chronologically, applying Running Total to SUM(Sales) produces cumulative sales through each month. This is useful for year-to-date analysis, goal tracking, and cumulative growth visualizations. The Compute Using setting should be checked because it determines whether Tableau calculates across months, categories, or another dimension in the view. Percent Difference measures change relative to another mark, Rank orders values, and Percent of Total measures contribution to a total. For cumulative progression over time, Running Total is the appropriate quick table calculation.<\/span><\/p>\n<p><b>Question 127.<\/b><\/p>\n<p><b>Which Tableau table calculation should an analyst use to show the percentage increase or decrease in Sales compared with the previous month?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Running Total<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Rank<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Percent Difference<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Percent of Total<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Percent Difference compares the current value with another value, commonly the immediately previous mark, and expresses the change as a percentage. In a monthly Sales chart, this can show month-over-month growth or decline. The analyst should ensure that the calculation is addressed across Month in chronological order so the comparison is made against the correct previous period. Running Total accumulates values rather than showing period-to-period change. Rank orders marks based on magnitude, and Percent of Total expresses each mark&#8217;s contribution to a total. For relative change between consecutive months, Percent Difference is the most appropriate table calculation.<\/span><\/p>\n<p><b>Question 128.<\/b><\/p>\n<p><b>An analyst wants to rank Sub-Categories by SUM(Sales), with the highest-selling Sub-Category receiving rank 1. Which feature is appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Group<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Bin<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Context filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Rank table calculation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Rank table calculation assigns a position to each mark based on the value of an aggregated measure. Applying Rank to SUM(Sales) can give the highest-selling Sub-Category rank 1, the next highest rank 2, and so forth. The result depends on how Tableau partitions and addresses the calculation, so the analyst should verify the Compute Using setting, particularly if Category or Region is also present. Groups combine dimension members, bins create numeric ranges, and context filters affect filter order. Ranking displayed aggregate results is a classic table-calculation use case and provides dynamic ordering as the underlying values or filters change.<\/span><\/p>\n<p><b>Question 129.<\/b><\/p>\n<p><b>Which Tableau table calculation returns the sequential position of a mark within its current partition, independent of the mark&#8217;s measure value?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> INDEX()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> RANK()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> SIZE()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> LOOKUP()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">INDEX()<\/span><span style=\"font-weight: 400;\"> returns the sequential position of a mark within a table-calculation partition, beginning with 1. Unlike <\/span><span style=\"font-weight: 400;\">RANK()<\/span><span style=\"font-weight: 400;\">, INDEX does not determine position based on the magnitude of a measure. Instead, it reflects the ordering of marks in the current view. This makes INDEX useful for row numbering, advanced filtering, pagination-style logic, and certain custom table calculations. The result can change when the view&#8217;s sort order or Compute Using configuration changes. <\/span><span style=\"font-weight: 400;\">SIZE()<\/span><span style=\"font-weight: 400;\"> returns the total number of marks in the partition, while <\/span><span style=\"font-weight: 400;\">LOOKUP()<\/span><span style=\"font-weight: 400;\"> retrieves a value from another mark at a specified relative offset. INDEX is therefore specifically associated with positional numbering.<\/span><\/p>\n<p><b>Question 130.<\/b><\/p>\n<p><b>Which Tableau table-calculation function can retrieve the value of an expression from a previous or next row in the current partition?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> SIZE()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> LOOKUP()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> INDEX()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> WINDOW_MAX()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">LOOKUP()<\/span><span style=\"font-weight: 400;\"> returns the value of an expression from a row at a specified relative offset within the table-calculation partition. For example, <\/span><span style=\"font-weight: 400;\">LOOKUP(SUM([Sales]), -1)<\/span><span style=\"font-weight: 400;\"> can return the previous mark&#8217;s sales value when the view is addressed appropriately. This makes it useful for custom period-over-period calculations, comparisons, and identifying changes between adjacent marks. INDEX returns a mark&#8217;s sequential position, while SIZE returns the total number of marks in the partition. WINDOW_MAX evaluates the maximum value across a defined window. Because LOOKUP accesses a different row relative to the current mark, it is particularly useful for previous-period and next-period calculations.<\/span><\/p>\n<p><b>Question 131.<\/b><\/p>\n<p><b>Which Tableau table-calculation function returns the sum of values across a specified window of marks?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> WINDOW_SUM()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> SUM() only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> RANK()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> ATTR()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">WINDOW_SUM()<\/span><span style=\"font-weight: 400;\"> calculates the sum of an expression across a defined set of marks in the current partition. The window can include the entire partition or a specific range relative to the current mark. For example, it can be used to calculate a moving total or to build a customized denominator for percentage calculations. Unlike ordinary <\/span><span style=\"font-weight: 400;\">SUM()<\/span><span style=\"font-weight: 400;\">, which aggregates underlying data according to the view&#8217;s level of detail, WINDOW_SUM operates on the aggregated marks already present in the visualization. This distinction is important because table calculations are evaluated later in Tableau&#8217;s processing sequence and depend on the layout, addressing, and partitioning of the view.<\/span><\/p>\n<p><b>Question 132.<\/b><\/p>\n<p><b>Which Tableau feature should an analyst use to display an overall average Sales line across a bar chart?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Forecast<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Trend line<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Bin<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Reference line<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A reference line can display a benchmark such as an average, median, constant, or parameter-controlled value on an axis-based visualization. Adding an average reference line to a Sales bar chart lets viewers quickly determine which categories are above or below the overall benchmark. The analyst can control whether the reference line applies to the entire table, each pane, or each cell depending on the chart structure. A trend line models relationships or trends, while forecasting projects future values. Bins group numeric values into intervals. When a single benchmark should be visually overlaid on a chart, a reference line is the appropriate Tableau analytics object.<\/span><\/p>\n<p><b>Question 133.<\/b><\/p>\n<p><b>An analyst wants to display an acceptable Sales range between $80,000 and $120,000 as a shaded area in a chart. What should be added?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Reference band<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Trend line<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Hierarchy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Set<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A reference band displays a shaded region between two values on an axis, making it appropriate for showing an acceptable or expected range. In this example, the analyst can define the lower boundary at $80,000 and the upper boundary at $120,000. Viewers can then immediately see which marks fall below, inside, or above the target range. Reference lines display a single value rather than a bounded area. Trend lines model patterns in data, while hierarchies and sets serve entirely different analytical purposes. Reference bands are particularly useful for tolerance limits, service-level ranges, performance zones, and expected operating intervals.<\/span><\/p>\n<p><b>Question 134.<\/b><\/p>\n<p><b>Which visualization is generally most appropriate for comparing one quantitative measure across several discrete categories when precise comparisons are important?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Pie chart<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Bar chart<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Packed bubbles<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Treemap<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Bar charts use length along a common baseline, which allows viewers to compare values accurately across categories. They are therefore generally preferable to pie charts, packed bubbles, or treemaps when precise categorical comparisons are important. Sorting the bars can further improve interpretation by making high and low values obvious. Pie charts rely on angle and area, which are harder to compare precisely, while packed bubbles and treemaps are better for high-level magnitude or composition. Bar charts remain one of Tableau&#8217;s most effective general-purpose visualization types because they are simple, familiar, and perceptually accurate for categorical comparisons.<\/span><\/p>\n<p><b>Question 135.<\/b><\/p>\n<p><b>A view contains hundreds of categories. The analyst wants to focus on the 10 categories with the highest SUM(Profit). Which Tableau feature should be used?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Parameter only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Geographic role<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Top N dimension filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Pages shelf<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Top N dimension filter can keep only a specified number of members based on an aggregated measure. The analyst can configure the Category field to display the top 10 members by SUM(Profit). Unlike sorting alone, which simply changes order, a Top N filter removes lower-ranked categories from the displayed result. This reduces clutter and helps viewers focus on the strongest performers. Tableau&#8217;s order of operations should be considered when other dimension filters are involved because the Top N calculation may need a context filter to produce results within a desired subset. Parameters can make N dynamic, but they do not perform the filtering by themselves.<\/span><\/p>\n<p><b>Question 136.<\/b><\/p>\n<p><b>An analyst wants dashboard users to choose whether a chart displays Sales, Profit, or Quantity without creating three separate worksheets. Which solution is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Create three extracts<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Create three context filters<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Use three separate data sources<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Use a parameter with a calculated field that returns the selected measure<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A parameter can present options such as Sales, Profit, and Quantity to the user. A calculated field can then evaluate the selected parameter value and return the appropriate measure. The visualization uses that single calculated field, allowing the same worksheet to switch dynamically between measures. This approach reduces workbook complexity and makes the dashboard more flexible. Separate extracts, context filters, or data sources would add unnecessary complexity and would not directly provide a clean metric-switching mechanism. Parameter-driven measure selection is a common Tableau design pattern for interactive dashboards and can also be combined with dynamic titles so viewers always know which metric is currently displayed.<\/span><\/p>\n<p><b>Question 137.<\/b><\/p>\n<p><b>Which dashboard action should an analyst configure when clicking a customer mark should update a parameter containing that Customer ID?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Parameter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Highlight action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> URL action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Filter action<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A parameter action updates a Tableau parameter using a value from a selected mark. If Customer ID is used as the source field, clicking a customer can write that identifier into the parameter. Calculated fields, titles, reference lines, and other logic that depend on the parameter can then respond to the user&#8217;s selection. A filter action restricts target worksheet data, while a highlight action emphasizes related marks. URL actions open external resources. Parameter actions are particularly valuable when the selection should influence calculations rather than simply filter data and can support highly interactive, application-like Tableau dashboard experiences.<\/span><\/p>\n<p><b>Question 138.<\/b><\/p>\n<p><b>Which dashboard action should be used when selecting a mark should change which dimension members are IN or OUT of an existing Tableau set?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Filter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Set action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> URL action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Highlight action<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A set action changes the membership of a Tableau set based on user interaction with marks. For example, selecting several customers can place those customers into a set and allow calculated fields to compare the selected customers with everyone else. This supports interactive cohort analysis, proportional brushing, custom highlighting, and IN-versus-OUT comparisons. A filter action removes unrelated marks from target views, whereas a highlight action simply emphasizes related marks. URL actions navigate to external resources. Set actions provide more analytical flexibility because set membership can be used throughout calculations and visual encodings rather than merely controlling which rows remain visible.<\/span><\/p>\n<p><b>Question 139.<\/b><\/p>\n<p><b>Which dashboard action is best when selecting a Region should emphasize corresponding marks in other worksheets but leave all other marks visible?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Filter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Parameter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Highlight action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> URL action<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A highlight action emphasizes marks related to a user&#8217;s selection while keeping the complete target view visible. This allows the viewer to maintain context while focusing attention on the selected Region. A filter action would instead remove unrelated marks from the target worksheet, which would change the displayed dataset. Parameter actions update parameters, and URL actions open external pages or resources. Highlight actions are particularly useful when the analytical task involves comparison, because users can see both the selected data and the surrounding population simultaneously. This can make patterns and differences easier to understand than filtering everything else from the view.<\/span><\/p>\n<p><b>Question 140.<\/b><\/p>\n<p><b>A user selects an Order ID in a dashboard and should be taken to that order&#8217;s page in an external web application. Which Tableau feature is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Set action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Parameter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Filter action<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> URL action<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A URL action allows Tableau to open an external web address in response to user interaction. The URL can include values from the selected mark, such as Order ID, allowing Tableau to construct a context-specific link to the corresponding record in another application. This can connect Tableau dashboards with CRM systems, support portals, inventory tools, or other internal web applications. Set actions modify set membership, parameter actions update parameter values, and filter actions restrict data in target worksheets. When the required interaction involves navigating from Tableau to an external web resource using data from the selected mark, a URL action is the appropriate choice.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Tableau TDA-C01 Exam Dumps and Practice Test Dumps &nbsp; Question 121. An analyst wants to show sales for the top 10 customers within a selected Region rather than the top 10 customers across the entire data source. What should the analyst do? Add the Region filter to context before applying the Top 10 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23332"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=23332"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23332\/revisions"}],"predecessor-version":[{"id":23333,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23332\/revisions\/23333"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}