Get Salesforce Analytics-Con-301 Exam Practice Questions - Real and Updated

Answer : B

For optimal performance, it is recommended to limit the data to what is necessary for analysis, which in this case would be the current and previous years. Moving the calculation of averages to the data layer and aggregating the dates to a monthly level will reduce the granularity of the data, thereby improving the performance of the dashboard. This approach aligns with best practices for optimizing workbook performance in Tableau, which suggest simplifying the data model and reducing the number of records processed12.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Tableau allows certain calculations to be materialized in extracts, meaning they are precomputed and stored inside the .hyper file to improve performance.

According to Tableau's extract documentation:

Materializable calculations must be compatible with the extract engine and must not depend on dynamic, view-based, or post-query logic.

Only row-level calculations and aggregation-level calculations without dependencies on runtime context can be materialized.

Tableau cannot materialize any calculation containing:

Table calculation functions

Functions requiring post-aggregation logic

View-dependent elements

Parameters that need runtime evaluation

Evaluation of the choices:

A . A row-level calculation --- Correct

Row-level calculations operate on each record individually before aggregation.

Tableau documentation specifies that these calculations can be pushed down into the extract and materialized because they do not depend on the visualization or user interaction.

Examples include concatenation, arithmetic, string manipulation, and row-based logic such as:

[Sales] * [Quantity] or IF [Region] = 'West' THEN 1 END

These can be precomputed inside the extract, improving performance.

B . A calculation that contains table calculation functions --- Not allowed

Table calculations (WINDOW_SUM, INDEX, RUNNING_SUM, RANK, etc.) depend on the table structure after aggregation and query execution.

Therefore, Tableau documentation states they cannot be materialized in extracts.

C . A calculation that contains parameters --- Not allowed

Parameters are evaluated at runtime, meaning the user can change their value.

Because of this, Tableau cannot permanently compute and store such a calculation inside an extract.

D . A calculation that contains an aggregation --- Generally not materialized

Aggregated calculations often depend on query context and cannot always be materialized.

Only simple, context-free aggregations might be materialized, but Tableau explicitly warns that aggregations are not guaranteed candidates for extract materialization.

Thus, this is not the best answer compared to row-level logic.

Conclusion

Only row-level calculations meet Tableau's exact requirements for materialization in extracts.

Reference From Tableau Consultant Documentation

Tableau Extract documentation describing materializable calculation types.

Tableau guidance stating table calculations and parameter-dependent calculations cannot be materialized.

Extract optimization guidelines describing row-level logic as eligible for materialization.

Answer : D

Comprehensive and Detailed Explanation From Exact Extract:

The dataset contains timestamps for each individual user interaction. Growth in user adoption over 6 months means the number of rows has expanded significantly. Tableau's performance documentation states that large row-level datasets can cause performance degradation even when using extracts, especially when:

The visualization is aggregated to a higher level (such as daily), and

The underlying extract still contains much more granular data than needed.

Tableau recommends pre-aggregating data before it reaches Tableau Desktop, which reduces extract size, memory use, and query time. This improves performance without changing what the visualization displays.

Option D uses Tableau Prep, which is included with Tableau Creator licensing and therefore incurs no additional cost. Tableau Prep can aggregate raw timestamp data into daily totals per product feature, which matches the visualization's actual granularity. This results in:

A dramatically smaller extract

Faster queries

No change to how the dashboard looks or functions

Option A would remove product features from the visualization, altering the dashboard content and reducing insight, which does not meet the requirement of minimal impact.

Option B requires purchasing an external ETL tool, which violates the requirement of no additional cost.

Option C reduces the number of extract refreshes but does not improve dashboard performance; the data would remain equally granular and equally slow.

Therefore, Tableau Prep aggregation is the correct solution that improves performance while maintaining the same visualization and incurring no additional cost.

Tableau performance guidelines recommending pre-aggregation of highly granular datasets.

Tableau Prep documentation stating it can be used to aggregate data before creation of extracts.

Tableau's extract optimization guidance describing how reducing row counts improves query and visualization performance.

Answer : A

To compute the required calculations and update the worksheet in Tableau Desktop, follow these steps:

Compute Average Sales by Segment for Each Category and Year:

Open the CC workbook and navigate to the Categorical Sales worksheet.

Drag the 'Sales' field to the Rows shelf if it's not already there.

Drag the 'Segment' field to the Rows shelf as well, placing it next to 'Category' and 'Year'.

Right-click on the 'Sales' field in the Rows shelf and select 'Quick Table Calculation' > 'Average'. This will compute the average sales for each segment within each category and year.

Create a Calculation for Year-over-Year Percentage Change:

Right-click in the data pane and select 'Create Calculated Field'.

Name the calculated field something descriptive, e.g., 'YoY Sales Change'.

Enter the formula to calculate the year-over-year percentage change:

(ZN(SUM([Sales])) - LOOKUP(ZN(SUM([Sales])), -1)) / ABS(LOOKUP(ZN(SUM([Sales])), -1))

Click 'OK' to save the calculated field.

Replace the Original Measure with the Year-over-Year Percentage Change in the Crosstab:

Remove the original 'Sales' measure from the view by dragging it off the Rows shelf.

Drag the newly created 'YoY Sales Change' calculated field to the Rows shelf where the 'Sales' field was originally.

Format the 'YoY Sales Change' field to display as a percentage. Right-click on the field in the Rows shelf, select 'Format', and adjust the number format to percentage.

Save Your Changes:

From the File menu, click 'Save' to ensure all your changes are stored.

Tableau Help: Offers guidance on creating calculated fields and using table calculations.

Tableau Desktop User Guide: Provides instructions on formatting and saving worksheets.

These steps allow you to manipulate data within Tableau effectively, using table calculations to analyze trends and changes in sales data by category and segment over years.

Topic 3, Knowledge-Based Section B

Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

Tableau's RLS entitlement design patterns include:

1. Deepest Granularity Method

Requires one unique role one unique lowest-level value pairing.

Fails when the dataset contains duplicate lowest-level values (e.g., multiple ''East'' sub-regions across different regions).

Cannot operate correctly when some lowest-level values are NULL.

Thus, the deepest granularity method is not valid here.

2. Sparse Entitlements Method

Tableau documentation states:

Sparse entitlements define RLS at each level of the hierarchy instead of only at the lowest level.

This method supports duplicate lowest-level values.

Handles scenarios where some levels are NULL because higher-level entitlements (e.g. Region = AMER) can still correctly apply.

More flexible for hierarchical geographic structures (Region Sub-Region Country, etc.).

Given the client's dataset:

Multiple ''East'' and ''West'' sub-regions

Some ''Null'' sub-regions

Hierarchical levels present

Sparse entitlements is the only correct and supported choice.

Why the incorrect options are wrong:

A & B --- Deepest Granularity

Deepest granularity fails when the lowest-level values are not unique.

It cannot handle NULL values at the lowest tier.

Performance is not superior in this scenario.

D --- Sparse because it is most performant

Performance is not the defining advantage.

Flexibility and ability to handle duplicate lowest-level values is.

Thus, C is the correct statement.

RLS entitlement design patterns: deepest vs. sparse entitlements.

Rules requiring unique lowest-level identifiers for deepest granularity.

Guidance stating sparse entitlements should be used when duplicates or NULL values exist in hierarchical structures.