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. Add the [Profit] filter to the context.
• B. Filter with a table calculation WINDOW_AVG(MIN([Profit]), first(), last())
• C. Filter with the table calculation used to create labels.
• D. Use a calculation with TOTAL() function instead of a quick table calculation.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

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. Integers are fastest, followed by Booleans, and then strings.
• C. Strings, integers, and Booleans all perform the same.
• D. Booleans are fastest, followed by integers, and then strings.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

From the desktop, open the CCworkbook. Use the US PopulationEstimates data source.
You need to shape the data in USPopulation Estimates by using TableauDesktop. The data must be formatted asshown in the following table.

Open the Population worksheet. Enterthe total number of records contained inthe data set into the Total Recordsparameter.
From the File menu in Tableau Desktop,click Save.

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 formulaCOUNT([Record ID])orSUM([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.

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] : AVG({ FIXED [Order ID] : SUM([Sales]) }) }
• B. [Sales]
  >
  { FIXED [Order ID] : SUM([Sales]) }
• C. { FIXED [Order ID] : SUM([Sales]) }
  >
  { FIXED [Region] : SUM([Sales]) }
• D. { FIXED [Order ID] : SUM([Sales]) }
  >
  { INCLUDE [Region] : AVG({ FIXED [Order ID] : SUM([Sales]) }) }

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

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 ('month', DATEADD ('month', 1, [Order Date]))
  Calc2: AVG(DATEDIFF ('day', [Order Date], [Calc1]))
• B. Calc1: DATETRUNC ('day', DATEADD ('day', 31, [Order Date]))
  Calc2: AVG ([Order Date] - [Calc1])
• C. Calc1: DATETRUNC ('day', DATEADD('week', 4, [Order Date]))
  Calc2: AVG([Order Date] - [Calc1])
• D. Calc1: DATETRUNC ('month', DATEADD('month', 1, [Order Date]))
  Calc2: AVG(DATEDIFF ('week', [Order Date], [Calc1]))

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).