Explanation:

Option A:
A filter action on "Select" filters the table to show only orders for the clicked Sub-Category, reducing rows rendered from 10,000+ to a subset. "Exclude all values" when clearing selection keeps the table empty by default, minimizing load time and ensuring fast rendering.
Option B:
Highlight action on Sub-Category still renders all 10,000+ rows, only highlighting relevant ones, so no performance gain.
Option C:
Highlight action on All Fields also renders all rows, offering no speed improvement.
Option D:
Filter action on "Menu" is less intuitive, and "Show all values" when clearing selection renders all 10,000+ rows, slowing the dashboard.

Option A optimizes performance by limiting data rendered, aligning with Tableau best practices.

Reference:
Tableau Dashboard Actions

Explanation:

In Tableau, to optimize report performance by materializing calculations in the extract (i.e., pre-computing and storing results in the .hyper file during extract creation/refresh), the calculation must be a row-level (level-of-detail) expression that doesn't depend on the visualization's partitioning, addressing, or sequencing. This allows Tableau to compute it once per row in the data source and reuse the stored value across all views, reducing query time and CPU load during dashboard rendering. Table calculations, however, are computed dynamically at query time based on the viz layout and cannot be materialized.

Here's a step-by-step evaluation of why A is ideal and the others are not:

Identify Row-Level vs. Aggregative/Sequential Calculations:
Materialization requires the calc to be computable independently per row without aggregation (e.g., SUM) or viz-dependent functions (e.g., LOOKUP, INDEX). Aggregates like SUM([Profit])/SUM([Sales]) need grouping context, so they can't be pre-stored per row. Sequential functions like LOOKUP run across partitions defined by the view.

Option A: Row-Level Net Sales Calculation:
This is a simple arithmetic expression: For each row, replace null Sales/Discount with 0 (ZN), then compute Net Sales = Sales * (1 - Discount).
No aggregation or viz dependencies—purely row-wise.
Materialization Benefit: Create a calculated field for "Net Sales," refresh the extract, and it stores the value per row. Reports using SUM([Net Sales]) now aggregate pre-computed values, speeding up large datasets (e.g., 10x faster queries in high-cardinality data).

Why Not the Others?
B. CASE [Sector Parameter] WHEN 1 THEN "green" WHEN 2 THEN "yellow":
This is row-level (parameter-based color mapping), but it's a dimension (string output), not a measure. Materializing dimensions doesn't yield significant performance gains for report computations—it's more about color logic, which is lightweight anyway. Not the primary target for extract optimization.

C. SUM([Profit])/SUM([Sales]):
This is an aggregate ratio (profit margin). It requires summing across groups (e.g., by customer or date), so it can't be materialized per row—Tableau must recompute it at runtime for each viz partition. Use FIXED LOD like {FIXED : SUM([Profit])/SUM([Sales])} for partial optimization, but not extract materialization.

D. POWER(...) - 1 END:
This is a complex table calculation (CAGR-like: (End Value / Start Value)^(1/(Periods-1)) - 1). It uses SUM (aggregate), LOOKUP (references prior partition), FIRST() (partition start), and INDEX() (row position)—all viz-dependent. Table calcs run last in the order of operations and can't be pre-computed in extracts.

Recommendation:
Convert A to a calculated field named "Net Sales," add it to the data source, and refresh the extract. Test performance via Tableau's Performance Recording (shows reduced "Computing Table Calcs" time).

References
Tableau Help: Extracts and Materialized Calculations – Details row-level calcs for pre-computation.
Tableau Performance Best Practices: Optimize Calculations – Emphasizes moving row-level measures to extracts.
Tableau: Tableau Performance Checklist: Calculations – Contrasts row-level vs. table calcs for materialization.

Explanation:

The key requirement is to identify Saturday and Sunday regardless of the workbook's data source's locale settings. The challenge is that the standard 'weekday' datepart in many systems, including Tableau, can be locale-dependent, meaning which day is considered the first day of the week (Sunday or Monday) can change.

Let's analyze the options:

Why B is Correct: The 'iso-weekday' datepart uses the ISO 8601 standard, which is locale-independent. In this standard:
Monday = 1
Tuesday = 2
Wednesday = 3
Thursday = 4
Friday = 5
Saturday = 6
Sunday = 7
Therefore, the calculation DATEPART('iso-weekday', [Order Date]) >= 6 will correctly return True for both Saturday (6) and Sunday (7) on any machine, in any locale. This perfectly meets the client's requirement.

