Explanation

The question asks for the percent difference in sales compared to the same quarter of the previous year (YoY % change). In Tableau, when the view is broken down by quarter in chronological order, the value from the same quarter last year is accessed using LOOKUP(..., -4). The complete percent difference formula must subtract the previous value and then divide the result by that same previous value.

Correct Option:

✅ B. (SUM ([Sales]) - LOOKUP (SUM ([Sales]), -4) ) / (LOOKUP (SUM ([Sales]), -4) )
This is the official and most widely recommended Tableau formula for year-over-year percent change by quarter. It correctly computes (Current Sales – Sales 4 quarters ago) ÷ Sales 4 quarters ago, returning the true percentage growth or decline (e.g., 0.12 = +12%).

Incorrect Options:

❌ A. (SUM ([Sales]) - LOOKUP (SUM ([Sales]), -4))
This formula only calculates the absolute difference in sales (e.g., +$50,000). It completely misses the division step needed to convert the raw change into a percentage, so the result is expressed in currency units instead of a percent, making it incorrect for the requested “percent difference”.

❌ C. (SUM([Sales]) / (LOOKUP (SUM ([Sales]), -4)))
This produces a ratio rather than a percent difference (e.g., 1.15 means sales are now 115% of last year’s same quarter). While related, it is not the same as percent change; it requires subtracting 1 and formatting as percent to match the question, which this formula does not do.

❌ D. (ZN (SUM ([Sales]) ) - LOOKUP (ZN (SUM ([Sales]) ), -4) )
The ZN() function replaces nulls with zero to avoid errors, which can be helpful in some cases. However, this calculation still only returns the absolute difference (raw dollar change), not a percentage. It adds unnecessary complexity and fails to include the required division by the previous period’s value.

Reference:
Support Portal Experience Enhancements for Tableau Customers and Partners
Tableau Training – Table Calculations: https://www.tableau.com/learn/training

Explanation

To create a filled map showing total Sales by State using the Superstore data source in the Map worksheet, follow these steps:

➡️ Open Book1 → Go to the Map worksheet.
➡️ Ensure the data source is set to Superstore.
➡️ In the Data pane, drag State to Rows. Tableau automatically recognizes geographic data.
➡️ Drag Sales to Color on the Marks card.
➡️ Change the Marks type to Map (Filled Map).
➡️ Customize color intensity to better visualize sales distribution.
➡️ This creates a filled geographic distribution of sales across U.S. states.

📝 Summary
A filled map is created by using geographic fields like State, combined with a measure such as Sales placed on the color shelf. Tableau automatically renders U.S. states and fills them based on the total sales value, making it easy to compare states visually.

🔗 Reference
Official Tableau Documentation: Maps and Geographic Data Analysis in Tableau

Explanation

When an alert is suspended in Tableau, only the alert owner can resume it. Suspended alerts are managed directly from the Tableau web environment where content ownership is accessible. Tableau stores all user-owned items such as alerts, subscriptions, and data sources in the My Content section. From there, the owner can view, edit, or resume a suspended alert. This location keeps alert control centralized and tied to ownership permissions.

🟦 Correct Answer: C. 🟦 The My Content area of Tableau web pages
Suspended alerts can be resumed only from the My Content section on Tableau Server or Tableau Cloud. This page displays all assets owned by the user, including data-driven alerts. Owners can open the alert details and resume suspended alerts directly from this interface, making it the official management location for owned alert settings.

🟥 Why the other options are incorrect

A. 🟥 The Data Source page of Tableau Desktop
Tableau Desktop is primarily used for creating and editing workbooks and data sources. It does not provide alert management functionality because alerts are server-side features tied to Tableau Server or Cloud. You cannot resume suspended alerts from Desktop, as it has no interface for alert control.

B. 🟥 The Notification area of Tableau Prep
Tableau Prep focuses on data preparation workflows, such as cleaning and transforming data. Its notification area only relates to workflow completion or errors. It does not include options to manage or resume data-driven alerts, which are only available on Tableau web pages.

D. 🟥 The Shared with Me page
This page displays content that others have shared with you, but you do not own it. Since only the alert owner has permissions to modify or resume alerts, content on this page cannot be used to resume a suspended alert. Attempting to manage alerts here would not provide the required access or control.

🔗 Official Reference
📄 Tableau Help — Data-Driven Alerts Management

Explanation:

When working with dimensions in Tableau, sometimes you need to adjust how values appear in your visualizations without altering the underlying data or creating new fields. This ensures that dashboards remain consistent, user-friendly, and readable while maintaining data integrity. Choosing the right method depends on whether you are changing the field name, individual values, or grouping data.

Correct Option (✅ B. Create aliases):
Aliases allow you to rename individual members of a dimension without creating a new field. For example, “NY” can be displayed as “New York,” or “Q1” as “Quarter 1.” The underlying data remains intact, so any calculations, filters, or joins still work normally. This is ideal for improving dashboard readability, standardizing terminology, or aligning value labels across multiple sheets. (help.tableau.com)

Incorrect Options:

🔴 A. Rename the fields:
This only changes the name of the field in the Data Pane, not the values themselves. So, if you rename “State” to “Region,” the individual members like “NY” or “CA” remain the same. It doesn’t help if you want to change how the values appear in a chart.

🔴 C. Create groups:
Groups are used to combine multiple dimension members into a new category. While this can simplify visualizations, it actually creates a new grouped field, which violates the requirement of not creating a new field. This is more suitable for aggregation rather than simple value renaming.

🔴 D. Transforms the fields:
Transformations (e.g., calculated fields, pivoting, or converting data types) modify data structure or create new fields. They do not simply rename existing dimension values, making them unsuitable for this specific requirement.

Summary:
To update dimension values without creating new fields, always use aliases. Renaming changes only the field name, grouping generates new fields, and transformations modify the dataset. Aliases keep the underlying data intact while improving readability and consistency in Tableau dashboards.

Reference:
Tableau Help: Create Aliases to Rename Members in the View

Explanation

To calculate each state’s percentage of its region’s total sales, the analyst must first create a calculation that returns the same regional total on every state row. This allows a simple division: State Sales ÷ Region Total. Only a FIXED LOD expression that is scoped exactly to Region (and ignores State) can deliver that consistent regional value across the entire dataset.

Correct Option

✅ A. {FIXED [Region]: SUM([Sales])}
This is the perfect solution. The FIXED keyword tells Tableau to compute the sum of Sales at the Region level only, ignoring any finer dimensions in the view (like State). The result is a single total for the entire region that appears on every state row belonging to that region, making the subsequent percent calculation accurate and straightforward.

Incorrect Options

❌ B. [FIXED [Region]: TOTAL([Sales])]
This syntax is completely invalid and will throw an error immediately. TOTAL() is a table calculation that requires compute-using settings and cannot be placed inside a FIXED LOD expression. Even if someone tries to force it, Tableau will reject the calculation before it ever ever runs.

❌ C. {FIXED [State]: SUM([Sales])}
Although this is valid syntax, it defeats the purpose. By fixing on State, the calculation simply returns the regular SUM([Sales]) for each state—exactly what you already get without any LOD. It provides no regional total at all, so dividing state sales by this value would always yield 100% and make the percentage-of-region analysis impossible.

❌ D. {FIXED [State], [Region]: SUM([Sales])}
This LOD is scoped to the combination of State and Region, meaning it still calculates sales at the individual state level (just with Region as extra context). The result is identical to normal SUM([Sales]) when both dimensions are present, so it never produces a single region-wide total. Using this in the denominator would again return 100% for every state.

Reference
FIXED Level of Detail Expressions
How Level of Detail Expressions Work in Tableau