Analytics-Con-301 Exam Study Guide Free Practice Test LAST UPDATED DATE Jun 17, 2026
The New Analytics-Con-301 2026 Updated Verified Study Guides & Best Courses
Salesforce Analytics-Con-301 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 48
SIMULATION
From the desktop, open the CC workbook. Use the US Population Estimates data source.
You need to shape the data in US Population Estimates by using Tableau Desktop. The data must be formatted as shown in the following table.
Open the Population worksheet. Enter the total number of records contained in the data set into the Total Records parameter.
From the File menu in Tableau Desktop, click Save.
Answer:
Explanation:
See the complete Steps below in Explanation
Explanation:
To shape the data in the "US Population Estimates" data source and enter the total number of records into the "Total Records" parameter in Tableau Desktop, follow these steps:
Open the CC Workbook and Access the Worksheet:
From the desktop, double-click on the CC workbook to open it in Tableau Desktop.
Navigate to the Population worksheet by selecting its tab at the bottom of the window.
Format and Shape the Data:
Ensure the data types match those specified in the requirements: Sex, Origin, Race as strings; Year, Age, Population as whole numbers.
To verify or change the data type, click on the dropdown arrow next to each field name in the Data pane and select "Change Data Type" if necessary.
Calculate Total Number of Records:
Create a new calculated field named "Total Records". To do this, right-click in the Data pane and select "Create Calculated Field".
Enter the formula COUNT([Record ID]) or SUM([Number of Records]) depending on how the data source identifies each row uniquely.
Drag this new calculated field onto the worksheet to display the total number of records.
Enter the Value into the Total Records Parameter:
Locate the "Total Records" parameter in the Data pane. Right-click on the parameter and select "Edit".
Manually enter the number displayed from the calculated field into the parameter, ensuring accuracy to meet the data shaping requirement.
Save Your Changes:
From the File menu, click 'Save' to ensure all your changes are stored.
References:
Tableau Desktop Guide: Provides detailed instructions on managing data types, creating calculated fields, and updating parameters.
Tableau Data Shaping Techniques: Outlines effective methods for manipulating and structuring data for analysis.
This process will ensure the data in the "US Population Estimates" is accurately shaped according to the specified format and that the total number of records is correctly calculated and entered into the designated parameter. This thorough approach ensures data integrity and accuracy in reporting.
NEW QUESTION # 49
A client wants to report Saturday and Sunday regardless of the workbook's data source's locale settings.
Which calculation should the consultant recommend?
- A. DATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7
- B. DATEPART('weekday', [Order Date])>=6
- C. DATENAME('iso-weekday', [Order Date])>=6
- D. DATEPART('iso-weekday', [Order Date])>=6
Answer: A
Explanation:
The calculation DATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7 is recommended because the ISO standard considers Monday as the first day of the week (1) and Sunday as the last day (7). This calculation will correctly identify Saturdays and Sundays regardless of the locale settings of the workbook's data source, ensuring that the report includes these days as specified by the client.
References: The use of the 'iso-weekday' part in the DATEPART function is consistent with the ISO 8601 standard, which is independent of locale settings. This approach is supported by Tableau's documentation on date functions and their behavior with different locale settings123.
To accurately identify weekends across different locale settings, using the 'iso-weekday' component is reliable as it is consistent across various locales:
ISO Weekday Function: The ISO standard treats Monday as the first day of the week (1), which makes Sunday the seventh day (7). This standardization helps avoid discrepancies in weekday calculations that might arise due to locale-specific settings.
Identifying Weekends: The calculation checks if the 'iso-weekday' part of the date is either 1 (Sunday) or 7 (Saturday), thereby correctly identifying weekends regardless of the locale settings.
References:
Handling Locale-Specific Settings: Using ISO standards in date functions allows for uniform results across systems with differing locale settings, essential for consistent reporting in global applications.
NEW QUESTION # 50
A client calculates the percent of total sales for a particular region compared to all regions.
Which calculation will fix the automatic recalculation on the % of total field?
- A. {FIXED [Region]:sum([Sales])}
- B. {FIXED [Region]:[Sales]}/{FIXED: SUM([Sales])}
- C. {FIXED [Region]:sum([Sales])}/{FIXED :SUM([Sales])
- D. {FIXED [Region]:sum([Sales])}/SUM([Sales]}
Answer: D
Explanation:
To correctly calculate the percent of total sales for a particular region compared to all regions, and to ensure that the calculation does not get inadvertently recalculated with each region filter application, the recommended calculation is:
{FIXED [Region]: sum([Sales])}: This part of the formula computes the sum of sales for each region, regardless of any filters applied to the view. It uses a Level of Detail expression to fix the sum of sales to each region, ensuring that filtering by regions won't affect the calculated value.
SUM([Sales]): This part computes the total sum of sales across all regions and is recalculated dynamically based on the filters applied to other parts of the dashboard or worksheet.
Combining the two parts: By dividing the fixed regional sales by the total sales, we get the proportion of sales for each region as compared to the total. This calculation ensures that while the denominator adjusts according to filters, the numerator remains fixed for each region, accurately reflecting the sales percentage without being affected by the region filter directly.
References
This calculation follows Tableau's best practices for using Level of Detail expressions to manage computation granularity in the presence of dashboard filters, as outlined in the Tableau User Guide and official Tableau training materials.
NEW QUESTION # 51
Which technique should a Tableau consultant use to make visualizations faster?
- A. Remove any unneeded dimensions from the Detail shelf.
- B. Include more sheets to increase rendering speed.
- C. Use Show Relevant Values on any filters.
- D. Use COUNTD to aggregate data as much as possible.
Answer: A
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.
NEW QUESTION # 52
An online sales company has a table data source that contains Order Date. Products ship on the first day of each month for all orders from the previous month.
The consultant needs to know the average number of days that a customer must wait before a product is shipped.
Which calculation should the consultant use?
- A. Calc1: DATETRUNC ('day', DATEADD('week', 4, [Order Date]))
Calc2: AVG([Order Date] - [Calc1]) - B. Calc1: DATETRUNC ('month', DATEADD ('month', 1, [Order Date]))
Calc2: AVG(DATEDIFF ('day', [Order Date], [Calc1])) - C. Calc1: DATETRUNC ('month', DATEADD('month', 1, [Order Date]))
Calc2: AVG(DATEDIFF ('week', [Order Date], [Calc1])) - D. Calc1: DATETRUNC ('day', DATEADD ('day', 31, [Order Date]))
Calc2: AVG ([Order Date] - [Calc1])
Answer: B
Explanation:
The correct calculation to determine the average number of days a customer must wait before a product is shipped is to first find the shipping date, which is the first day of the following month after the order date. This is done using DATETRUNC('month', DATEADD('month', 1, [Order Date])). Then, the average difference in days between the order date and the shipping date is calculated using AVG(DATEDIFF('day', [Order Date], [Calc1])). This approach ensures that the average wait time is calculated in days, which is the most precise measure for this scenario.
References: The solution is based on Tableau's date functions and their use in calculating differences between dates, which are well-documented in Tableau's official learning resources and consultant documents12.
To calculate the average waiting days from order placement to shipping, where shipping occurs on the first day of the following month:
Calculate Shipping Date (Calc1): Use the DATEADD function to add one month to the order date, then apply DATETRUNC to truncate this date to the first day of that month. This represents the shipping date for each order.
Calculate Average Wait Time (Calc2): Use DATEDIFF to calculate the difference in days between the original order date and the calculated shipping date (Calc1). Then, use AVG to average these differences across all orders, giving the average number of days customers wait before their products are shipped.
References:
Date Functions in Tableau: Functions like DATEADD, DATETRUNC, and DATEDIFF are used to manipulate and calculate differences between dates, crucial for creating metrics that depend on time intervals, such as customer wait times in this scenario.
NEW QUESTION # 53
A consultant creates a histogram that presents the distribution of profits across a client's customers. The labels on the bars show percent shares. The consultant used a quick table calculation to create the labels.
Now, the client wants to limit the view to the bins that have at least a 15% share. The consultant creates a profit filter but it changes the percent labels.
Which approach should the consultant use to produce the desired result?
- A. Filter with a table calculation WINDOW_AVG(MIN([Profit]), first(), last())
- B. Add the [Profit] filter to the context.
- C. Use a calculation with TOTAL() function instead of a quick table calculation.
- D. Filter with the table calculation used to create labels.
Answer: B
Explanation:
When a filter is applied directly to the view, it can affect the calculation of percentages in a histogram because it changes the underlying data that the quick table calculation is based on. To avoid this, adding the [Profit] filter to the context will maintain the original calculation of percent shares while filtering out bins with less than a 15% share. This is because context filters are applied before any other calculations, so the percent shares calculated will be based on the context-filtered data, thus preserving the integrity of the original percent labels.
References: The solution is based on the principles of context filters and their order of operations in Tableau, which are documented in Tableau's official resources and community discussions123.
When a histogram is created showing the distribution of profits with labels indicating percent shares using a quick table calculation, and a need arises to limit the view to bins with at least a 15% share, applying a standard profit filter directly may undesirably alter how the percent labels calculate because they depend on the overall distribution of data. Placing the [Profit] filter into the context makes it a "context filter," which effectively changes how data is filtered in calculations:
Create a Context Filter: Right-click on the profit filter and select "Add to Context". This action changes the order of operations in filtering, meaning the context filter is applied first.
Adjust the Percent Calculation: With the profit filter set in the context, it first reduces the data set to only those profits that meet the filter criteria. Subsequently, any table calculations (like the percent share labels) are computed based on this reduced data set.
View Update: The view now updates to display only those bins where the profits are at least 15%, and the percent share labels recalculated to reflect the distribution of only the filtered (contextual) data.
References:
Context Filters in Tableau: Context filters are used to filter the data passed down to other filters, calculations, the marks card, and the view. By setting the profit filter as a context filter, it ensures that calculations such as the percentage shares are based only on the filtered subset of the data.
NEW QUESTION # 54
A client wants guidance for Creators to build efficient extracts from large data sources.
What are three Tableau best practices that the Creators should use? Choose three.
- A. Hide all unused fields.
- B. Use aggregate data for visible dimensions, whenever possible.
- C. Keep only the data required for analysis by using extract filters.
- D. Include all the data from the original data source in the extract.
- E. Use only live connections as they are always faster than extracts.
Answer: A,B,C
Explanation:
To build efficient extracts from large data sources, it is crucial to minimize the load and optimize the performance of the extracts:
A . Keep only the data required for analysis by using extract filters: This best practice involves using filters to reduce the volume of data extracted, thus focusing only on the data necessary for analysis.
B . Use aggregate data for visible dimensions, whenever possible: Aggregating data at the time of extraction reduces the granularity of the data, which can significantly improve performance and reduce the size of the extract.
E . Hide all unused fields: Removing fields that are not needed for analysis from the extract reduces the complexity and size of the data model, which in turn enhances performance and speeds up load times.
These practices are endorsed in Tableau's official documentation and training sessions as effective ways to enhance the performance of Tableau extracts and optimize dashboard responsiveness.
NEW QUESTION # 55
A Tableau consultant is asked to evaluate a workbook that is slow to respond and make a recommendation on possible performance improvements. The workbook connects to three extract data sources from an SQL database. The sheets are used in five dashboards. The consultant runs a performance recording on the workbook and notices that the largest amount of time is spent on rendering the visualizations.
What is the most effective approach to reduce the workbook's rendering time?
- A. Filter the unused data before bringing it into the workbook.
- B. Change the connections to live.
- C. Update worksheets to reduce the number of records displayed.
- D. Change the dashboards' size to Automatic.
Answer: C
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.
NEW QUESTION # 56
A client notices that while creating calculated fields, occasionally the new fields are created as strings, integers, or Booleans. The client asks a consultant if there is a performance difference among these three data types.
What should the consultant tell the customer?
- A. Strings are fastest, followed by integers, and then Booleans.
- B. Booleans are fastest, followed by integers, and then strings.
- C. Integers are fastest, followed by Booleans, and then strings.
- D. Strings, integers, and Booleans all perform the same.
Answer: C
Explanation:
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.
References: The performance hierarchy of data types in Tableau calculations is documented in resources that discuss best practices for optimizing Tableau performance1.
NEW QUESTION # 57
From the desktop, open the CC workbook. Use the US Population Estimates data source.
You need to shape the data in US Population Estimates by using Tableau Desktop. The data must be formatted as shown in the following table.
Open the Population worksheet. Enter the total number of records contained in the data set into the Total Records parameter.
From the File menu in Tableau Desktop, click Save.
Answer:
Explanation:
See the complete Steps below in Explanation:
Explanation:
To shape the data in the "US Population Estimates" data source and enter the total number of records into the
"Total Records" parameter in Tableau Desktop, follow these steps:
* Open the CC Workbook and Access the Worksheet:
* From the desktop, double-click on the CC workbook to open it in Tableau Desktop.
* Navigate to the Population worksheet by selecting its tab at the bottom of the window.
* Format and Shape the Data:
* Ensure the data types match those specified in the requirements: Sex, Origin, Race as strings; Year, Age, Population as whole numbers.
* To verify or change the data type, click on the dropdown arrow next to each field name in the Data pane and select "Change Data Type" if necessary.
* Calculate Total Number of Records:
* Create a new calculated field named "Total Records". To do this, right-click in the Data pane and select "Create Calculated Field".
* Enter the formula COUNT([Record ID]) or SUM([Number of Records]) depending on how the data source identifies each row uniquely.
* Drag this new calculated field onto the worksheet to display the total number of records.
* Enter the Value into the Total Records Parameter:
* Locate the "Total Records" parameter in the Data pane. Right-click on the parameter and select
"Edit".
* Manually enter the number displayed from the calculated field into the parameter, ensuring accuracy to meet the data shaping requirement.
* Save Your Changes:
* From the File menu, click 'Save' to ensure all your changes are stored.
References:
Tableau Desktop Guide: Provides detailed instructions on managing data types, creating calculated fields, and updating parameters.
Tableau Data Shaping Techniques: Outlines effective methods for manipulating and structuring data for analysis.
This process will ensure the data in the "US Population Estimates" is accurately shaped according to the specified format and that the total number of records is correctly calculated and entered into the designated parameter. This thorough approach ensures data integrity and accuracy in reporting.
NEW QUESTION # 58
A client has a large data set that contains more than 10 million rows.
A consultant wants to calculate a profitability threshold as efficiently as possible. The calculation must classify the profits by using the following specifications:
. Classify profit margins above 50% as Highly Profitable.
. Classify profit margins between 0% and 50% as Profitable.
. Classify profit margins below 0% as Unprofitable.
Which calculation meets these requirements?
- A. IF [ProfitMargin]>=0.50 Then 'Highly Profitable'
ELSEIF [ProfitMargin]>=0 Then 'Profitable'
ELSE 'Unprofitable'
END - B. IF([ProfitMargin]>=0.50,'Highly Profitable', 'Profitable')ELSE 'Unprofitable'END
- C. IF [ProfitMargin]>0.50 Then 'Highly Profitable'
ELSEIF [ProfitMargin]>=0 Then 'Profitable'
ELSE 'Unprofitable'
END - D. IF [ProfitMargin]>0.50 Then 'Highly Profitable'
ELSEIF [ProfitMargin]>=0 Then 'Profitable'
ELSEIF [ProfitMargin] <0 Then 'Unprofitable'END
Answer: A
Explanation:
The correct calculation for classifying profit margins into categories based on specified thresholds involves the use of conditional statements that check ranges in a logical order:
* Highly Profitable Classification: The first condition checks if the profit margin is 50% or more. This must use the ">=" operator to include exactly 50% as "Highly Profitable".
* Profitable Classification: The next condition checks if the profit margin is between 0% and 50%.
Since any value falling at or above 50% is already classified, this condition only needs to check for values greater than or equal to 0%.
* Unprofitable Classification: The final condition captures any remaining scenarios, which would only be values less than 0%.
References:
Logical Order in Conditional Statements: It is crucial in programming and data calculation to ensure that conditions in IF statements are structured in a logical and non-overlapping manner to accurately categorize all possible values.
NEW QUESTION # 59
A client has many published data sources in Tableau Server. The data sources use the same databases and tables. The client notices different departments give different answers to the same business questions, and the departments cannot trust the data. The client wants to know what causes data sources to return different data.
Which tool should the client use to identify this issue?
- A. Tableau Prep Conductor
- B. Ask Data
- C. Tableau Resource Monitoring Tool
- D. Tableau Catalog
Answer: D
Explanation:
The Tableau Catalog is part of the Tableau Data Management Add-on and is designed to help users understand the data they are using within Tableau. It provides a comprehensive view of all the data assets in Tableau Server or Tableau Online, including databases, tables, and fields. It can help identify issues such as data quality, data lineage, and impact analysis. In this case, where different departments are getting different answers to the same business questions, the Tableau Catalog can be used to track down inconsistencies and ensure that everyone is working from the same, reliable data source.
References: The recommendation for using Tableau Catalog is based on its features that support data discovery, quality, and governance, which are essential for resolving data inconsistencies across different departments12.
When different departments report different answers to the same business questions using the same databases and tables, the issue often lies in how data is being accessed and interpreted differently across departments. Tableau Catalog, a part of Tableau Data Management, can be used to solve this problem:
Visibility: Tableau Catalog gives visibility into the data used in Tableau, showing users where data comes from, where it's used, and who's using it.
Consistency and Trust: It helps ensure consistency and trust in data by providing detailed metadata management that can highlight discrepancies in data usage or interpretation.
Usage Metrics and Lineage: It offers tools for tracking usage metrics and understanding data lineage, which can help in identifying why different departments might see different results from the same underlying data.
References:
Tableau Catalog Usage: The Catalog is instrumental in providing a detailed view of the data environment, allowing organizations to audit, track, and understand data discrepancies across different users and departments.
NEW QUESTION # 60
A consultant has a view using a table calculation to calculate percent of total Sales by Category. The consultant would like to filter out particular categories, but wants the percent of total calculation to remain steady even as they filter items in or out.
What should the consultant do to achieve the desired impact?
- A. Filter Category by using a Context Filter instead of a Dimension Filter.
- B. Filter Category by using a Data Source Filter instead of a Dimension Filter.
- C. Create a FIXED Level of Detail (LOD) expression, and then use that instead of the table calculation.
- D. Create an aggregate expression, and then use that instead of the table calculation.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The key detail of the question:
"filter out particular categories, but wants the percent of total calculation to remain steady even as they filter items in or out." This means the percent of total must ignore filters.
Table calculations always operate after filters, except table calc filters like "Filter on Table Calculation," and after dimension filters, so filtering categories directly will change the denominator.
Tableau's documented solution for "percent of total that does not change with filtering" is:
# Use a FIXED LOD to define the stable denominator
A FIXED LOD expression "freezes" the aggregation level and is unaffected by dimension filters unless explicitly added to context.
This allows the consultant to compute:
{ FIXED : SUM([Sales]) }
or
{ FIXED [Category] : SUM([Sales]) }
Then percent of total becomes:
SUM([Sales]) / { FIXED : SUM([Sales]) }
The FIXED LOD stores the total before filters are applied, ensuring the percent remains steady.
This is exactly what Tableau documentation explains under:
* Level of Detail Expressions
* LODs and Order of Operations
* Using LODs to create filter-independent calculations
Thus, D is correct.
Why the other answers are wrong:
# A. Context Filter
Context filters run before FIXED LODs but after raw data.
If Category is put into context, LOD totals would be reduced.
Table calculation totals still change because table calcs run near the bottom of the pipeline.
# B. Data Source Filter
Data source filters remove rows before all table calculations and LODs.
This would make the percent of total incorrect, because filtered-out categories would physically be gone.
# C. Aggregate Expression
An aggregate field alone does not solve the issue because it still respects dimension filters.
NEW QUESTION # 61
A client is concerned that a dashboard has experienced degraded performance after they added additional quick filters. The client asks a consultant to improve performance.
Which two actions should the consultant take to fulfill the client's request? Choose two.
- A. Add existing filters to Context.
- B. Ensure filters are set to display "Only Relevant Values" instead of "All Values in Database."
- C. Use Filter Actions instead of quick filters.
- D. Modify filters to include an "Apply" button.
Answer: C,D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Quick filters are one of the most expensive features in Tableau because they require queries to populate value lists and dynamic recalculations when filters change.
According to Tableau performance documentation:
1. Add an "Apply" Button
This prevents Tableau from re-running queries every time the user selects a filter value.
Queries are executed once when the user presses Apply.
This is a documented best practice for filter-heavy dashboards.
2. Replace Quick Filters with Filter Actions
Filter actions are far more efficient because:
* They leverage the existing view context
* They do not require separate filter UI queries
* They avoid the overhead of quick filter value lists
Tableau recommends using filter actions instead of multiple quick filters for better performance.
Why the other options are incorrect:
* B. Add filters to Context: Context filters make downstream filters faster, but do not reduce quick filter processing cost; they can even increase extract size and slow down the dashboard.
* C. Only Relevant Values: This actually slows performance because Tableau must re-evaluate the entire data set to determine relevancy every time filters update.
Thus, A and D are the correct performance-improvement approaches.
* Tableau Performance Checklist recommending Apply button for multi-select filters.
* Performance documentation advising the use of Filter Actions over multiple quick filters.
* Filtering best practices explaining the cost of Only Relevant Values.
NEW QUESTION # 62
A client wants to produce a visualization to show quarterly profit growth and aggregated sales totals across a number of product categories from the data provided below.
Which set of charts should the consultant use to meet the client's requirements?
- A. Scatter plot and pie chart
- B. Gantt and bar charts
- C. Waterfall chart and tree map
- D. Line and bubble charts
Answer: C
Explanation:
To effectively display quarterly profit growth and aggregated sales totals across different product categories, a combination of a Waterfall chart and a Tree Map is recommended:
Waterfall Chart: This chart type is excellent for visualizing the sequential growth or decline of profits across different quarters for each sub-category. It clearly shows how profits accumulate over time, highlighting both positive and negative changes, which makes it ideal for tracking profit growth or decline through the quarters.
Tree Map: A Tree Map can efficiently display aggregated sales totals where each block size represents the total sales of a product category, providing a quick, visually impactful comparison across categories. This is especially useful when the client wants to understand which categories contribute most to sales in a glanceable format.
Together, these charts provide a comprehensive overview of both profit trends over time (Waterfall Chart) and a comparative snapshot of sales performance across categories (Tree Map), meeting the client's need to analyze performance dynamics in a detailed yet consolidated manner.
References
These recommendations are based on common best practices for data visualization in Tableau, where specific chart types are chosen for their strengths in communicating certain types of data relationships and dynamics, as detailed in Tableau's official visualization guides.
NEW QUESTION # 63
A client builds a dashboard that presents current and long-term stock measures. Currently, the data is at a daily level. The data presents as a bar chart that presents monthly results over current and previous years. Some measures must present as monthly averages.
What should the consultant recommend to limit the data source for optimal performance?
- A. Limit data to current and previous years as well as to the last day of each month to eliminate the need to use the averages.
- B. Limit data to current and previous years and leave data at daily level to calculate the averages in the report.
- C. Move calculating averages to data layer and aggregate dates to monthly level.
- D. Limit data to current and previous years, move calculating averages to data layer, and aggregate dates to monthly level.
Answer: D
Explanation:
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.
References: The recommendation is based on the guidelines provided in Tableau's official documentation on optimizing workbook performance, which includes tips on data management and aggregation for better performance12.
NEW QUESTION # 64
A stakeholder has multiple files saved (CSV/Tables) in a single location. A few files from the location are required for analysis. Data transformation (calculations) is required for the files before designing the visuals. The files have the following attributes:
. All files have the same schema.
. Multiple files have something in common among their file names.
. Each file has a unique key column.
Which data transformation strategy should the consultant use to deliver the best optimized result?
- A. Use wildcard Union option to combine/merge all the files together before doing the data transformation (calculations).
- B. Apply the data transformation (calculations) in each require file and do the wildcard union to combine/merge before designing the visuals.
- C. Apply the data transformation (calculations) in each require file and do the join to combine/merge before designing the visuals.
- D. Use join option to combine/merge all the files together before doing the data transformation (calculations).
Answer: A
Explanation:
Moving calculations to the data layer and materializing them in the extract can significantly improve the performance of reports in Tableau. The calculation ZN([Sales])*(1 - ZN([Discount])) is a basic calculation that can be easily computed in advance and stored in the extract, speeding up future queries. This type of calculation is less complex than table calculations or LOD expressions, which are better suited for dynamic analysis and may not benefit as much from materialization12.
References: The answer is based on the best practices for creating efficient calculations in Tableau, as described in Tableau's official documentation, which suggests using basic and aggregate calculations to improve performance1. Additionally, the process of materializing calculations in extracts is detailed in Tableau's resources2.
Given that all files share the same schema and have a common element in their file names, the wildcard union is an optimal approach to combine these files before performing any transformations. This strategy offers the following advantages:
Efficient Data Combination: Wildcard union allows multiple files with a common naming scheme to be combined into a single dataset in Tableau, streamlining the data preparation process.
Uniform Schema Handling: Since all files share the same schema, wildcard union ensures that the combined dataset maintains consistency in data structure, making further data manipulation more straightforward.
Pre-Transformation Combination: Combining the files before applying transformations is generally more efficient as it reduces redundancy in transformation logic across multiple files. This means transformations are written and processed once on the unified dataset, rather than repeatedly for each individual file.
References:
Wildcard Union in Tableau: This feature simplifies the process of combining multiple similar files into a single Tableau data source, ensuring a seamless and efficient approach to data integration and preparation.
NEW QUESTION # 65
......
Get Prepared for Your Analytics-Con-301 Exam With Actual 102 Questions: https://lead2pass.real4prep.com/Analytics-Con-301-exam.html