Why the Other Options are Incorrect:

A. DATEPART('weekday', [Order Date])>=6: This uses the standard 'weekday' datepart. The behavior of this function depends on the data source's locale settings. In a U.S. locale, Sunday is considered the first day of the week (value 1), so Saturday would be 7. In this case, >=6 would catch Saturday (7) and Sunday (1? No, Sunday is 1, so it would be missed). This logic would fail. In a locale where Monday is the first day, it might work, but it is not reliable and violates the "regardless of locale" requirement.

B. DATENAME('iso-weekday', [Order Date])>=6: This is syntactically and logically flawed. DATENAME() returns a string (e.g., "Saturday", "samedi"), not a number. Comparing a string to the number 6 ("Saturday" >= 6) is invalid and will not work.

C. DATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7: This uses the correct 'iso-weekday' datepart but applies the wrong logic. As explained above, in the ISO standard, Monday is 1 and Sunday is 7. This calculation would flag Monday (1) and Sunday (7), which is not what the client wants. They specifically asked for Saturday and Sunday.

Reference & Key Concepts:
DATEPART() vs. DATENAME(): DATEPART() returns an integer, while DATENAME() returns a string. For numerical comparisons like finding a weekend, you must use DATEPART.

ISO 8601 Standard: This is an international standard for date and time representations. Its definition of the week (Monday as day 1) is critical for creating portable, locale-independent calculations.

Locale Dependence: Always be cautious of locale settings when working with dates. Functions that rely on a system's default first day of the week can produce different results when a workbook is opened in a different country. Using the 'iso-' prefix is the best practice to avoid this.

For your exam, remember that 'iso-weekday' is the key to solving any problem that requires a consistent, locale-independent definition of weekdays.

Explanation:

Why Tableau Public?

The client wants:

- Interactive Tableau visualizations embedded on a public website
- Data is small (< 5,000 rows) and updated infrequently via manual refresh
- Cost is a priority

Tableau Public is:

- Free
- Designed specifically for public-facing, embeddable visualizations
- Well-suited for small datasets and manual refresh workflows
- Perfect when there is no requirement to keep the data private (all workbooks on Tableau Public are publicly accessible)

So Tableau Public meets all requirements at no additional cost.

Why not the others?

A. Tableau Cloud licensed per user
Licensing is per user, which becomes expensive if the visualization is public (unlimited viewers).
Better for secure, authenticated internal use, not open public websites.

C. Tableau Embedded Analytics
Typically involves enterprise-level licensing and is intended for authenticated, integrated experiences.
Overkill and more costly for a small, infrequently updated public viz.

D. Tableau Server licensed per core
Requires infrastructure + core-based licensing = most expensive option.
Not appropriate when cost is a priority and Tableau Public satisfies requirements.

✅ Use Tableau Public (B) to publish and embed the dashboard on the public website at minimal cost.

Explanation:

A. Compatibility with newer Tableau Desktop and Prep Builder versions
Necessity: Tableau enforces strict forward and backward compatibility rules. New versions of Tableau Desktop and Tableau Prep Builder often introduce file format changes or connect to server APIs that are only available in recent versions of Tableau Server.
Impact: If users upgrade their local Desktop/Prep tools, they may lose the ability to publish content to the older Tableau Server version, requiring the server upgrade to restore workflow integrity.

D. The security team has a report of bugs and security vulnerabilities in older versions of Tableau
Necessity: All software, including Tableau Server, has a lifecycle of known security vulnerabilities (CVEs) and bugs that are patched in newer versions.
Impact: Running an outdated version of Tableau Server poses a significant security risk to the company's data and infrastructure. Staying current with upgrades ensures the application receives the latest security patches and fixes, which is often a mandatory requirement from enterprise security teams.

❌ Incorrect Answers
B. Users are complaining of performance; the upgrade will reduce the server's hardware requirements
Incorrect. Upgrades generally introduce more features and, while they often bring efficiency improvements, they rarely reduce the overall hardware requirements. Performance issues are usually solved by proper sizing, scaling, and configuration of the existing version, not simply by upgrading.

C. The need to access new features and improvements from Tableau Cloud
Incorrect. Upgrading Tableau Server gives access to new features released for Server, but it does not grant access to exclusive features specific to Tableau Cloud (like the full, integrated suite of Einstein Generative AI tools). Accessing Cloud features requires a platform migration (from Server to Cloud), not just an upgrade. ``