You have a sales dataset with fields OrderDate and SalesAmount. You want to calculate the year-over-year sales growth percentage using a Level of Detail (LOD) expression in Tableau.
Which of the following LOD expressions correctly calculates the total sales for the previous year to use in the growth calculation?
Think about how to fix the year to the previous year using date functions inside the LOD.
Option C correctly fixes the calculation to the previous year by using DATEPART with DATEADD to shift the year back by one, then sums sales for that year.
You want to create a dashboard that shows monthly sales trends over the past two years and includes a forecast for the next 6 months.
Which visualization type in Tableau best fits this requirement?
Consider which chart type best shows trends over time and supports forecasting.
Line charts with continuous date axes are ideal for showing trends over time and Tableau's built-in forecast feature works best with them.
Why is a moving average commonly used in trend analysis dashboards?
Think about what moving averages do to noisy data.
Moving averages smooth out short-term fluctuations, making it easier to see the overall trend by reducing noise like seasonal effects.
You need to build a data model in Tableau to analyze sales trends over multiple years with the ability to filter by product categories and regions.
Which data modeling approach is best to support fast and flexible trend analysis?
Think about how dimension tables help with filtering and performance.
A star schema separates facts and dimensions, enabling efficient filtering and aggregation for trend analysis across multiple years.
A Tableau user created a calculated field to compute a 3-month moving average of sales:
WINDOW_AVG(SUM([SalesAmount]), -2, 0)
However, the moving average does not appear correctly on the dashboard.
What is the most likely cause of the problem?
Consider how Tableau computes table calculations and the importance of addressing.
Without properly setting addressing and partitioning, WINDOW_AVG may compute over wrong data points, causing incorrect moving averages.