Important Salesforce Analytics-Con-301 Exam Questions

Answer: A

Explanation:

To record the performance of the Property Transactions dashboard in the NYC Property Transactions.twbx workbook and analyze it using a bar chart, follow these detailed steps:

Open the NYC Property Transactions Workbook:

From the desktop, double-click the NYC Property Transactions.twbx workbook to open it in Tableau Desktop.

Start Performance Recording:

Before doing anything else, navigate to the 'Help' menu in Tableau Desktop.

Select 'Settings and Performance', then choose 'Start Performance Recording'.

Open the Property Transactions Dashboard and Reset Filters:

Navigate to the Property Transactions dashboard within the workbook.

Reset all filters to show all values. This usually involves selecting the dropdown on each filter and choosing 'All' or using a 'Reset' button if available.

Stop the Performance Recording:

Go back to the 'Help' menu.

Choose 'Settings and Performance', then select 'Stop Performance Recording'.

Tableau will automatically open a new tab displaying the performance recording results.

Save the Performance Recording:

In the performance recording results tab, go to the 'File' menu.

Click 'Save As' and navigate to the C:\CC\Data\ directory.

Save the file, ensuring it is stored in the desired location.

Create a New Worksheet for Performance Analysis:

Return to the NYC Property Transactions workbook and create a new worksheet by clicking on the 'New Worksheet' icon.

Drag the 'Command Name' field to the Columns shelf.

Drag the 'Elapsed Time' field to the Rows shelf.

Ensure that the 'Worksheet' field is also included in the analysis to break down the time by individual sheets within the dashboard.

Choose 'Bar Chart' from the 'Show Me' options to display the data as a bar chart.

Customize and Finalize the Bar Chart:

Adjust the axes and labels to clearly display the information.

Format the chart to enhance readability, applying color coding or sorting as needed to emphasize sheets with longer load times.

Save Your Work:

Once the new worksheet and the performance recording are complete, ensure all work is saved.

Navigate to the 'File' menu and click 'Save', confirming that changes are stored in the workbook.

Tableau Help Documentation: Provides guidance on how to start and stop performance recordings and analyze them.

Tableau Visualization Techniques: Offers tips on creating effective bar charts for performance data.

By following these steps, you have successfully recorded and analyzed the performance of the Property Transactions dashboard, providing valuable insights into how each component of the dashboard contributes to the overall load time. This analysis is crucial for optimizing dashboard performance and ensuring efficient data visualization.

Answer: B

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

Tableau performance documentation explains that rendering speed is strongly affected by the number of marks that Tableau must draw. Each dimension placed on the Detail shelf increases the granularity of the view and increases the number of marks in the visualization.

Removing unnecessary dimensions:

Reduces the number of marks

Reduces rendering time

Decreases memory and CPU usage

Improves interactive performance

Option A (Show Relevant Values) can slow performance because Tableau must dynamically calculate relevancy each time filters change.

Option C is incorrect because COUNTD is one of the slowest aggregate functions in Tableau and does not speed visualization.

Option D is incorrect because adding more sheets increases dashboard load time and rendering workload.

Removing unnecessary fields from Detail is a documented best practice for improving visualization speed.

Tableau Performance Checklist recommending reducing marks and removing unnecessary dimensions.

Rendering optimization guidance explaining how dimensions on Detail expand mark counts.

Best practices discouraging overuse of COUNTD.

Answer: A

Explanation:

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.

Answer: B

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

According to Tableau's Performance Optimization guidance, rendering time becomes the largest bottleneck when excessive marks, dense data, or overly complex visualizations appear on worksheets. Rendering is the last stage in the Tableau Order of Operations and is directly affected by how many marks must be drawn and how visually complex each view is.

Tableau's performance recommendations explain:

When a performance recording shows that Rendering is the slowest step, the most effective improvement is to reduce the number of marks (records) in the view.

Rendering time is determined by the number of marks, shapes, headers, labels, and visual elements Tableau must draw.

Reducing the amount of data displayed on each worksheet is the most impactful change when rendering is the dominant delay.

Option B directly aligns with this: updating worksheets to reduce the number of records displayed lowers the number of marks, reduces visual density, and improves rendering speed.

Option A is not effective because changing dashboard size does not reduce the number of marks.

Option C would degrade performance because live connections are typically slower than extracts.

Option D improves data preparation and may reduce extract load times, but it does not directly address rendering unless the unused data was contributing to marks in the view. The question indicates the bottleneck is specifically rendering, so reducing marks is the most appropriate action.

Therefore, the most effective solution to reduce rendering time is to reduce the number of records (marks) displayed on worksheets.

Tableau Performance Recording guidance describing rendering as the slowest stage when too many marks are present.

Tableau Performance Checklist recommending reducing the number of marks in views to improve rendering.

Tableau Desktop help sections on best practices for improving visualization performance when rendering dominates.

Answer: B

Explanation:

Tableau's official in-place upgrade steps for single-node Tableau Server require:

Disable scheduled tasks (to prevent extract failures during upgrade).

Run the upgrade script for the new version.

Validate and test the server after upgrade.

The critical detail:

An in-place upgrade means upgrading the existing production environment directly, not installing in a separate environment or cloning VMs.

Option B matches exactly the documented operational steps for an in-place upgrade.

Why the other options are incorrect:

A: Uninstalling Tableau Server is not part of an in-place upgrade workflow.

C: This describes a migration or test upgrade in a separate environment, not an in-place upgrade.

D: VM cloning and restoring is not required for in-place upgrades and is not part of Tableau's official procedure.

Only B represents the correct in-place upgrade sequence.

Tableau Server in-place upgrade instructions: disable tasks run upgrade script test.

Single-node upgrade guidelines noting that uninstalling is not required.

Tableau Server administration materials clarifying the difference between in-place upgrade and sandbox testing.