Salesforce Analytics-Con-301 Exam Dumps

To improve performance by moving calculations to the data layer and materializing them in the extract, the consultant should choose calculations that benefit from pre-computation and significantly reduce the load during query time:

Aggregation-Level Calculation: The formula SUM([Profit])/SUM([Sales]) calculates a ratio at an aggregate level, which is ideal for pre-computation. Materializing this calculation in the extract means that the complex division operation is done once and stored, rather than being recalculated every time the report is accessed.

Performance Improvement: By pre-computing this aggregate ratio, Tableau can utilize the pre-calculated fields directly in visualizations, which speeds up report loading and interaction times as the heavy lifting of data processing is done during the data preparation stage.

Materialization in Extracts: This concept involves pre-calculating and storing complex aggregations or calculations within the Tableau data extract itself, improving performance by reducing the computational load during visualization rendering.

Tableau's built-in geocoding supports only the following geographic roles:

Country

State / Province

County

City

Postal Code

Airport

Area codes

Congressional districts, etc.

Tableau does NOT natively geocode street-level addresses.

When a dataset contains street address fields, Tableau will not recognize them as geographic fields because:

Street Address 1 and Street Address 2 are not valid Tableau geographic roles.

Tableau cannot automatically translate street text (like ''101 Random Place Rd'') into latitude/longitude.

Therefore, to plot street-level points on a map, Tableau requires:

Custom geocoding OR latitude/longitude fields.

Tableau documents that for exact address locations:

You must either supply latitude and longitude for each address, or

Use custom geocoding, where the user uploads a .csv with addresses matched to coordinates.

Why the other answer choices are incorrect:

B . Change the data type to Geographic role

Street address fields cannot be assigned a geographic role. Tableau will reject them or not map them.

C . Establish a hierarchy

Hierarchies help with drilldown but do not generate geographic coordinates for street addresses.

D . Add a map layer

Map layers allow visual overlays but cannot generate geocoding for address fields.

The only correct way to map street addresses is to custom geocode (or supply lat/long), which matches option A.

Tableau Geocoding documentation stating street-level addresses are not natively supported.

Custom Geocoding instructions for mapping exact address points.

Mapping best practices stating that lat/long or custom geocode files are required for street accuracy.

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.

In Tableau, the performance of calculated fields can vary based on the data type used. Calculations involving integers and Booleans are generally faster than those involving strings. This is because numerical operations are typically more efficient for a computer to process than string operations, which can be more complex and time-consuming. Therefore, when performance is a consideration, it is advisable to use integers or Booleans over strings whenever possible.

Comprehensive and Detailed Explanation From Exact Extract:

When optimizing performance with live connections, Tableau documentation emphasizes minimizing the workload passed to the database. Key principles include:

Databases resolve numeric and Boolean fields significantly faster than strings and dates.

Using simpler data types reduces query parsing time and improves join and filter performance.

This is a standard Tableau recommendation for live query optimization.

Why the other answers are incorrect:

B: Table calculations add workload on Tableau, but live performance depends on database efficiency; granular table calc processing worsens performance.

C: Custom SQL often hurts performance because it disables query optimization, increases load times, and prevents Tableau from generating efficient queries.

D: Compute Calculations Now applies only to extracts, and has no effect on live connections.

Thus, the documented performance best practice for live sources is to use numbers and Booleans instead of strings and dates.

Live connection optimization guidance: prefer numeric and Boolean fields over strings/dates.

Best practices cautioning against Custom SQL for performance.

Documentation stating Compute Calculations Now applies only to extracts.