Salesforce Analytics-Con-301 Exam Questions

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.

When dashboards are published to Tableau Cloud, the function USERNAME() returns the user's Tableau Cloud username, which is the email address associated with their Tableau Cloud account.

Tableau documentation states:

On Tableau Cloud, the value returned by USERNAME() is always the user's email address.

Row-Level Security (RLS) is typically implemented using a comparison of USERNAME() to an email field in the data source.

For secure filtering, the field compared to USERNAME() must match the authentication identity exactly.

Looking at the provided table:

''Abbreviated Name'' contains short custom codes like ''SMiller,'' which do not match Tableau Cloud usernames.

''Lower Case Name'' contains names like ''sean miller,'' which also do not match Tableau Cloud usernames.

''Email'' contains the full email address for each user, such as ''Sean.Miller@superstore.com,'' which is the only field that corresponds to what USERNAME() returns in Tableau Cloud.

Therefore, the correct field to reference is Email.

Tableau Cloud authentication documentation stating USERNAME() returns the user's email address.

Row-Level Security setup guidance recommending the comparison USERNAME() = [Email Field].

Tableau security practices indicating only the email column will match USERNAME() values on Tableau Cloud.

Comprehensive and Detailed Explanation From Exact Extract:

The problem:

Custom SQL joins two multi-row tables, causing many-to-many duplication.

This artificially multiplies claim costs.

The extract becomes heavy and slow due to Custom SQL.

Tableau's recommended solution:

Use Relationships in the Logical Layer

Instead of physical joins

Tableau resolves many-to-many issues automatically

Query is generated at the appropriate granularity to avoid duplication

This is exactly Option A.

Relationships allow the Claims facts to remain at the claim grain and Members to remain at the member grain. Tableau resolves aggregations correctly, preventing inflated values.

Why the others are incorrect:

B --- Physical Join

Would continue the same duplication problem because multi-row joins multiply rows.

C --- LODs

Would require complex calculations and are error-prone.

They do NOT fix the duplication in the underlying extract.

D --- Table Calculations

Happen after Tableau aggregates the duplicated data --- too late to fix the inflated baseline numbers.

Thus, the only correct and modern solution is relationships.

Relationships documentation explaining resolution of many-to-many granularity issues.

Guidance recommending avoiding Custom SQL for performance reasons.

Logical Layer behavior preventing row-duplication errors.