Explanation

Tableau extracts are standalone, optimized copies of data that allow fast analysis even when disconnected from the original database. Since Tableau version 10.5 (released in 2018), the extract engine was completely rewritten, and the new format uses the .hyper extension. This file contains the actual rows and columns in a compressed, columnar structure that Tableau can query extremely quickly. Older .tde extracts are still supported, but any extract created today will always be .hyper.

Correct Option

✅ A. Sales.hyper
The .hyper file is unmistakably a Tableau extract. It holds the full dataset (or a subset defined during creation) in Tableau’s proprietary high-performance format. You can connect directly to a .hyper file as a data source, publish it to Tableau Server/Online, or include it in a packaged workbook (.twbx). It’s the only file in the list that actually contains extracted data.

Incorrect Options

❌ B. Sales.csv
This is a plain-text comma-separated values file — one of the most common raw data formats. While Tableau can connect to it live or extract from it, the .csv itself is just source data, not a Tableau extract. It remains human-readable in any text editor.

❌ C. Export.mdb
An .mdb file is a legacy Microsoft Access database. Tableau can connect to Access files as a data source (live or extract), but the .mdb is the original database, not a Tableau-created extract. It uses Microsoft’s proprietary format, not Tableau’s.

❌ D. Book1.twb
A .twb workbook contains only XML metadata: layouts, calculations, formatting, and connection information. It never stores the actual data rows. If data were bundled inside, the file would be a packaged workbook (.twbx) instead.

Reference
Extract Your Data

Explanation:

This question tests your knowledge of how Tableau handles missing data/sparse data (structural gaps) in a visualization versus true Null values within existing database rows.

The Core Logic:
In a typical line chart or text table displaying an absolute time series (e.g., month-by-month), a month might completely lack a row in the underlying database for that year (e.g., no transactions occurred in February). This is known as a structural gap.

Why standard IFNULL or ZN fails alone:
A standard row-level function like ZN(SUM([Sales])) evaluates to zero only if a record exists in the database table and its Sales field contains a Null value. If the row does not exist at all, the aggregation has no cell to evaluate, leaving the visual space blank.

The Solution:
To force a value into a non-existent cell, a table calculation must be used. Wrapping the measure in a LOOKUP(..., 0) expression references the current cell offset position (0) within the visual partition. This forces Tableau to create a placeholder coordinate in the visual layout. Wrapping that table calculation output inside ZN() converts that placeholder into a literal 0.00% or 0, causing the line chart to dip continuously down to zero instead of leaving a visual break.

Why Other Options Are Incorrect:

IFNULL or ISNULL without a Table Calculation:
These are row-level functions that check existing row values. They cannot generate new visual coordinates where underlying data lines completely skip a time division.

PREVIOUS_VALUE:
This returns the calculated value of the immediate prior cell mark in the partition, which would repeat the previous month's sales number rather than forcing the value to zero.

References:

Tableau Documentation (Populating Empty Cells with Zeros or Other Values): "To replace empty cells that occur due to a sparse data matrix (no rows exist in the data source), you must use a table calculation function

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

Explanation:

In a box plot, the distribution of profits refers to the spread or variability of the data. This is visually represented by the length of the box (interquartile range, or IQR) and the length of the whiskers (range from minimum to maximum, excluding outliers). The smaller the box and whiskers, the smaller the distribution (less spread) of profits.

Why Central is correct:

The box plot for the Central region would show the shortest box and whiskers, indicating that profit values across states in this region are more tightly clustered together with less variability compared to other regions. This means the profits in Central states are more consistent.

Why the other options are incorrect:

A. South: The South region would show a larger spread, with a longer box or whiskers, indicating greater variability in profits across its states.

B. East: The East region would also show a larger distribution, with more spread in profit values compared to Central.

D. West: The West region likely has the largest distribution, with a wide range of profit values, indicating high variability.

Since the question asks for the region with the smallest distribution, Central is the correct choice because its box plot would appear the most compressed.

Reference:

Tableau Help: Box Plot – A box plot displays the distribution of data based on a five-number summary. The length of the box and whiskers indicates the spread of the data; shorter lengths indicate smaller variability or distribution.

Explanation

When the requirement is for data that is "as close to real-time as possible," a live connection is inherently superior to a scheduled extract refresh. Since the data is stored in a cloud-based database, a live connection from Tableau Cloud is feasible, provided the necessary network security (like the firewall) is correctly configured to allow the connection. This setup ensures that every dashboard interaction queries the most current data directly from the source.

✅ Correct Option: C

Create a connection to the database using Tableau Desktop. Publish the data source to Tableau Cloud using a live connection, ensuring the database firewall has been configured to allow connections from Tableau Cloud.
This option is ideal for real-time needs. A live connection is the only way to get data immediately upon being recorded, avoiding the delay of scheduled extracts. Publishing this live connection to Tableau Cloud makes it accessible to end-users. The crucial step is configuring the database firewall to explicitly authorize the specific IP addresses or domain of Tableau Cloud, ensuring a secure and reliable data flow.

❌ Incorrect Options

A. Create a connection to the database using Tableau Desktop. Publish the data source to Tableau Cloud using a live connection and disable any firewalls on the database.
This option correctly identifies the need for a live connection but suggests a highly insecure practice: disabling firewalls. While disabling a firewall would allow the connection, it severely compromises the security of the underlying database, making the entire system vulnerable. Security best practices mandate allowing connections only from specific, necessary sources (like Tableau Cloud), not disabling the firewall entirely.

B. Create a connection to the database to retrieve the data using Tableau Bridge. Schedule the refresh of the data extract to 15 minutes.
This approach uses a data extract and a 15-minute refresh schedule, which directly contradicts the "as close to real-time" requirement, as the data will be at least 15 minutes old at any given time. Furthermore, Tableau Bridge is typically used to connect Tableau Cloud to on-premise or private network data sources, not standard cloud-based databases, making its inclusion here likely unnecessary.

D. Create a connection to the database using Tableau Desktop and retrieve an extract of the data. Publish the data source from Tableau Desktop to Tableau Cloud and schedule the refresh of the extract.
Like option B, using an extract and a scheduled refresh introduces an unacceptable delay for a real-time requirement. Extracts, even if refreshed frequently, are snapshots of data and will not reflect the time log entries instantaneously. This method is best for improving dashboard performance with less real-time data needs, not for immediate data visibility.

📖 Reference
Tableau Official Documentation: Live Connections vs. Extracts
Source: Tableau Help: Live Connections vs. Extracts (Search for "Tableau Live Connections vs. Extracts" on the official Tableau website)

Note: The official documentation emphasizes that live connections should be used for scenarios requiring access to the most up-to-date data, provided the underlying data source performance is adequate. Security configuration (like firewalls) for live connections to cloud databases is a standard, required step.