{"id":23350,"date":"2026-09-28T05:10:12","date_gmt":"2026-09-28T05:10:12","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23350"},"modified":"2026-09-28T05:10:12","modified_gmt":"2026-09-28T05:10:12","slug":"tableau-tda-c01-practice-test-questions-and-exam-dumps-part16-q301-320","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/tableau-tda-c01-practice-test-questions-and-exam-dumps-part16-q301-320\/","title":{"rendered":"Tableau TDA-C01 Practice Test Questions and Exam Dumps Part16 Q301-320"},"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 301.<\/b><\/p>\n<p><b>An analyst wants to show only the top 5 Product Sub-Categories by SUM(Sales) within a selected Region. Which approach is most appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Add Region to context, then apply a Top 5 filter to Sub-Category based on SUM(Sales)<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Apply a Top 5 filter first and then hide Region<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Use a highlight action instead of filtering<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Convert Sales to a dimension<\/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 evaluates filters according to its order of operations. If the analyst wants the Top 5 Sub-Categories within a selected Region, Region should be placed in context so the regional subset is established first. The Top 5 Sub-Category filter can then be evaluated against that smaller set of data. Without context, Tableau may determine the top members across a broader dataset and only afterward apply the Region filter, producing unexpected results. Highlighting does not restrict the dataset, and converting Sales into a dimension would change its analytical behavior. Context filters are especially useful when a later Top N or conditional filter must be calculated within an earlier filtered subset.<\/span><\/p>\n<p><b>Question 302.<\/b><\/p>\n<p><b>Which Tableau filter is evaluated after dimension filters and is based on aggregated measure values such as SUM(Sales)?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Extract filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Measure filter<\/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;\"> Data source 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;\">A measure filter operates on aggregated quantitative values after Tableau has grouped the data according to the dimensions in the view. For example, if Customer Name is present and Sales is filtered as SUM(Sales) greater than a threshold, Tableau evaluates the aggregate for each customer and then filters the resulting marks. Extract and data source filters operate earlier, while context filters establish a subset before standard dimension filters. Understanding this order matters because changing the filter type can change the data included in calculations and can produce different results even when the visible filter condition appears similar.<\/span><\/p>\n<p><b>Question 303.<\/b><\/p>\n<p><b>Which Tableau calculation is most appropriate for determining the total Sales for each Customer regardless of the dimensions displayed in the current worksheet?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">RUNNING_SUM(SUM([Sales]))<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">{ INCLUDE [Customer ID] : SUM([Sales]) }<\/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 calculates using the dimensions explicitly defined in the expression. <\/span><span style=\"font-weight: 400;\">{ FIXED [Customer ID] : SUM([Sales]) }<\/span><span style=\"font-weight: 400;\"> therefore creates a customer-level total that does not automatically change when dimensions such as Category, Region, or Sub-Category are added to the visualization. The result can still be affected by filters that are evaluated before FIXED, particularly context filters. INCLUDE calculations are relative to the current view&#8217;s detail, while RUNNING_SUM and WINDOW_SUM are table calculations operating on already aggregated marks. When the grain must remain explicitly fixed at Customer ID, a FIXED LOD expression is the appropriate solution.<\/span><\/p>\n<p><b>Question 304.<\/b><\/p>\n<p><b>An analyst needs to calculate Sales at the Customer level even though the worksheet displays only Region. Which LOD expression type is designed for this scenario?<\/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;\">INCLUDE adds one or more dimensions to the level of detail used for a calculation, even when those dimensions are not visible in the view. For example, an INCLUDE expression can calculate Sales at Customer ID while the worksheet itself is displayed only at Region. Tableau then aggregates those finer customer-level results back to the Region level. This is useful for metrics such as average customer sales or customer-level profitability. EXCLUDE removes dimensions from the current view&#8217;s detail, while table calculations operate later on aggregated marks. INCLUDE directly addresses the need to introduce a hidden finer-grained dimension into a calculation.<\/span><\/p>\n<p><b>Question 305.<\/b><\/p>\n<p><b>A view contains Region and State, but the analyst wants a calculation that ignores State and returns Region-level Sales. Which Tableau approach is most suitable?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Use an EXCLUDE LOD expression for State<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Use a histogram<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Convert State to a measure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Apply a URL 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;\">An EXCLUDE LOD expression removes one or more dimensions from the level of detail used for the calculation while leaving those dimensions visible in the view. If Region and State are shown, excluding State allows the calculation to return a Region-level Sales total for each state mark. This is useful for comparing state performance with the total for its parent region. A histogram analyzes numeric distributions, converting State to a measure would not produce the desired aggregation, and URL actions provide external navigation. EXCLUDE is intended specifically for broader calculations that should ignore selected dimensions already present in the visualization.<\/span><\/p>\n<p><b>Question 306.<\/b><\/p>\n<p><b>Which Tableau table calculation is most appropriate for showing cumulative Profit from January through each subsequent month?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> 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;\"> 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: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Running Total accumulates the selected measure across the chosen addressing dimension. If Month is arranged chronologically and SUM(Profit) is used, the calculation adds January Profit to February, then adds March, and continues through the sequence. This makes it ideal for year-to-date profitability and cumulative performance tracking. The analyst must verify the Compute Using setting so the calculation progresses across Month and resets where intended, such as at the start of a new year. Difference measures changes between marks, Percent of Total shows contribution, and Rank orders marks. For cumulative values over time, Running Total is the appropriate calculation.<\/span><\/p>\n<p><b>Question 307.<\/b><\/p>\n<p><b>Which table calculation is most appropriate for displaying the percentage change from one month\u2019s Sales to the next?<\/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;\"> Percent of Total<\/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;\"> 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 Difference compares the current mark with another mark, typically the preceding one, and expresses the change as a percentage. Applied to monthly Sales, it can show month-over-month growth or decline. Correct addressing is essential so Tableau compares the current month with the immediately preceding month. Running Total accumulates values, Percent of Total measures each value\u2019s share of a total, and Rank orders values. Percent Difference is particularly useful when the analyst wants relative change rather than an absolute difference because it normalizes the change according to the previous period\u2019s magnitude.<\/span><\/p>\n<p><b>Question 308.<\/b><\/p>\n<p><b>Which Tableau table-calculation function can return the Sales value from the next mark in the current partition?<\/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;\"> SIZE()<\/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;\">LOOKUP(SUM([Sales]),1)<\/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;\">LOOKUP()<\/span><span style=\"font-weight: 400;\"> retrieves the value of an expression from a different mark at a relative offset within the current table-calculation partition. An offset of <\/span><span style=\"font-weight: 400;\">1<\/span><span style=\"font-weight: 400;\"> refers to the next mark, while <\/span><span style=\"font-weight: 400;\">-1<\/span><span style=\"font-weight: 400;\"> refers to the previous mark. This is useful for forward-looking comparisons, custom difference calculations, and checking subsequent period values. INDEX returns positional numbering, SIZE returns the number of marks in the partition, and RANK assigns a position based on values. LOOKUP depends on the current sort order, partitioning, and addressing, so those settings must be correct for the retrieved value to represent the intended next period.<\/span><\/p>\n<p><b>Question 309.<\/b><\/p>\n<p><b>Which Tableau function returns the number of marks in the current table-calculation 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;\"> FIRST()<\/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;\">SIZE()<\/span><span style=\"font-weight: 400;\"> returns the number of marks or rows in the current table-calculation partition. It is useful in calculations that depend on partition length, such as custom row selection, conditional formatting, or validating whether enough observations exist for a rolling calculation. Like all table calculations, its value depends on the current partitioning of the worksheet. INDEX returns a mark&#8217;s sequential position, FIRST returns an offset to the first row, and LOOKUP retrieves values from other marks. SIZE specifically answers how many marks belong to the active calculation partition.<\/span><\/p>\n<p><b>Question 310.<\/b><\/p>\n<p><b>Which Tableau function returns a mark\u2019s sequential position in its current table-calculation 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;\"> ATTR()<\/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;\">INDEX()<\/span><span style=\"font-weight: 400;\"> assigns a sequential position to each mark in a table-calculation partition, starting with 1. It differs from RANK because INDEX is based on the ordering of marks rather than directly ranking a measure\u2019s value. This makes it useful for row numbering, advanced filtering, pagination-like logic, or custom table calculations. The result can change if the sort order changes or if the addressing configuration is modified. SIZE returns the partition size, while ATTR checks whether one common value represents the underlying data. For simple positional numbering within a partition, INDEX is the appropriate function.<\/span><\/p>\n<p><b>Question 311.<\/b><\/p>\n<p><b>Which Tableau calculation is best for averaging Sales over the current month and the two previous months?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> FIXED LOD expression<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Percent of Total<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Moving Average table calculation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Context filter<\/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 Moving Average table calculation is designed to average values across a rolling window of marks. For a three-month moving average, the analyst can configure the calculation to average the current month with the two preceding months. This smooths short-term fluctuations and helps reveal underlying trends. Because it is a table calculation, the result depends on the order of months and the Compute Using setting. A FIXED LOD expression defines aggregation granularity but does not inherently create a rolling window. Percent of Total and context filters address different analytical requirements. Moving Average is therefore the correct feature.<\/span><\/p>\n<p><b>Question 312.<\/b><\/p>\n<p><b>Which Tableau function is best suited for replacing null numeric values with zero?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> ISNULL()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> IFNULL() only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> COUNT()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> ZN()<\/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;\">ZN()<\/span><span style=\"font-weight: 400;\"> is designed specifically for numeric null handling. When its argument is null, it returns zero; otherwise, it returns the original numeric value. This can simplify calculations where a missing numeric value should legitimately be treated as zero. IFNULL can also provide a replacement value but is more general-purpose, while ISNULL only tests whether a value is missing. COUNT performs aggregation and does not replace nulls. Analysts should make sure that converting null to zero is semantically correct because missing information and an actual measured value of zero may represent different business conditions.<\/span><\/p>\n<p><b>Question 313.<\/b><\/p>\n<p><b>Which Tableau function should be used to check whether a string starts with the prefix <\/b><b>INV-<\/b><b>?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> STARTSWITH()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> CONTAINS()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> RIGHT()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> FIND()<\/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;\">STARTSWITH()<\/span><span style=\"font-weight: 400;\"> returns TRUE when a string begins with the specified substring. For example, <\/span><span style=\"font-weight: 400;\">STARTSWITH([Document ID],&#8221;INV-&#8220;)<\/span><span style=\"font-weight: 400;\"> can identify invoice-related identifiers. CONTAINS tests whether the substring appears anywhere, while RIGHT extracts characters from the end of the string. FIND returns the position of a substring and could be used indirectly, but STARTSWITH expresses the business rule more clearly. Purpose-specific functions improve readability and make calculated fields easier to maintain, especially when logic is shared across multiple worksheets or workbooks.<\/span><\/p>\n<p><b>Question 314.<\/b><\/p>\n<p><b>Which Tableau string function should an analyst use to convert a text field to uppercase?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> LOWER()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> UPPER()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> TRIM()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> STR()<\/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;\">UPPER()<\/span><span style=\"font-weight: 400;\"> converts alphabetic characters in a string to uppercase. This is useful for normalizing source values that use inconsistent capitalization. For example, <\/span><span style=\"font-weight: 400;\">east<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">East<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">EAST<\/span><span style=\"font-weight: 400;\"> can all be converted to <\/span><span style=\"font-weight: 400;\">EAST<\/span><span style=\"font-weight: 400;\"> before comparison, grouping, or filtering. LOWER converts text to lowercase, TRIM removes surrounding spaces, and STR converts compatible non-string values into text. Standardizing capitalization can prevent logically identical values from appearing as separate categories and can improve the reliability of calculated-field comparisons and custom classification logic.<\/span><\/p>\n<p><b>Question 315.<\/b><\/p>\n<p><b>Which Tableau function can replace a substring such as <\/b><b>Ltd.<\/b><b> with <\/b><b>Limited<\/b><b> inside a text field?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> TRIM()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> FIND()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> REPLACE()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> LEN()<\/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;\">REPLACE()<\/span><span style=\"font-weight: 400;\"> substitutes occurrences of one substring with another. For example, <\/span><span style=\"font-weight: 400;\">REPLACE([Company],&#8221;Ltd.&#8221;,&#8221;Limited&#8221;)<\/span><span style=\"font-weight: 400;\"> can standardize company naming for analysis or display. This transformation affects the Tableau calculation result rather than permanently modifying the underlying source data. TRIM removes whitespace, FIND returns the position of a substring, and LEN returns the number of characters in a string. REPLACE is therefore useful for predictable text normalization, abbreviation cleanup, or removing unwanted characters where a known search-and-substitute rule can be applied consistently.<\/span><\/p>\n<p><b>Question 316.<\/b><\/p>\n<p><b>Which Tableau date function should be used to calculate the number of months between Order Date and Ship Date?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> DATEADD()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> DATETRUNC()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> DATEPART()<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> DATEDIFF()<\/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;\">DATEDIFF()<\/span><span style=\"font-weight: 400;\"> returns the difference between two dates using a specified unit. An expression such as <\/span><span style=\"font-weight: 400;\">DATEDIFF(&#8216;month&#8217;,[Order Date],[Ship Date])<\/span><span style=\"font-weight: 400;\"> calculates the number of month boundaries between the two dates. This can be useful for long fulfillment periods, subscription duration, or tenure calculations. DATEADD shifts a date, DATETRUNC rounds a date to a time boundary, and DATEPART extracts one component. The analyst should remember that DATEDIFF counts boundaries between the dates rather than necessarily measuring exact fractional months. For elapsed date units, DATEDIFF is the correct function.<\/span><\/p>\n<p><b>Question 317.<\/b><\/p>\n<p><b>Which Tableau function should be used to return the beginning of the month that contains a date?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">DATETRUNC(&#8216;month&#8217;,[Date])<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> MONTH([Date])<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> DATEADD(&#8216;month&#8217;,1,[Date])<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> DATEDIFF(&#8216;month&#8217;,[Date],TODAY())<\/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;\">DATETRUNC(&#8216;month&#8217;,[Date])<\/span><span style=\"font-weight: 400;\"> returns the first day of the month containing the source date. It retains a date data type and preserves the year context, which makes it useful for grouping, comparing, joining, or plotting monthly periods. MONTH returns only the month component, while DATEADD shifts dates and DATEDIFF measures intervals. DATETRUNC is especially helpful when the analyst wants all dates in a given month to map to a consistent month-start value rather than simply returning a month name or month number.<\/span><\/p>\n<p><b>Question 318.<\/b><\/p>\n<p><b>Which Tableau operation should be used to append rows from similarly structured tables such as <\/b><b>Sales_2024<\/b><b>, <\/b><b>Sales_2025<\/b><b>, and <\/b><b>Sales_2026<\/b><b>?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> 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;\"> Blend<\/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 union stacks rows vertically from tables that have compatible column structures. If the yearly Sales tables contain the same fields, a union can combine them into one dataset spanning multiple years. A join combines columns based on matching keys, while relationships connect logical tables without immediately flattening them. Data blending combines aggregated results from different data sources. When data is partitioned by year, month, or another period and each table follows the same schema, a union is the natural operation for creating one continuous analytical dataset.<\/span><\/p>\n<p><b>Question 319.<\/b><\/p>\n<p><b>Which join type preserves all records from both tables, including records that do not match?<\/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;\"> Full outer join<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Right join<\/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 full outer join preserves all matching records and also retains unmatched records from both the left and right tables. When no corresponding record exists on one side, the fields from that side are null. This is useful when analysts need a complete view of both populations, including records missing a counterpart. Inner joins keep only matched records, while left and right joins preserve the complete population from only one side. Full outer joins can increase result size and expose data-quality issues, so analysts should review join keys and row counts carefully after combining the tables.<\/span><\/p>\n<p><b>Question 320.<\/b><\/p>\n<p><b>A dashboard user should be able to click a Product Category and have multiple other worksheets show only data related 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 passes values from selected marks in a source worksheet to one or more target worksheets and restricts those target views to matching data. Selecting a Product Category can therefore cause tables, charts, and maps elsewhere on the dashboard to show only records associated with that category. A highlight action keeps unrelated marks visible, parameter actions update parameters, and URL actions open external resources. Filter actions are one of Tableau\u2019s most common dashboard interaction tools because they allow visualizations themselves to act as intuitive filtering controls for related views.<\/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 301. An analyst wants to show only the top 5 Product Sub-Categories by SUM(Sales) within a selected Region. Which approach is most appropriate? Add Region to context, then apply a Top 5 filter to Sub-Category based on SUM(Sales) 2. Apply a Top 5 [&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\/23350"}],"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=23350"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23350\/revisions"}],"predecessor-version":[{"id":23351,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23350\/revisions\/23351"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}