Sep-2024 Realistic TCC-C01 Accurate & Verified Answers As Experienced in the Actual Test!
Latest Tableau TCC-C01 Practice Test Questions, Tableau Certified Consultant Exam Dumps
NEW QUESTION # 17
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. DATENAME('iso-weekday', [Order Date])>=6
- C. DATEPART('iso-weekday', [Order Date])>=6
- D. DATEPART('weekday', [Order Date])>=6
Answer: A
Explanation:
The calculationDATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7is 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 avoiddiscrepancies 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 # 18
A client wants to migrate their Tableau Server to Tableau Cloud. The Tableau Server is configured with three sites: Finance, Strategy, and Marketing. A consultant must provide a solution that minimizes user impact and costs.
Which configuration should the consultant recommend for Tableau Cloud to meet the client's requirements?
- A. One Tableau Cloud instance configured with a Finance project folder, Strategy project folder, and Marketing project folder
- B. Three separate Tableau Cloud instances for Finance, Strategy, and Marketing
- C. One Tableau Cloud instance configured with all workbooks in a single project
- D. One Tableau Cloud instance with two sites for Strategy and Marketing, and one Tableau Server instance for Finance
Answer: A
Explanation:
To minimize user impact and costs while migrating from Tableau Server to Tableau Cloud with multiple sites, the best solution is:
* Single Tableau Cloud Instance with Multiple Projects: Instead of multiple sites which could imply higher management overhead and possibly higher costs, configuring one Tableau Cloud instance with different project folders for each former site (Finance, Strategy, Marketing) is most efficient.
* Benefits: This setup maintains organizational separation of data and access similar to having different sites but leverages the unified management and simplicity of a single cloud instance. It reduces complexity in user access management and integration points.
* Implementation: Each project folder acts like a mini-site within the larger instance, where specific permissions and content can be managed independently, akin to the original server setup but within a single cloud-based environment.
ReferencesThis recommendation is in line with best practices for cloud migration focusing on consolidation and cost efficiency, as suggested in Tableau's official documentation for cloud migration strategies.
NEW QUESTION # 19
A consultant plans a Tableau deployment for a client that uses Salesforce. The client wants users to automatically see Tableau views of regional sales filtered by customer as soon as the users sign into Salesforce.
Which approach should the consultant use to deliver the final visualization?
- A. Create a list of URLs that the users can click in Salesforce.
- B. Publish to Tableau Mobile for viewing.
- C. Embed views into Salesforce.
- D. Create subscriptions for each view to deliver reports by email.
Answer: C
Explanation:
To ensure that users automatically see Tableau views of regional sales filtered by customer as they sign into Salesforce, embedding the views directly into Salesforce is most effective:
* Embedding Views: Tableau provides capabilities to embed its dashboards into web applications such as Salesforce. This approach ensures that the visualization is part of the Salesforce user interface, enhancing user experience by not requiring users to navigate away from Salesforce to view the data.
* Implement this by using Tableau's embedding code, which can be generated from the Tableau Server for each specific view. Place this embed code into the Salesforce Visualforce pages or use Salesforce Canvas to integrate these views seamlessly.
* This setup allows the Tableau views to inherit user credentials from Salesforce, enabling personalized data visualization based on the user's access rights and region, directly aligned with their Salesforce login session.
ReferencesThe embedding technique is documented in both Tableau's and Salesforce's official integration guides, which provide step-by-step instructions on embedding Tableau views into Salesforce platforms.
NEW QUESTION # 20
For a new report, a consultant needs to build a data model with three different tables, including two that contain hierarchies of locations and products. The third table contains detailed warehousing data from all locations across six countries. The consultant uses Tableau Cloud and the size of the third table excludes using an extract.
What is the most performant approach to model the data for a live connection?
- A. Joining the tables in Tableau Prep
- B. Relating the tables in Tableau Desktop
- C. Joining the tables in Tableau Desktop
- D. Blending the first two tables with the third
Answer: B
Explanation:
For a performant live connection in Tableau Cloud, especially when dealing with large datasets that preclude the use of extracts, relating the tables in Tableau Desktop is the recommended approach. This method allows for flexibility in how the data is queried and can improve performance by leveraging Tableau's relationships feature, which optimizes queries for the underlying database.
References:The best practices for live connections in Tableau Cloud suggest using relationships to manage complex data models efficiently1.Additionally, Tableau's documentation on connecting data sources recommends using relationships for better performance with live connections2.
NEW QUESTION # 21
A client is working in Tableau Prep and has a field named Orderld that is compiled by country, year, and an order number as shown in the following table.
What should the consultant use to transform the table in the most efficient manner?
- A. A calculated field that uses the LEFT function
- B. A calculated field that uses the TRIM function
- C. The Aliases option
- D. The Split option
Answer: D
Explanation:
To transform theOrderldfield in Tableau Prep, the Split option is the most efficient and straightforward method. Here's how you can apply it:
* In Tableau Prep, drag your dataset into the flow.
* Click on theOrderldfield in the workspace to select it.
* Look for the option in the toolbar that says "Split" and select it.
* Choose "Automatic Split" if the delimiters (such as hyphens) are consistent; Tableau Prep should automatically detect the hyphen as the delimiter and split theOrderldinto multiple new fields.
* The dataset should now show new columns: one for the country code (CA, FR, US), one for the year (2017), and one for the order number (152156, 152157, etc.).
The Split option works effectively here because it automatically identifies and uses the hyphen as the delimiter to divide the originalOrderldinto the desired components without manual specification of conditions or writing any formulas.
ReferencesThis procedure is based on the standard functionalities provided in Tableau Prep for splitting a field into multiple columns based on a delimiter, as described in the Tableau Prep user guide.
NEW QUESTION # 22
From the desktop, open the CC workbook.
Open the City Pareto worksheet.
You need to complete the Pareto chart toshow the percentage of sales compared tothe percentage of cities. The chart mustshow references lines to visualize how thedata compares to the Pareto principle.
From the File menu in Tableau Desktop, clickSave.
Answer:
Explanation:
See the complete Steps below in Explanation:
Explanation:
To complete the Pareto chart in the "City Pareto" worksheet of your Tableau Desktop and add reference lines to illustrate how the data compares to the Pareto principle, 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 City Pareto worksheet by selecting its tab at the bottom of the window.
* Construct the Pareto Chart:
* Ensure that sales data is aggregated by city. If not, drag the 'City' dimension to the Columns shelf and the 'Sales' measure to the Rows shelf.
* Sort the sales data in descending order to properly align the cities according to their sales contribution.
* To create a running total of sales, right-click on the 'Sales' measure on the Rows shelf, select
'Quick Table Calculation', and choose 'Running Total'.
* Drag the 'Number of Records' field to the Rows shelf next to the Sales running total. Right-click on it, select 'Quick Table Calculation', and choose 'Running Total'. Set its calculation to 'Percent of Total' from the 'Edit Table Calculation' option to represent the percentage of cities.
* Add Reference Lines for the Pareto Principle:
* Click on the Analytics tab in the sidebar.
* Drag a 'Reference Line' element and drop it onto the chart area.
* Set the Reference Line for the Sales axis at 80% to represent the typical Pareto cutoff where 80% of effects come from 20% of causes.
* Add another Reference Line on the axis representing the percentage of cities, set at 20%, to visually assess the Pareto principle.
* Adjust the Appearance of the Chart:
* Format the reference lines by right-clicking on them, selecting 'Edit', and choosing a distinct style or color to make them stand out.
* Ensure the chart is clear and labels are appropriately adjusted for easy understanding of the data visualization.
* Save Your Changes:
* From the File menu, click 'Save' to ensure all your changes are stored.
References:
* Tableau Help: Offers detailed guidance on creating Pareto charts and adding reference lines.
* Tableau Visualization Best Practices: Provides tips on effectively displaying cumulative data and principles such as Pareto.
By following these steps, you will have successfully enhanced the City Pareto worksheet to include a complete Pareto chart with reference lines that illustrate how the sales data compares to the Pareto principle, making it easier to analyze and communicate the distribution of sales across cities.
NEW QUESTION # 23
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 and leave data at daily level to calculate the averages in the report.
- B. Limit data to current and previous years, move calculating averages to data layer, and aggregate dates to monthly level.
- C. 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.
- D. Move calculating averages to data layer and aggregate dates to monthly level.
Answer: B
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 foroptimizing 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 # 24
For a new report, a consultant needs to build a data model with three different tables, including two that contain hierarchies of locations and products. The third table contains detailed warehousing data from all locations across six countries. The consultant uses Tableau Cloud and the size of the third table excludes using an extract.
What is the most performant approach to model the data for a live connection?
- A. Joining the tables in Tableau Prep
- B. Relating the tables in Tableau Desktop
- C. Joining the tables in Tableau Desktop
- D. Blending the first two tables with the third
Answer: B
NEW QUESTION # 25
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. Use a calculation with TOTAL() function instead of a quick table calculation.
- B. Filter with the table calculation used to create labels.
- C. Add the [Profit] filter to the context.
- D. Filter with a table calculation WINDOW_AVG(MIN([Profit]), first(), last())
Answer: C
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 # 26 
From the desktop, open the NYC
Property Transactions workbook.
You need to record the performance of
the Property Transactions dashboard in
the NYC Property Transactions.twbx
workbook. Ensure that you start the
recording as soon as you open the
workbook. Open the Property
Transactions dashboard, reset the filters
on the dashboard to show all values, and
stop the recording. Save the recording in
C:\CC\Data\.
Create a new worksheet in the
performance recording. In the worksheet,
create a bar chart to show the elapsed
time of each command name by
worksheet, to show how each sheet in
the Property Transactions dashboard
contributes to the overall load time.
From the File menu in Tableau Desktop,
click Save. Save the performance
recording in C:\CC\Data\.
Answer:
Explanation:
See the complete Steps below in Explanation:
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.
References:
* 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.
NEW QUESTION # 27
A client creates a report and publishes it to Tableau Server where each department has its own user group set on the server. The client wants to limit visibility of the report to the sales and marketing groups in the most efficient manner.
Which approach should the consultant recommend?
- A. Add user filters from Tableau Server to each worksheet and select only sales and marketing user groups.
- B. Prepare a row-level security (RLS) entitlement table to define limitations of the access and use it to build user filters in the report's data source.
- C. Grant access to the report on the Tableau Server only to the members of sales and marketing user groups.
- D. Use user groups defined on Tableau Server to build user filters in the report's data source.
Answer: C
Explanation:
The most efficient way to limit report visibility to specific user groups on Tableau Server is to manage permissions directly on the server. By granting access to the report only to the sales and marketing user groups, the client ensures that only members of these groups can view the report. Thismethod is straightforward and does not require the additional steps involved in setting up row-level security or user filters.
References:The approach is supported by best practices in managing user permissions and visibility on Tableau Server, as described in the Tableau Community and official Tableau resources12.
NEW QUESTION # 28
A consultant builds a report where profit margin is calculated as SUM([Profit]) / SUM([Sales]). Three groups of users are organized on Tableau Server with the following levels of data access that they can be granted.
. Group 1: Viewers who cannot see any information on profitability
. Group 2: Viewers who can see profit and profit margin
. Group 3: Viewers who can see profit margin but not the value of profit Which approach should the consultant use to provide the required level of access?
- A. Use user filters to allow only Groups 2 and 3 access to data on profitability. Then, create a calculated field that limits visibility of profit value to Group 2 and use the calculation in the view in the report.
- B. Specify in the row-level security (RLS) entitlement table individuals who can see profit, profit margin, or none of these. Then, use the table data to create user filters in the report.
- C. Specify with user filters in each view individuals who can see profit, profit margin, or none of these.
- D. Use user filters to access data on profitability to all groups. Then, create a calculated field that allows visibility of profit value to Group 2 and use the calculation in the view in the report.
Answer: A
Explanation:
The approach of using user filters to control access to data on profitability for Groups 2 and 3, combined with a calculated field that restricts the visibility of profit value to only Group 2, aligns with Tableau's best practices for managing content permissions. This method ensures that each group sees only the data they are permitted to view, with Group 1 not seeing any profitability information, Group 2 seeing both profit and profit margin, and Group 3 seeing only the profit margin without the actual profit values.This setup can be achieved through Tableau Server's permission capabilities, which allow for detailed control over what each user or group can see and interact with12.
References:The solution is based on the capabilities and permission rules that are part of Tableau Server's security model, as detailed in the official Tableau documentation12. These resources provide guidance on how to set up user filters and calculated fields to manage data access levels effectively.
NEW QUESTION # 29
A client has a dashboard that uses a bar chart to visualize sales by Sub-Category and a detail table that has all the orders for the products within Sub- Category. The table has more than 10,000 rows of data and is slow to load.
A consultant plans to add an action so when the client interacts with the bar chart, only the relevant data appears in the table.
What will provide the fastest rendering of the dashboard?
- A. Add a highlight action and set Target Highlighting to All Fields.
- B. Add a filter action, set "Run action on" to Select, and set "Clearing the selection will" to Exclude all values.
- C. Add a filter action, set "Run action on" to Menu, and set "Clearing the selection will" to Show all values.
- D. Add a highlight action and set Target Highlighting to Sub-Category.
Answer: B
Explanation:
To optimize the dashboard rendering, particularly when dealing with a large dataset, a filter action is the most effective tool. Here's why the specified choice is optimal:
* Add a filter action: This action creates a direct filter on the detail table based on the selection in the bar chart. It ensures that only data related to the selected sub-category is loaded into the table, significantly reducing load time and improving performance.
* Set "Run action on" to Select: This setting means the filter action will be triggered as soon as the user selects a bar in the bar chart. Immediate activation of the filter ensures that the dashboard is interactive and responsive.
* Set "Clearing the selection will" to Exclude all values: When the selection is cleared, this setting ensures that no data is shown, which avoids loading the entire dataset unnecessarily. This maintains performance when no sub-category is actively selected.
ReferencesThis strategy follows Tableau's performance best practices by using actions to limit the amount of data processed and rendered, as detailed in the Tableau User Guide and training materials on Dashboard Actions for optimizing large datasets.
NEW QUESTION # 30
A client uses Tableau Data Management and notices that when they view a data source, they sometimes see a different count of workbooks in the Connected Workbooks tab compared to the lineage count in Tableau Catalog.
What is the cause of this discrepancy?
- A. Some workbooks have not been viewed by enough users yet.
- B. Some of the workbooks connected to the data source are not visible to the user due to permissions.
- C. Some workbooks have been connected to the data source, but do not use any fields from it.
- D. Some Creators have connected to the data source in Tableau Desktop but have not yet published a workbook.
Answer: B
Explanation:
The discrepancy between the count of workbooks in the Connected Workbooks tab and the lineage count in Tableau Catalog can occur because of user permissions. In Tableau Data Management, the visibility of connected workbooks is subject to the permissions set by administrators. If a user does not have permission to view certain workbooks, they will not see them listed in the Connected Workbooks tab, even though these workbooks are part of the data source's lineage and are counted in Tableau Catalog.
References:This explanation is based on the functionality of Tableau Data Management and Tableau Catalog, which includes managing user permissions and access to workbooks.The information is supported by Tableau's official documentation on data management and security practices1.
NEW QUESTION # 31
A client notices that several groups are sharing content across divisions and are not complying with their data governance strategy. During a Tableau Server audit, a consultant notices that the asset permissions for the client's top-level projects are set to "Locked," but that "Apply to Nested Projects" is not checked.
The consultant recommends checking "Apply to Nested Projects" to enforce compliance.
Which impact will the consultant's recommendation have on access to the existing nested projects?
- A. Users will be prompted to manually update permissions for all nested projects.
- B. Current custom access will be maintained, but new custom permissions will not be granted.
- C. Users will be notified that they will automatically lose access to content after 30 days.
- D. Access will be automatically rolled back to the top-level project permissions immediately.
Answer: D
Explanation:
When "Apply to Nested Projects" is checked in Tableau Server, the permission rules set at the top-level project are enforced for all assets in the project and all nested projects. This means that any custom access previously granted to nested projects will be overridden, and the permissions will revert to those defined at the top-level project. This action ensures consistent application of the data governance strategy across all divisions.
References:The impact of checking "Apply to Nested Projects" is detailed in Tableau's official documentation, which explains how locked nested projects can be used to govern site content with greater flexibility and efficiency12.
NEW QUESTION # 32
A client wants to count all the distinct orders placed in 2010. They have written the following calculation, but the result is incorrect.
IF YEAR([Date])=2010 THEN COUNTD ([OrderID]) END
Which calculation will produce the correct result?
- A. COUNTD(IF YEAR([Date])=2010 THEN [OrderID] END)
- B. IF YEAR([Date])=2010 THEN {COUNTD ([OrderID])} END
- C. COUNT(IF YEAR([Date])=2010 THEN [OrderID] END)
- D. IF MIN(YEAR([Date]))=2010 THEN WINDOW_COUNTD([OrderID]) END
Answer: A
Explanation:
The correct calculation to count all distinct orders placed in 2010 involves placing the conditional inside the aggregation function, not the other way around. Here's how to correct the client's calculation:
* Original Calculation Issue: The client's original calculation attempts to apply theCOUNTDfunction within anIFstatement, which does not work as expected because theCOUNTDfunction cannot conditionally count within the scope of theIFstatement.
* Correct Calculation:COUNTD(IF YEAR([Date]) = 2010 THEN [OrderID] END). This calculation checks each order date; if the year is 2010, it returns theOrderID. TheCOUNTDfunction then counts all uniqueOrderIDs that meet this condition.
* Why It Works: This method ensures that each order is first checked for the year condition before being counted, effectively filtering and counting in one step. It efficiently processes the data by focusing the distinct count operation only on relevant records.
ReferencesThis approach is consistent with Tableau's guidance on using conditional logic inside aggregation functions for accurate and efficient data calculations, as detailed in the Tableau User Guide under
"Aggregations and Calculations".
NEW QUESTION # 33
Use the following login credentials to sign in
to the virtual machine:
Username: Admin
Password:
The following information is for technical
support purposes only:
Lab Instance: 40201223
To access Tableau Help, you can open the
Help.pdf file on the desktop.
From the desktop, open the CC workbook.
Open the Categorical Sales worksheet.
You need to use table calculations to
compute the following:
. For each category and year, calculate
the average sales by segment.
. Create another calculation to
compute the year-over-year
percentage change of the average
sales by category calculation. Replace
the original measure with the year-
over-year percentage change in the
crosstab.
From the File menu in Tableau Desktop, click
Save.
Answer:
Explanation:
See the complete Steps below in Explanation:
Explanation:
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.
References:
* 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.
NEW QUESTION # 34
From the desktop, open the CC workbook.
Open the Incremental worksheet.
You need to add a line to the chart that
shows the cumulative percentage of sales
contributed by each product to the
incremental sales.
From the File menu in Tableau Desktop, click
Save.
Answer:
Explanation:
See the complete Steps below in Explanation:
Explanation:
To add a line showing the cumulative percentage of sales contributed by each product to the incremental sales in the Incremental worksheet of your Tableau Desktop, follow these detailed 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 Incremental worksheet by clicking on its tab at the bottom of the window.
* Calculate Cumulative Sales Percentage:
* Create a new calculated field to compute the cumulative percentage of sales. Right-click in the Data pane and select 'Create Calculated Field'.
* Name this field "Cumulative Sales Percentage".
* Enter the following formula to calculate the running sum of sales as a percentage of the total sales:
(RUNNING_SUM(SUM([Sales])) / TOTAL(SUM([Sales])) [Sales]))
* Click 'OK' to save the calculated field.
* Add the Cumulative Sales Percentage Line to the Chart:
* Drag the "Cumulative Sales Percentage" field to the Rows shelf, placing it next to the existing Sales measure.
* Ensure that the cumulative line appears as a continuous line. Right-click on the "Cumulative Sales Percentage" field on the Rows shelf, select 'Change Chart Type', and choose 'Line'.
* Adjust the axis to synchronize or dual-axis if necessary. Right-click on the axis of the
"Cumulative Sales Percentage" and select 'Synchronize Axis' if it's on a dual-axis setup.
* Format the Cumulative Sales Percentage Line:
* Click on the "Cumulative Sales Percentage" line in the visualization.
* Navigate to the 'Format' pane to adjust the line style, thickness, and color to make it distinct from other data in the chart.
* Save Your Changes:
* From the File menu, click 'Save' to ensure all your changes are stored.
References:
* Tableau Help: Provides additional details on creating calculated fields and customizing line charts.
* Tableau User Guide: Offers extensive instructions on formatting charts, including line types and axis synchronization.
By following these steps, you will successfully add a cumulative sales percentage line to your chart, enhancing the visualization to reflect the incremental contribution of each product to the overall sales in a dynamic and informative manner.
NEW QUESTION # 35
A client wants to flag orders that have sales higher than the regional average.
Which calculated field will produce the required result?
- A. { FIXED [Order ID] : SUM([Sales]) }
>
{ FIXED [Region] : SUM([Sales]) } - B. { FIXED [Order ID] : SUM([Sales]) }
>
{ FIXED [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) } - C. { FIXED [Order ID] : SUM([Sales]) }
>
{ INCLUDE [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) } - D. [Sales]
>
{ FIXED [Order ID] : SUM([Sales]) }
Answer: B
Explanation:
To flag orders with sales higher than the regional average, the correct calculated field would compare the sum of sales for each order against the average sales of all orders within the same region:
* Correct Formula:{ FIXED [Order ID] : SUM([Sales]) } > { FIXED [Region] : AVG({ FIXED
[Order ID] : SUM([Sales]) }) }
* This calculation uses a Level of Detail (LOD) expression:
* The left part of the formula{ FIXED [Order ID] : SUM([Sales]) }calculates the total sales for each individual order.
* The right part{ FIXED [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) }calculates the average sales per order within each region.
* The>operator is used to compare these two values to determine if the sales for each order exceed the regional average.
ReferencesThis formula utilizes Tableau's LOD expressions to perform complex comparisons across different dimensions of the data, as explained in Tableau's official training materials on LOD calculations.
NEW QUESTION # 36
A client is using Tableau to visualize data by leveraging security token-based credentials. Suddenly, sales representatives in the field are reporting that they cannot access the necessary workbooks. The client cannot recreate the error from their offices, but they have seen screenshots from the field agents. The client wants to restore functionality for the field agents with minimal disruption.
Which step should the consultant recommend to accomplish the client's goal?
- A. Ask the workbook owners to republish the workbooks to refresh the security token.
- B. Ensure that "Allow Refresh Access" was checked when the data source was published.
- C. Renew the security token via the Data Connection on Tableau Server.
- D. Change the data source permissions for the connection to "Prompt User."
Answer: C
Explanation:
When field agents are unable to access workbooks due to issues with security token-based credentials, the most immediate and least disruptive solution is to renew the security token. This can be done through the Data Connection settings on Tableau Server. Renewing the token will restore access for the field agents without requiring them to take any action or affecting other users.
References:The use of personal access tokens (PATs) in Tableau and the procedure for renewing them are documented in Tableau's official resources.It is noted that PATs are long-lived authentication tokens that can be revoked and renewed to manage access securely1.Additionally, there have been discussions in the Tableau Community regarding issues with concurrent PAT access, which further supports the need to manage tokens effectively2.
NEW QUESTION # 37
A client has a published data source in Tableau Server and they want to revert to the previous version of the data source. The solution must minimize the impact on users.
What should the consultant do to accomplish this task?
- A. Select a previous version from Tableau Server, download it, and republish that data source.
- B. Select a previous version from Tableau Server, and then click Restore.
- C. Request that a server administrator restore a Tableau Server backup.
- D. Delete and recreate the data source manually.
Answer: B
Explanation:
To minimize the impact on users when reverting to a previous version of a published data source in Tableau Server, the consultant should use the built-in revision history feature. By selecting a previous version from the revision history and clicking 'Restore', the data source will revert to that version without the need for a full server backup restoration or manual recreation of the data source. This process is quick and has the least amount of disruption to users.
References:The functionality and process for reverting to a previous version of a data source are outlined in Tableau's official documentation on working with content revisions1.This feature is part of Tableau Server's capabilities to manage and maintain data sources effectively21.
NEW QUESTION # 38
A Tableau Cloud client has requested a custom dashboard to help track which data sources are used most frequently in dashboards across their site.
Which two actions should the client use to access the necessary metadata? Choose two.
- A. Download metadata through Tableau Catalog.
- B. Access metadata through the Metadata API.
- C. Connect directly to the Site Content data source within the Admin Insights project.
- D. Query metadata through the GraphiQL engine.
Answer: B,D
Explanation:
To track which data sources are used most frequently across a site in Tableau Cloud, the client should use the GraphiQL engine and the Metadata API.The GraphiQL engine allows for interactive exploration of the metadata, making it easier to construct and test queries1.The Metadata API provides access to metadata and lineage of external assets used by the content published to Tableau Cloud, which is essential for tracking data source usage2.
References:The actions are based on the capabilities of the GraphiQL engine and the Metadata API as described in Tableau's official documentation and learning resources321.
NEW QUESTION # 39
......
Free TCC-C01 Exam Files Downloaded Instantly 100% Dumps & Practice Exam: https://www.passexamdumps.com/TCC-C01-valid-exam-dumps.html
Sep-2024 Pass Tableau TCC-C01 Exam in First Attempt Easily: https://drive.google.com/open?id=1dtLXiTqBwlM7TXrisq7ON6YCwcAwSx50
