Tableau Desktop Foundations Advanced Practice Exam: Hard Questions 2025

A workbook connects to a large cloud data warehouse. Users report that filtering the view by a high-cardinality Customer ID is extremely slow and sometimes times out. The analysis must remain at transaction grain, but the dashboard must feel responsive for interactive filtering. Which approach is most appropriate in Tableau Desktop to improve performance while preserving detail?

You blend Sales (primary) to Targets (secondary) on Region and Month. Sales has daily rows; Targets has one row per Region-Month. The view shows SUM(Sales) and SUM(Target). When you add Product Category from Sales, the Target value multiplies unexpectedly. What is the best fix to prevent Target duplication while keeping Sales at daily granularity?

A data source has two tables: Orders (Order ID, Customer ID, Order Date) and Returns (Order ID, Return Date, Return Amount). Some orders have multiple return records. The analyst needs total sales and total return amount by Customer without inflating sales due to return-row duplication. Which modeling approach in Tableau Desktop best avoids duplication while keeping flexibility for additional Return-level fields later?

A dashboard contains a map and a trend chart. Selecting a state on the map should filter the trend chart, but should NOT filter the map itself (users want to keep geographic context). Additionally, a separate KPI sheet should update with the same selection. Which configuration best meets this requirement?

A dashboard shows Sales by Sub-Category. Users want to click a bar and see a detail table of the underlying orders, but the detail table should appear in a new window/tab and must include multiple fields not present in the original bar chart. What is the best solution?

A dashboard uses several worksheets connected to the same extract. Performance degrades after adding a date filter and multiple quick filters. The requirement is to reduce redundant queries and improve responsiveness without changing the underlying data source. Which technique is most effective?

You need to show Month-over-Month (MoM) % change in Sales, but the view can be sliced by Region and Product. When users add/remove dimensions, the MoM calculation must still correctly restart per pane (i.e., per Region-Product combination) and compute across months. Which approach is most robust?

A view shows top 10 Customers by Sales. The business now wants 'Top 10 Customers by Sales within each Region', displayed in the same sheet, with an 'Other' group for the rest. The result must remain stable when additional filters (like Year) are added, and the 'Other' should always represent non-top customers within each Region. What is the best approach?

A workbook will be published so executives can view it, but only some users are allowed to see Profit and Discount measures due to sensitivity. The same dashboard layout should be used for everyone; restricted users should see the dashboard but with those measures hidden/blank. What is the most appropriate solution pattern?

After publishing a workbook, viewers report that a dashboard action no longer works as expected: selecting a mark should filter a target sheet, but nothing happens. In Desktop it works. The workbook uses a published data source, and the target sheet is hidden (not shown as a tab). Which is the most likely cause and fix?