Salesforce Analytics-Con-301 Exam Questions

Comprehensive and Detailed Explanation From Exact Extract:

Tableau documentation explains:

Tableau Public

Free platform.

Allows public sharing and embedding of fully interactive dashboards.

Ideal for small datasets and infrequent updates.

Does not require user-based licensing.

Embedding is unrestricted because all content is publicly visible.

This perfectly matches the scenario:

Public-facing website

Low cost priority

Small dataset

Manual, infrequent updates

Why the other options are incorrect:

A . Tableau Cloud (per user)

Requires paid licenses.

Does not allow unrestricted public embedding without expensive add-ons.

Designed for secure internal use, not public web-wide embedding.

C . Tableau Embedded Analytics

A paid embedding solution requiring proper licensing.

Designed for large-scale, secure, programmatic embedding --- too costly for this use case.

D . Tableau Server (per core)

Requires server infrastructure & licensing.

Far more expensive than Tableau Public.

Thus, Tableau Public is the correct, cost-effective solution.

Tableau Public documentation describing free embedding for public websites.

Comparison guides showing Tableau Cloud/Server require licensing for embedding.

Public vs. Enterprise Tableau deployment best practices.

Comprehensive and Detailed Explanation From Exact Extract:

The requirement is:

Compute total sales per customer, not per transaction.

Then compute the average of those customer totals, grouped by region.

Tableau documentation states that FIXED LOD expressions are used to calculate values at a specific level of granularity regardless of the view.

To solve the business need:

Step 1:

Calculate total customer sales for each Customer ID within each Region:

{ FIXED [Customer ID], [Region] : SUM([Sales Amount]) }

This produces one number per customer per region.

Step 2:

Compute the average of those totals:

AVG( { FIXED [Customer ID], [Region] : SUM([Sales Amount]) } )

This yields:

Average total customer sales by region

This is exactly option C.

Why the other options are incorrect:

A . EXCLUDE Region: Would combine regions and incorrectly calculate overall totals.

B . FIXED Region: AVG(Sales Amount): Computes average of line-level sales, not customer totals.

D . FIXED Customer ID + Region: AVG(Sales Amount): Averages individual transactions, not customer totals.

Only option C matches the required two-step logic.

LOD Expressions: FIXED for computing customer-level aggregates.

Nested LOD usage for first calculating customer totals, then averaging them at a higher level.

Tableau guidance: SUM inside FIXED for per-customer totals, AVG outside for averaging customers.

The dataset shown is a classic ''wide'' format'':

A single row per state

Separate columns for each year: 2019, 2020, 2021, 2022, 2023, 2024

Tableau's documentation on data structure and pivoting explains:

Why A is TRUE

Tableau documentation identifies wide datasets (multiple columns representing categories such as years, months, or similar time periods) as high-maintenance structures because:

For every new year, a new column must be added.

Metadata and calculations must be updated each time.

This type of structure is described as having poor scalability and higher maintenance.

This dataset fits that exact description, so A is correct.

Why C is TRUE

According to Tableau's ''Pivot Data from Columns to Rows'' section:

Wide datasets can and should often be pivoted so that repeated columns (such as year columns) become rows.

Pivoting enables dynamic capabilities such as:

Year filters (year selector)

Time-series analysis

Consistent aggregations

Simplified calculations

Pivoting this dataset would produce:

State

Year

Value

Alabama

2019

2300.39

Alabama

2020

3030.39

...

...

...

This makes the dataset tall and tidy, which Tableau identifies as better for analysis and dashboard interactivity.

Therefore, C is correct.

Why B is FALSE

The column names (2019, 2020, 2021...) are simply numbers.

Tableau documentation stresses that good metadata includes descriptive column names.

These column names:

Do not indicate what the measure represents (Revenue? Sales? Population?)

Only show the year, not the meaning of the metric

Thus they are not considered accurate or descriptive column names.

Why D is FALSE

The dataset is already denormalized, not normalized.

Denormalized data means combining multiple attributes (like multiple years) into one table, which is exactly what this dataset already does.

Tableau documentation explains that wide data is already denormalized, and the recommended fix is pivoting, not further denormalization.

Therefore, D is incorrect.

Comprehensive and Detailed Explanation From Exact Extract:

Tableau allows fiscal calendars to be defined at the data source level, affecting how all date fields behave across the workbook.

According to Tableau documentation:

Fiscal calendars must be set using Data Source Date Properties.

Once set, this becomes a default property for all date fields unless overridden.

This allows charts, hierarchies, and date parts to automatically follow the fiscal year starting in February.

Correct procedure:

Go to Data Source.

Open Date Properties.

Set Fiscal Year Start = February.

(Optional) Adjust Date Field Default Properties.

This ensures all charts and date hierarchies use the fiscal calendar automatically.

Why the other options are incorrect:

A . Right-click on axis Use Fiscal Calendar

This option does not exist in Tableau.

B . Set Fiscal Year in Data Preview

Not supported; fiscal configuration isn't made in the preview window.

C . Use FISCALYEAR() / FISCALQUARTER()

This is manual, requires custom fields, and does not configure Tableau's built-in fiscal calendar system.

This is more work and not the correct method.

Only Option D configures the fiscal calendar globally and correctly.

Tableau Date Properties documentation specifying fiscal year settings.

Default Properties configuration for date fields.

Official guidance for implementing fiscal calendars.

When a client republishes a dashboard after making changes and users report broken bookmarks, the likely causes include:

The dashboard was published to a different project: Changing the project location alters the URL path, causing bookmarks to point to a now non-existent dashboard location.

The dashboard was published with a new name: Altering the dashboard's name changes its URL, resulting in broken bookmarks as the previous URL no longer leads to the intended dashboard.