Salesforce Certified Tableau Desktop Foundations Free Sample Questions

A dual axis chart is the correct choice because it allows two measures with different scales to be displayed on the same chart using two independent axes (a left and a right axis). This is essential for comparing the trend of the closing price and the magnitude of the trading volume simultaneously without one scale distorting the other. A combined axis chart requires the measures to share a single axis, which would not work for measures with vastly different scales. A scatterplot is used for correlation between two measures, not for showing trends over time. A stacked bar chart is used for part-to-whole analysis.

A calculated field is the best solution because it allows for conditional logic (e.g., IF [Conversion Rate] > 0.05 THEN 'High' ...) to create dynamic groupings based on a measure's value. This new calculated dimension can then be used across any worksheet. Standard groups are static and based on selecting dimension members, not on a measure's value. Sets create a binary IN/OUT grouping. A hierarchy is for drilling down, not for conditional grouping.

This statement is true. When Tableau attempts to convert a data type, it follows specific rules. If a string value cannot be parsed into the target numeric format (e.g., 'N/A' cannot become a whole number), Tableau will assign a Null value to it. This is a key data preparation behavior to understand.

A left join with the 'Orders' table on the left is the correct method. This ensures that all records from the 'Orders' table are kept, and matching return information from the 'Returns' table is appended where an Order ID match exists. For orders that were not returned, the fields from the 'Returns' table will be Null. An inner join would only show orders that were returned. A relationship would also work, but the question asks for a specific approach to combine tables to ensure all orders are included, and a left join explicitly achieves this at the physical layer.

A parameter is needed to store the user's selection (e.g., 5%, 10%, 15%). It acts as a dynamic variable that is not tied to the data source.

A calculated field is required to use the value from the parameter in a calculation (e.g., SUM([Sales]) * (1 + [Sales Increase Parameter])). The calculation's result changes dynamically as the user changes the parameter value.

The primary benefit of a .tds file is that it stores the connection information and all the metadata layer customizations (renamed fields, hierarchies, default formats, calculated fields, etc.). By sharing the .tds file, the organization ensures that every analyst starts with the same clean, standardized, and enriched data model, leading to consistent and reliable analysis. A .tds file does not contain the actual data; a .tdsx (packaged data source) does. While it can be part of a security strategy, its primary purpose is metadata management, not security enforcement.

The most direct method is to select the map worksheet on the dashboard, click the 'Use as Filter' icon (funnel shape) from its context menu. This automatically creates a filter action where the map (source sheet) filters the other worksheets (target sheets) on the dashboard when a mark (a state) is selected.

Creating an alias is the correct method for changing the display name of a specific member (a data value) within a dimension. By right-clicking the 'east' member in the Data pane or in a view and selecting 'Edit Alias', the analyst can change its display value to 'East'. Tableau will then aggregate both 'East' and 'east' together under the alias. Renaming the field changes the field name, not its values. Grouping would create a new dimension. A calculated field could also solve this but is more complex than using a simple alias for this specific problem.

To aggregate data for a specific time period across all years, you must use a discrete date part. Selecting the discrete Month (blue pill, shows 'May') will treat 'May' as a categorical label and aggregate all data for May, regardless of the year. Using a continuous Month (green pill, shows 'May 2023') would create a timeline where each month/year combination is a distinct point on a continuous axis, which would not achieve the desired aggregation.

The key difference lies in Tableau's order of operations. A context filter is applied before most other filters (like standard dimension or measure filters). It effectively creates a temporary table or 'context' from the data source. All subsequent filters and calculations then run only on the data that passes through the context filter. This can significantly improve performance on large datasets and is necessary when you want a dimension filter to apply before a FIXED LOD calculation. Dimension filters are applied after context filters and FIXED LODs.