Salesforce Certified Tableau Desktop Foundations Practice Questions

A live connection is the appropriate choice in this scenario. It sends queries directly to the source database whenever a user interacts with the visualization. This ensures that the data is always up-to-date. While performance depends on the database, the scenario specifies a 'high-performance database', making a live connection the ideal method for real-time analysis on large datasets where extracts are impractical.

The quickest and most intuitive way to sort a chart by a measure is to use the one-click sort icons. Hovering over the axis for the measure (in this case, the Profit axis) will reveal a small sort icon. Clicking this icon will instantly sort the corresponding dimension (State) in descending order based on the measure's value. Clicking it again will sort in ascending order.

This is the optimal solution. An extract will provide the best performance for a dashboard with frequent filtering and drill-downs, which is a key requirement. Since the data is only updated nightly, a nightly extract refresh aligns perfectly with the data freshness needs. Using a relationship is superior to a join here because it maintains the separate levels of detail of the tables, preventing data duplication and providing flexibility for future analysis. The revenue calculation is correctly performed as a calculated field within Tableau.

This statement is true. It accurately describes the fundamental difference between dimensions and measures in Tableau. Dimensions (like 'Category' or 'Region') are used to set the level of detail or granularity in the view and are typically categorical. Measures (like 'Sales' or 'Quantity') are numeric, quantitative values that you can perform mathematical operations on (e.g., SUM, AVG).

When you create bins from a continuous measure, Tableau generates a new field in the Data pane. This new field is a dimension. Even though it's derived from a measure, its purpose is to group the data into discrete, categorical buckets (the bins), which is the role of a dimension.

Exporting as a PDF creates a high-quality, vector-based document that preserves the dashboard's layout and is easily shareable and printable. It's a standard format for reports and presentations.

Exporting as an Image (like PNG or JPEG) creates a static, pixel-based file of the dashboard. This is ideal for embedding directly into presentation slides or sharing quickly in an email or report.

Relationships (the logical layer) are the modern and preferred method for this scenario. They maintain the separate nature of the tables, querying them at their native level of detail and performing context-aware joins only when needed for a specific visualization. This avoids the massive data duplication and performance degradation that would occur from physically joining Customers (10M rows) down to the Order_Details level (500M rows). Physical joins would make it difficult and inefficient to perform calculations at different granularities (like counting unique customers).

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.