{"id":23326,"date":"2026-09-28T05:06:43","date_gmt":"2026-09-28T05:06:43","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23326"},"modified":"2026-09-28T05:06:43","modified_gmt":"2026-09-28T05:06:43","slug":"tableau-tda-c01-practice-test-questions-and-exam-dumps-part4-q61-80","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/tableau-tda-c01-practice-test-questions-and-exam-dumps-part4-q61-80\/","title":{"rendered":"Tableau TDA-C01 Practice Test Questions and Exam Dumps Part4 Q61-80"},"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 61.<\/b><\/p>\n<p><b>An analyst wants to display total sales for each state on a filled map. Which Tableau field characteristic is required for State to be recognized appropriately?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> It must be converted to a measure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> It should have an appropriate geographic role<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> It must be placed in a set<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> It must be converted to a continuous numeric field<\/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;\">Tableau uses geographic roles to recognize fields that represent locations such as Country, State, City, Postal Code, and Latitude or Longitude. Assigning the correct geographic role allows Tableau to generate geographic coordinates and create maps from the field. Once State is recognized geographically, the analyst can add Sales to Color to create a filled map that represents sales magnitude by state. Converting the field into a measure or numeric field would not provide the required geographic meaning. Geographic roles therefore help Tableau distinguish location values from ordinary categorical text and support automatic map creation.<\/span><\/p>\n<p><b>Question 62.<\/b><\/p>\n<p><b>A Tableau map shows several locations as unknown. What should the analyst do first to resolve the issue?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Edit the locations and provide additional geographic context<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Convert the geographic field to a measure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Remove all filters<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Create a trend line<\/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;\">Unknown locations often occur because Tableau cannot uniquely identify a geographic value. For example, multiple cities may share the same name, or the data may contain abbreviations that Tableau does not recognize. The analyst can use Edit Locations to provide additional context such as country, state, or region, or manually correct unresolved values. This helps Tableau geocode the data accurately. Removing filters or changing the field into a measure would not address the geographic ambiguity. Proper geographic context is especially important when datasets contain cities, postal codes, or administrative regions that may have duplicate names across different countries or territories.<\/span><\/p>\n<p><b>Question 63.<\/b><\/p>\n<p><b>Which Tableau visualization is generally best for comparing actual performance against a target while also showing qualitative performance ranges?<\/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;\"> Scatter plot<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Bullet graph<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Packed bubbles<\/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 bullet graph is designed to compare an actual measure against a target or benchmark while optionally showing qualitative ranges such as poor, satisfactory, and excellent performance. It provides a compact alternative to gauges and is particularly useful in performance dashboards. For example, current sales can be displayed against a sales target with background bands indicating performance thresholds. Scatter plots are better for relationships between measures, pie charts emphasize composition, and packed bubbles show relative magnitude. When the analytical goal is performance-to-target comparison in a space-efficient format, a bullet graph is generally the most appropriate visualization.<\/span><\/p>\n<p><b>Question 64.<\/b><\/p>\n<p><b>Which Tableau chart type is most appropriate when an analyst wants to compare one measure across many categories using horizontal bars?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Line chart<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Histogram<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Area chart<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Bar chart<\/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 bar chart is one of the clearest visualizations for comparing quantitative values across discrete categories. Horizontal bars are especially useful when category names are long or when many categories need to be displayed. The length of each bar provides an intuitive representation of relative magnitude. Sorting the bars by the measure can further improve readability. Line and area charts are better suited to continuous trends, particularly over time, while histograms show distributions of a continuous measure. For straightforward categorical comparison, a bar chart is typically the preferred choice because it allows viewers to compare values accurately and quickly.<\/span><\/p>\n<p><b>Question 65.<\/b><\/p>\n<p><b>An analyst wants to identify whether Sales and Profit have a positive or negative relationship across customers. Which visualization should be created?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Scatter plot<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Treemap<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Text table<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Pie chart<\/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 scatter plot places one continuous measure on each axis and creates marks representing entities such as customers. Plotting Sales against Profit allows the analyst to identify whether higher sales generally correspond to higher profits, lower profits, or no consistent relationship. Outliers and clusters may also become visible. Tableau can add a trend line to help assess the overall pattern. Treemaps and pie charts emphasize composition, while text tables are better for detailed numerical lookup. When the primary question involves the relationship between two quantitative measures, a scatter plot is generally the most informative visualization.<\/span><\/p>\n<p><b>Question 66.<\/b><\/p>\n<p><b>Which Tableau feature allows an analyst to divide numeric values into ranges such as 0\u201399, 100\u2013199, and 200\u2013299?<\/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;\"> Set<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Hierarchy<\/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 bin groups continuous numeric values into discrete ranges of a specified size. If the bin size is 100, values can be grouped into intervals such as 0\u201399, 100\u2013199, and 200\u2013299 depending on the data. Bins are commonly used when building histograms because they make distributions easier to analyze. A group combines dimension members into custom categories, while a set defines membership in a subset. A hierarchy organizes related dimensions into drill-down levels. Bins are specifically designed for numeric range grouping and are therefore the correct Tableau feature for this requirement.<\/span><\/p>\n<p><b>Question 67.<\/b><\/p>\n<p><b>An analyst wants to display how frequently individual transaction values fall into different Sales ranges. Which chart is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Map<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Gantt chart<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Histogram<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Pie chart<\/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 histogram displays the distribution of a continuous measure by placing values into bins and showing the frequency of records within each bin. It is ideal for understanding whether transaction values are concentrated in certain ranges, whether the distribution is skewed, and whether unusually high or low values exist. A map is for geographic analysis, while a Gantt chart is commonly used to display duration or scheduling relationships. Pie charts show composition rather than distribution. For understanding the shape and frequency distribution of transaction values, a histogram is the most appropriate Tableau visualization.<\/span><\/p>\n<p><b>Question 68.<\/b><\/p>\n<p><b>An analyst has monthly tables with identical fields and wants to combine them into one data set containing all months. Which Tableau operation should be used?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Relationship<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Blend<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Union<\/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 union appends rows from multiple tables with similar structures into a single combined dataset. If each monthly table contains the same columns, such as Order Date, Customer, Product, and Sales, unioning the tables produces one longer table containing records from every month. A join combines columns horizontally based on matching fields, while relationships maintain separate logical tables and define how they interact. Data blending combines aggregated data from multiple sources. Since the requirement is to stack monthly records vertically, a union is the correct operation.<\/span><\/p>\n<p><b>Question 69.<\/b><\/p>\n<p><b>Which join type returns only records whose join keys match in both tables?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Inner join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Left join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Right join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Full outer join<\/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;\">An inner join returns only records where the specified join condition finds matching values in both tables. Rows from either table that do not have a matching key are excluded. This is useful when the analysis should include only entities represented in both datasets, but it can unintentionally remove valid records if the matching keys are incomplete. A left join preserves all rows from the left table, a right join preserves all rows from the right table, and a full outer join preserves unmatched rows from both. Understanding the consequences of each join type is important because joins can directly affect row counts and analytical results.<\/span><\/p>\n<p><b>Question 70.<\/b><\/p>\n<p><b>What is a major risk of physically joining two tables when both contain multiple rows for the same join key?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Tableau automatically deletes all measures<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Row duplication can cause measures to be overstated<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Filters stop working<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> All fields become continuous<\/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;\">When both tables contain multiple rows for the same key, a physical join can create a many-to-many result that multiplies rows. Measures may then be repeated and produce inflated sums or other incorrect aggregates. For example, joining several order rows to several support records for the same customer can create multiple combinations of those rows. Analysts should understand the grain of each table before joining and may prefer relationships when tables need to preserve different levels of detail. Filters and field types do not automatically fail because of a many-to-many join, but duplicated rows can seriously distort analytical results.<\/span><\/p>\n<p><b>Question 71.<\/b><\/p>\n<p><b>Which Tableau data-modeling method allows logical tables to remain separate and be combined according to the fields used in the visualization?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Physical join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Union<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Relationship<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Bin<\/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;\">Relationships connect logical tables while allowing each table to retain its own level of detail. Tableau determines how the tables should be queried and combined based on the fields required by the current visualization. This can help prevent duplication issues that might occur with physical joins between tables of different granularities. A physical join merges tables into a single row-level structure before analysis, while a union stacks rows. Bins group numeric values into ranges and are unrelated to data modeling. Relationships are therefore useful when multiple related tables should remain logically distinct while still participating in the same analysis.<\/span><\/p>\n<p><b>Question 72.<\/b><\/p>\n<p><b>An analyst wants to create a field that returns <\/b><b>Profitable<\/b><b> when Profit is greater than zero and <\/b><b>Unprofitable<\/b><b> otherwise. Which calculated field is appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">SUM([Profit])<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">COUNT([Profit])<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">[Profit] \/ [Sales]<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">IF [Profit] &gt; 0 THEN &#8220;Profitable&#8221; ELSE &#8220;Unprofitable&#8221; END<\/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 IF statement evaluates a logical condition and returns different values depending on whether the condition is true or false. In this case, the calculation checks whether Profit is greater than zero and assigns a corresponding category. Because the expression uses row-level Profit, Tableau evaluates the classification at the row level unless the expression is changed to use aggregated fields. SUM and COUNT alone would only produce numeric aggregations, while dividing Profit by Sales calculates a ratio. Conditional calculations are frequently used in Tableau to create classifications, flags, and business-rule categories from existing data.<\/span><\/p>\n<p><b>Question 73.<\/b><\/p>\n<p><b>Which Tableau function is most suitable when the analyst needs to evaluate a field against several exact values and return a different result for each?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> CASE<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> SUM<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> COUNTD<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> WINDOW_SUM<\/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 CASE expression compares an expression with multiple possible values and returns a corresponding result for the first matching case. For example, an analyst could assign different labels depending on whether Region equals East, West, Central, or South. CASE is often easier to read than a long series of nested IF statements when the conditions are straightforward equality checks. More complex Boolean conditions may still require IF or ELSEIF logic. SUM performs aggregation, COUNTD calculates distinct values, and WINDOW_SUM is a table calculation. CASE is therefore appropriate for mapping several exact input values to different outputs.<\/span><\/p>\n<p><b>Question 74.<\/b><\/p>\n<p><b>Which Tableau function should an analyst use to test whether a field contains a null value?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> COUNTD()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> ISNULL()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> ATTR()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> INDEX()<\/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;\">ISNULL()<\/span><span style=\"font-weight: 400;\"> evaluates whether a specified expression contains a null value and returns a Boolean result. It is useful in calculated fields when analysts need to identify missing values and apply alternative logic. For example, <\/span><span style=\"font-weight: 400;\">IF ISNULL([Region]) THEN &#8220;Unknown&#8221; ELSE [Region] END<\/span><span style=\"font-weight: 400;\"> can replace missing regions for presentation. <\/span><span style=\"font-weight: 400;\">COUNTD()<\/span><span style=\"font-weight: 400;\"> counts distinct values, <\/span><span style=\"font-weight: 400;\">ATTR()<\/span><span style=\"font-weight: 400;\"> checks whether an aggregated set has one consistent value, and <\/span><span style=\"font-weight: 400;\">INDEX()<\/span><span style=\"font-weight: 400;\"> is a table calculation that returns the position of a mark. Null handling is important because null values can affect calculations, filtering, and visual interpretation.<\/span><\/p>\n<p><b>Question 75.<\/b><\/p>\n<p><b>Which Tableau function can replace a null numeric value with zero in a calculated field?<\/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;\"> COUNT()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> ZN()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> RANK()<\/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;\">ZN()<\/span><span style=\"font-weight: 400;\"> returns zero when the supplied numeric expression is null; otherwise, it returns the original numeric value. This makes it convenient for calculations where missing numeric values should be treated as zero. For example, <\/span><span style=\"font-weight: 400;\">ZN([Profit])<\/span><span style=\"font-weight: 400;\"> can prevent a null Profit value from propagating through some calculations. However, analysts should use this function carefully because null and zero can have different business meanings. INDEX and RANK are table calculations, while COUNT counts records or non-null values. When the intended behavior is specifically to convert a null numeric result to zero, <\/span><span style=\"font-weight: 400;\">ZN()<\/span><span style=\"font-weight: 400;\"> is the most direct Tableau function.<\/span><\/p>\n<p><b>Question 76.<\/b><\/p>\n<p><b>Which Tableau table calculation returns the position of a mark within its current partition?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> RANK()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> SIZE()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> WINDOW_SUM()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> INDEX()<\/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;\">INDEX()<\/span><span style=\"font-weight: 400;\"> returns the sequential position of a mark within the current table-calculation partition, beginning with 1. It can be useful for custom filtering, numbering rows, or controlling advanced table-calculation behavior. The result depends on the addressing and partitioning configuration, so changing the Compute Using setting can change the index values. <\/span><span style=\"font-weight: 400;\">RANK()<\/span><span style=\"font-weight: 400;\"> assigns positions according to a measure\u2019s values rather than simply the mark\u2019s sequential position. <\/span><span style=\"font-weight: 400;\">SIZE()<\/span><span style=\"font-weight: 400;\"> returns the number of rows in the partition, and <\/span><span style=\"font-weight: 400;\">WINDOW_SUM()<\/span><span style=\"font-weight: 400;\"> aggregates values across a specified window. INDEX is therefore the function specifically designed to return mark position within a partition.<\/span><\/p>\n<p><b>Question 77.<\/b><\/p>\n<p><b>Which Tableau table calculation returns the total number of marks 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;\"> INDEX()<\/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;\"> FIRST()<\/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;\">SIZE()<\/span><span style=\"font-weight: 400;\"> returns the number of rows or marks in the current table-calculation partition. This can be useful when calculations depend on how many marks exist in a partition or when analysts need logic based on group size. Like other table calculations, its result depends on how the view is partitioned. <\/span><span style=\"font-weight: 400;\">INDEX()<\/span><span style=\"font-weight: 400;\"> returns the current mark\u2019s sequential position, while <\/span><span style=\"font-weight: 400;\">RANK()<\/span><span style=\"font-weight: 400;\"> determines rank according to a measure. <\/span><span style=\"font-weight: 400;\">FIRST()<\/span><span style=\"font-weight: 400;\"> returns an offset from the current row to the first row in the partition. Understanding these functions is important for advanced Tableau calculations that rely on the structure of the displayed marks rather than directly on source rows.<\/span><\/p>\n<p><b>Question 78.<\/b><\/p>\n<p><b>An analyst wants to calculate a running cumulative sum of Sales over Month. Which table calculation is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Percent of Total<\/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;\"> Difference<\/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 value of a measure as Tableau moves across the specified addressing dimension. With Month in chronological order and SUM(Sales) in the view, the running total shows cumulative sales through each month. It is useful for year-to-date totals, progress toward goals, and cumulative performance analysis. The Compute Using setting must be configured correctly so that the accumulation proceeds across Month rather than another dimension. Percent of Total shows contribution to a total, Rank assigns order, and Difference compares one mark with another. For cumulative values, Running Total is the correct quick table calculation.<\/span><\/p>\n<p><b>Question 79.<\/b><\/p>\n<p><b>Which Tableau table calculation should be used to display each category&#8217;s contribution to the total Sales in the current partition?<\/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;\"> Difference<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Percent of Total<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Rank<\/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 of Total divides each mark\u2019s value by the total for the current table-calculation partition and presents the result as a proportion or percentage. This makes it ideal for questions such as what percentage of total sales comes from each category or region. The exact result depends on the Compute Using configuration because that determines which marks belong to the denominator. Running Total accumulates values, Difference compares marks, and Rank orders them. Percent of Total is especially useful in bar charts and text tables because it communicates relative contribution without requiring analysts to manually create the division calculation.<\/span><\/p>\n<p><b>Question 80.<\/b><\/p>\n<p><b>A dashboard contains a summary chart and a detailed table. The analyst wants selecting a category in the chart to restrict the table to that category. Which Tableau feature should be configured?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Highlight 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;\"> 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: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A filter action allows a user interaction in one worksheet to filter the data displayed in another worksheet. In this scenario, selecting a category in the summary chart can pass that category to the detailed table, causing the table to show only records associated with the selection. Filter actions can be configured to run on selection, hover, or menu and can specify source and target worksheets. A highlight action would emphasize matching rows while leaving unrelated data visible. Parameter actions update parameter values, while URL actions navigate to external resources. For restricting a target view based on a selected mark, a filter action is the appropriate dashboard interaction.<\/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 61. An analyst wants to display total sales for each state on a filled map. Which Tableau field characteristic is required for State to be recognized appropriately? It must be converted to a measure 2. It should have an appropriate geographic role 3. [&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\/23326"}],"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=23326"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23326\/revisions"}],"predecessor-version":[{"id":23327,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23326\/revisions\/23327"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23326"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23326"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}