2026 Analytics-Con-301 dumps review - Professional Quiz Study Materials
Analytics-Con-301 Test Prep Training Practice Exam Questions Practice Tests
NEW QUESTION # 34
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. The Split option
- B. A calculated field that uses the TRIM function
- C. A calculated field that uses the LEFT function
- D. The Aliases option
Answer: A
Explanation:
To transform the Orderld field 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 the Orderld field 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 the Orderld into 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 original Orderld into the desired components without manual specification of conditions or writing any formulas.
References
This 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 # 35
SIMULATION
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 # 36
A consultant is working with a Tableau Server customer. The customer asks the consultant if there is a need to upgrade their instance of Tableau Server that was installed over 1 year ago.
Which two situations justify the need for an upgrade? Choose two.
- A. The need to access new features and improvements from Tableau Cloud
- B. The security team has a report of bugs and security vulnerabilities in older versions of Tableau
- C. Compatibility with newer Tableau Desktop and Prep Builder versions that users might want to install
- D. Users are complaining of performance; the upgrade will reduce the server's hardware requirements
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau's upgrade guidance identifies two major drivers for upgrading Tableau Server:
* Version Compatibility with Tableau Desktop and Tableau Prep Builder
* Tableau Server must be equal to or newer than the version used by Desktop and Prep Builder for publishing.
* Organizations upgrading Desktop often must upgrade Server to avoid compatibility issues.
* This is a core reason to update a year-old installation.
* Security and Bug Fixes
* Tableau regularly publishes security patches, bug fixes, and stability enhancements.
* Older versions accumulate unresolved security issues that may be identified by security teams.
* Tableau explicitly states that upgrading ensures the instance receives the latest security protections.
Option B is incorrect because upgrading does not reduce hardware requirements; in many cases hardware needs may increase.
Option C is incorrect because Tableau Cloud features do not require upgrading Tableau Server. Tableau Cloud enhancements are independent of Server versions.
Therefore, the two conditions that justify upgrading are maintaining compatibility and addressing security vulnerabilities.
* Tableau's version compatibility matrix requiring alignment between Tableau Server and Desktop/Prep.
* Upgrade planning documents emphasizing security patches and bug fixes as key upgrade drivers.
* Notes describing that performance complaints alone are not solved simply by upgrading.
NEW QUESTION # 37
A client has a database that stores widget inventory by day and it is updated on a nonstandard schedule as shown below.
They want a data visualization that shows widget inventory daily, however their business unit does not have the ability to modify the data warehouse structure.
What should the client do to achieve the desired result?
- A. Update the Widget Inventory Table to be a daily snapshot.
- B. Use Tableau Prep to add new rows.
- C. Create a temporary table in the database.
- D. Use Tableau Desktop to visualize null values.
Answer: B
Explanation:
For a client who needs a daily visualization of widget inventory but cannot modify the data warehouse structure, the best approach is to use Tableau Prep to add new rows. Tableau Prep can be used to manipulate the existing dataset by adding missing date entries and appropriately adjusting inventory counts based on available data. This allows the creation of a complete daily snapshot for visualization without needing changes to the underlying database structure.
NEW QUESTION # 38
A client has a dashboard that renders in less than 10 seconds. The client receives a request to add a new calculated field that will return TRUE if a Project contains any one of the values "Project 1" or "Project 2" and FALSE otherwise. After adding the function found below, the dashboard's render time increases to 14 seconds from 10 seconds.
[Project] = 'Project 1' OR [Project] = 'Project 2'
Which function should the consultant use to reduce the render time?
- A. (([Project] = 'Project 1') OR ([Project] = 'Project 2'))
- B. [Project] IN ('Project 1', 'Project 2')
- C. [Project] = 'Project 1' AND [Project] = 'Project 2'
- D. [Project] IN ('Project 1' OR 'Project 2')
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau documentation states that IN expressions are optimized internally for better query performance than multiple OR statements. They are pushed efficiently to the data source and simplified during query compilation.
The original expression uses two OR conditions, which increases the complexity of row-level evaluation:
[Project] = 'Project 1' OR [Project] = 'Project 2'
Tableau's performance guidelines recommend replacing multiple OR comparisons with an IN expression whenever possible:
[Project] IN ('Project 1', 'Project 2')
This reduces rendering time by minimizing row evaluation overhead and creating a cleaner, optimized logical condition.
Option D achieves this exactly.
Option A is logically incorrect because a project cannot simultaneously equal both values.
Option B is syntactically incorrect because IN expects a list, not an OR inside the list.
Option C is simply a reformatting of the original OR expression and provides no performance improvement.
Option D is the only valid, optimized solution.
* Tableau calculation optimization guidance recommending IN over OR for performance.
* Tableau's query performance notes indicating that OR statements expand logical branches and slow down evaluation.
* Best practices for row-level calculations suggesting simplified logical expressions.
NEW QUESTION # 39
A client wants to see data for only the last day in a dataset and the last day is always yesterday. The date is represented with the field Ship Date.
The client is not concerned about the daily refresh results. The volume of data is so large that performance is their priority. In the future, the client will be able to move the calculation to the underlying database, but not at this time.
The solution should offer the best performance.
Which approach should the consultant use to produce the desired results?
- A. Filter MONTH/DAY/YEAR on [Ship Date] field and use an option to filter to the latest date value when the workbook opens.
- B. Filter on calculation [Ship Date]=TODAY()-1.
- C. Filter on Ship Date field using the Yesterday option.
- D. Filter on calculation [Ship Date]={MAX([Ship Date])}.
Answer: B
Explanation:
The best approach to ensure performance while providing data for only the last day (yesterday) in the dataset is to use a calculated field that filters the data to include only yesterday's date:
Filter on calculation [Ship Date]=TODAY()-1: This calculated field dynamically computes yesterday's date by subtracting one day from today's date. This approach ensures that each day, only the data for the previous day is loaded, which keeps the volume of data minimal and improves performance.
Dynamic Date Calculation: The use of TODAY()-1 ensures the filter remains up-to-date with the changing dates, without the need for manual updates, providing accuracy and timeliness in the dashboard.
This approach is efficient because it avoids the overhead of processing the entire dataset and focuses only on the relevant day's data. It also aligns with Tableau's capabilities for creating dynamic filters using date functions, as highlighted in the Tableau help documentation on date calculations and filters.
References
This solution utilizes Tableau's built-in date functions and dynamic calculations to optimize performance, as recommended in Tableau's performance optimization resources and date calculation guidelines.
NEW QUESTION # 40
A client collects information about a web browser customers use to access their website. They then visualize the breakdown of web traffic by browser version.
The data is stored in the format shown below in the related table, with a NULL BrowserID stored in the Site Visitor Table if an unknown browser version accesses their website.
The client uses "Some Records Match" for the Referential Integrity setting because a match is not guaranteed. The client wants to improve the performance of the dashboard while also getting an accurate count of site visitors.
Which modifications to the data tables and join should the consultant recommend?
- A. Add an "Unknown" option to the Browser Table, reference its BrowserID in the Site Visitor Table, and leave the Referential Integrity set to
"Some Records Match." - B. Add an "Unknown" option to the Browser Table, reference its BrowserID in the Site Visitor Table, and change the Referential Integrity to "All Records Match."
- C. Continue to use NULL as the BrowserID in the Site Visitor Table and leave the Referential Integrity set to "Some Records Match."
- D. Continue to use NULL as the BrowserID in the Site Visitor Table and change the Referential Integrity to "All Records Match."
Answer: B
Explanation:
To improve the performance of a Tableau dashboard while maintaining accurate counts, particularly when dealing with unknown or NULL BrowserIDs in the data tables, the following steps are recommended:
Modify the Browser Table: Add a new row to the Browser Table labeled "Unknown," assigning it a unique BrowserID, e.g., 0 or 4.
Update the Site Visitor Table: Replace all NULL BrowserID entries with the BrowserID assigned to the "Unknown" entry. This ensures every record in the Site Visitor Table has a valid BrowserID that corresponds to an entry in the Browser Table.
Change Referential Integrity Setting: Change the Referential Integrity setting from "Some Records Match" to "All Records Match." This change assumes all records in the primary table have corresponding records in the secondary table, which improves query performance by allowing Tableau to make optimizations based on this assumption.
References:
Handling NULL Values: Replacing NULL values with a valid unknown option ensures that all data is included in the analysis, and integrity between tables is maintained, thereby optimizing the performance and accuracy of the dashboard.
NEW QUESTION # 41
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. 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.
- D. Specify with user filters in each view individuals who can see profit, profit margin, or none of these.
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 # 42
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. Booleans are fastest, followed by integers, and then strings.
- B. Integers are fastest, followed by Booleans, and then strings.
- C. Strings are fastest, followed by integers, and then Booleans.
- D. Strings, integers, and Booleans all perform the same.
Answer: B
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 # 43
A worksheet uses a LOOKUP function to display Sales by Month, Year of Order Date, and sales from the last
12 months. A consultant wants to use a Relative Date Filter to filter for data from the last 12 months.
However, when the consultant does this, the prior year's data is removed from the sheet.
Which two actions should the consultant take to retain the prior year's data after applying the filter? Choose two.
- A. Set the Relative Date filter as a Context Filter instead of Measure Filter.
- B. Replace the LOOKUP function with a FIXED Level of Detail (LOD) expression.
- C. Create the following calculation: DATEDIFF('month', [Order Date], {MAX([Order Date])}) < 12. Hide all False values.
- D. Create the following calculation: LOOKUP(MIN([Order Date]),0). Filter on that calculation instead of Order Date.
Answer: A,D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
A LOOKUP table calculation requires access to rows outside the filtered date range so that the calculation can reference prior data. When a Relative Date Filter removes older data before the table calculation is evaluated, the LOOKUP loses the needed rows, causing the prior year's data to disappear.
Tableau's order of operations states:
* Relative Date Filters act early (at the dimension filter stage).
* Table calculations act very late.
* To preserve table calculation context, filters must not remove necessary rows.
Two Tableau-documented approaches address this:
Explanation for B
Setting the Relative Date Filter as a Context Filter allows table calculations to operate on the full dataset needed for LOOKUP. Context filters create a separate temporary table, and subsequent filters like table calculations evaluate after the context is established.
This ensures older rows are still available to the LOOKUP function.
Explanation for C
Creating a field such as:
LOOKUP(MIN([Order Date]), 0)
and filtering on this field instead of Order Date converts the filter into a table calculation filter, which occurs after the LOOKUP computation. Tableau documentation explains that table calculation filters preserve the full dataset required for the LOOKUP window.
This ensures that the LOOKUP still has access to last year's values even when filtering for the current 12 months.
Why A is incorrect
Replacing LOOKUP with an LOD changes the logic entirely.
LOD expressions cannot replicate moving-window or lag-type behavior.
Why D is incorrect
DATEDIFF logic can replicate a rolling window, but hiding False values is essentially a manual filter and does not preserve the integrity of the LOOKUP's required partitioning. It also contradicts Tableau's recommended approach for maintaining table calculation context.
* Tableau Order of Operations explaining why table calculation filters preserve data for LOOKUP.
* Tableau documentation on context filters and how they allow more data to remain available for downstream table calculations.
* Tableau guidance on how Relative Date Filters interact with table calculations.
* Best practices for preserving table calculation window rows when filtering.
NEW QUESTION # 44
A client's fiscal calendar runs from February 1 through January 31.
How should the consultant configure Tableau to use the client's fiscal calendar when building date charts?
- A. Create Calculated Fields using the FISCALQUARTER() and FISCALYEAR() functions.
- B. Edit the data source and set the Fiscal Year in the data preview window.
- C. Right click on the Date axis in charts and select Use Fiscal Calendar.
- D. Edit the data source Date Properties, then update the Default Properties of the Date Fields.
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau allows fiscal calendars to be defined at the data source level, affecting how all date fields behave across the workbook.
According to Tableau documentation:
* Fiscal calendars must be set using Data Source Date Properties.
* Once set, this becomes a default property for all date fields unless overridden.
* This allows charts, hierarchies, and date parts to automatically follow the fiscal year starting in February.
Correct procedure:
* Go to Data Source.
* Open Date Properties.
* Set Fiscal Year Start = February.
* (Optional) Adjust Date Field Default Properties.
This ensures all charts and date hierarchies use the fiscal calendar automatically.
Why the other options are incorrect:
A). Right-click on axis # Use Fiscal Calendar
This option does not exist in Tableau.
B). Set Fiscal Year in Data Preview
Not supported; fiscal configuration isn't made in the preview window.
C). Use FISCALYEAR() / FISCALQUARTER()
This is manual, requires custom fields, and does not configure Tableau's built-in fiscal calendar system.
This is more work and not the correct method.
Only Option D configures the fiscal calendar globally and correctly.
* Tableau Date Properties documentation specifying fiscal year settings.
* Default Properties configuration for date fields.
* Official guidance for implementing fiscal calendars.
NEW QUESTION # 45
A consultant wants to improve the performance of reports by moving calculations to the data layer and materializing them in the extract.
Which type of calculation is the consultant able to move?
- A. A row-level calculation
- B. A calculation that contains parameters
- C. A calculation that contains table calculation functions
- D. A calculation that contains an aggregation
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau allows certain calculations to be materialized in extracts, meaning they are precomputed and stored inside the .hyper file to improve performance.
According to Tableau's extract documentation:
* Materializable calculations must be compatible with the extract engine and must not depend on dynamic, view-based, or post-query logic.
* Only row-level calculations and aggregation-level calculations without dependencies on runtime context can be materialized.
* Tableau cannot materialize any calculation containing:
* Table calculation functions
* Functions requiring post-aggregation logic
* View-dependent elements
* Parameters that need runtime evaluation
Evaluation of the choices:
A). A row-level calculation - Correct
Row-level calculations operate on each record individually before aggregation.
Tableau documentation specifies that these calculations can be pushed down into the extract and materialized because they do not depend on the visualization or user interaction.
Examples include concatenation, arithmetic, string manipulation, and row-based logic such as:
[Sales] * [Quantity] or IF [Region] = 'West' THEN 1 END
These can be precomputed inside the extract, improving performance.
B). A calculation that contains table calculation functions - Not allowed Table calculations (WINDOW_SUM, INDEX, RUNNING_SUM, RANK, etc.) depend on the table structure after aggregation and query execution.
Therefore, Tableau documentation states they cannot be materialized in extracts.
C). A calculation that contains parameters - Not allowed
Parameters are evaluated at runtime, meaning the user can change their value.
Because of this, Tableau cannot permanently compute and store such a calculation inside an extract.
D). A calculation that contains an aggregation - Generally not materialized Aggregated calculations often depend on query context and cannot always be materialized.
Only simple, context-free aggregations might be materialized, but Tableau explicitly warns that aggregations are not guaranteed candidates for extract materialization.
Thus, this is not the best answer compared to row-level logic.
Conclusion
Only row-level calculations meet Tableau's exact requirements for materialization in extracts.
References From Tableau Consultant Documentation
* Tableau Extract documentation describing materializable calculation types.
* Tableau guidance stating table calculations and parameter-dependent calculations cannot be materialized.
* Extract optimization guidelines describing row-level logic as eligible for materialization.
NEW QUESTION # 46
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 Then 'Highly Profitable'
ELSEIF [ProfitMargin]>=0 Then 'Profitable'
ELSE 'Unprofitable'
END - C. IF([ProfitMargin]>=0.50,'Highly Profitable', 'Profitable')
ELSE 'Unprofitable'
END - D. IF [ProfitMargin]>0.50 Then 'Highly Profitable'
ELSEIF [ProfitMargin]>=0 Then 'Profitable'
ELSEIF [ProfitMargin] <0 Then 'Unprofitable'
END
Answer: B
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 # 47
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. Use join option to combine/merge all the files together before doing the data transformation (calculations).
- D. Apply the data transformation (calculations) in each require file and do the join to combine/merge before designing the visuals.
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 # 48
A client is searching for ways to curate and document data in order to obtain data lineage. The client has a data source connected to a data lake.
Which tool should the consultant recommend to meet the client's requirements?
- A. Tableau Catalog without Tableau Data Management Add-on
- B. Tableau Catalog with Tableau Data Management Add-on
- C. Tableau Catalog with Tableau Server Management Add-on
- D. Tableau Prep Conductor
Answer: B
Explanation:
To effectively curate and document data for obtaining data lineage, particularly from a data source connected to a data lake, the recommended tool is:
Tableau Catalog with Tableau Data Management Add-on: This add-on enhances the capabilities of Tableau Catalog, providing extensive features for data management, including detailed data lineage, impact analysis, and metadata management.
Functionality: The Tableau Catalog with the Data Management Add-on allows users to see the full history and lineage of the data, trace its usage across all Tableau content, and understand dependencies. It also facilitates better governance and transparency in data handling.
Why Choose this Tool: For a client needing comprehensive data lineage and documentation capabilities, this add-on ensures that data stewards and users can maintain and utilize a well-managed data environment. It supports robust data governance practices necessary for large and complex data ecosystems like those typically associated with data lakes.
References
The recommendation is based on the functionalities offered by the Tableau Data Management Add-on, as described in Tableau's official documentation on managing and documenting data sources for enhanced governance and operational efficiency.
NEW QUESTION # 49
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. Grant access to the report on the Tableau Server only to the members of sales and marketing user groups.
- B. Add user filters from Tableau Server to each worksheet and select only sales and marketing user groups.
- C. 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.
- D. Use user groups defined on Tableau Server to build user filters in the report's data source.
Answer: A
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. This method 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 # 50
A business analyst is creating a view of the top 10 customers for each region. The analyst has set a "Top 10" filter on Customer Name. However, it did not display the top 10 customers per region, as shown in the image below.
Which type of filter should the business analyst add to filter for region?
- A. Table Calculation filter
- B. Dimension filter
- C. Extract filter
- D. Context filter
Answer: D
Explanation:
The issue occurs because of Tableau's Order of Operations.
Key Tableau logic:
* Top N filters are a type of Dimension filter.
* Dimension filters are evaluated after Context filters.
* When you place Region on Filters (as a standard dimension filter), Tableau:
* First applies the Customer Name Top 10 filter across the entire data set, not per region.
* Then limits the view to the selected region(s).
* This results in seeing the global Top 10 customers, not the Top 10 per region.
How to fix it:
To force Tableau to compute Top 10 customers within each region, the Region filter must be applied before the Top N Customer filter.
This is done by making Region a Context Filter.
Effect of a Context Filter:
* Context filters are executed before the Top N filter.
* Region becomes the context.
* Tableau then evaluates the Top 10 customers inside each region's subset of data.
This produces the correct "Top 10 customers per region".
Why the other options are incorrect:
A). Extract filter
Applies once when creating the extract; does not control Top N logic inside the workbook.
B). Dimension filter
This is what the analyst already has - and it causes the unwanted behavior because it happens after the Top N filter.
C). Table Calculation filter
Top N is not a table calculation; table calc filters cannot fix this problem.
Only the Context Filter changes the execution order so Top N works per region.
* Tableau Order of Operations showing Context Filters applied before Top N filters.
* Best practices recommending Context Filters when Top N must be computed within subcategories.
* Filtering documentation explaining that Top N filters require context when additional dimensional filters are present.
NEW QUESTION # 51
A client wants to view stores serviced by delivery drivers on a map. The have the information provided in the table below:
What does the client need to do to plot exact street addresses on the map?
- A. Establish a hierarchy of State > City > Street Address 1 > Street Address 2.
- B. Custom geocode the street addresses.
- C. Change the data type of Street Address 1 and Street Address 2 to the Geographic role.
- D. Add a Map layer to the visualization.
Answer: B
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.
NEW QUESTION # 52
SIMULATION
From the desktop, open the CC workbook.
Open the Manufacturers worksheet.
The Manufacturers worksheet is used to
analyze the quantity of items contributed by
each manufacturer.
You need to modify the Percent
Contribution calculated field to use a Level
of Detail (LOD) expression that calculates
the percentage contribution of each
manufacturer to the total quantity.
Enter the percentage for Newell to the
nearest hundredth of a percent into the
Newell % Contribution parameter.
From the File menu in Tableau Desktop, click
Save.
Answer:
Explanation:
See the complete Steps below in Explanation
Explanation:
To modify the Percent Contribution calculated field to use a Level of Detail (LOD) expression and accurately calculate the percentage contribution of each manufacturer to the total quantity, follow these steps:
Open the CC Workbook and Access the Worksheet:
Double-click on the CC workbook from the desktop to open it in Tableau Desktop.
Navigate to the Manufacturers worksheet by selecting its tab at the bottom of the window.
Modify the Percent Contribution Calculated Field:
Navigate to the Data pane and find the "Percent Contribution" calculated field.
Right-click on the "Percent Contribution" field and select 'Edit'.
Modify the formula to incorporate an LOD expression that calculates the total quantity across all manufacturers and the specific quantity per manufacturer:
{FIXED [Manufacturer]: SUM([Quantity])} / {SUM([Quantity])}Quantity])}
This formula uses {FIXED [Manufacturer]: SUM([Quantity])} to compute the total quantity contributed by each manufacturer, regardless of other dimensions in the view. The total quantity {SUM([Quantity])} calculates the grand total across all manufacturers. The division calculates the percentage contribution.
Click 'OK' to save the updated calculated field.
Enter Percentage for Newell:
With the updated "Percent Contribution" field, drag it onto the view to update the chart or table.
Identify the value corresponding to 'Newell' in the updated visualization.
Round this value to the nearest hundredth of a percent as required.
Enter this value into the "Newell % Contribution" parameter. To do this, locate the parameter in the Data pane or on the dashboard, right-click it, and choose 'Edit'. Enter the calculated percentage for Newell.
Save Your Changes:
From the File menu, click 'Save' to store all the modifications you have made to the workbook.
References:
Tableau Help: Offers detailed guidance on using LOD expressions for precise and context-independent aggregations.
Tableau Desktop User Guide: Provides comprehensive instructions on managing calculated fields and parameters, ensuring accurate data analysis.
By following these steps, you will have successfully updated the calculation for percent contribution using LOD expressions, providing a more accurate analysis of each manufacturer's contribution to the total quantity. Moreover, updating the parameter with Newell's specific contribution rounds out the task by reflecting precise data inputs for reporting or further analysis.
NEW QUESTION # 53
A client has a data source that stores a time stamp for each time a user interacts with a product feature. They visualize 3 years of data at the daily level. As adoption has grown over the last 6 months, the dashboard performance has steadily decreased, despite connecting via a data extract that is set to refresh every hour.
A Tableau consultant needs to improve performance of the dashboard with the least impact to the visualization.
Which option meets these requirements without additional cost?
- A. Leverage Tableau Prep to aggregate the data to the daily product level.
- B. Decrease the extract refresh to once a day.
- C. Invest in an extract, transform, load (ETL) tool to aggregate the data to a daily level.
- D. Add extract filters to limit the number of product features visualized.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The dataset contains timestamps for each individual user interaction. Growth in user adoption over 6 months means the number of rows has expanded significantly. Tableau's performance documentation states that large row-level datasets can cause performance degradation even when using extracts, especially when:
* The visualization is aggregated to a higher level (such as daily), and
* The underlying extract still contains much more granular data than needed.
Tableau recommends pre-aggregating data before it reaches Tableau Desktop, which reduces extract size, memory use, and query time. This improves performance without changing what the visualization displays.
Option D uses Tableau Prep, which is included with Tableau Creator licensing and therefore incurs no additional cost. Tableau Prep can aggregate raw timestamp data into daily totals per product feature, which matches the visualization's actual granularity. This results in:
* A dramatically smaller extract
* Faster queries
* No change to how the dashboard looks or functions
Option A would remove product features from the visualization, altering the dashboard content and reducing insight, which does not meet the requirement of minimal impact.
Option B requires purchasing an external ETL tool, which violates the requirement of no additional cost.
Option C reduces the number of extract refreshes but does not improve dashboard performance; the data would remain equally granular and equally slow.
Therefore, Tableau Prep aggregation is the correct solution that improves performance while maintaining the same visualization and incurring no additional cost.
* Tableau performance guidelines recommending pre-aggregation of highly granular datasets.
* Tableau Prep documentation stating it can be used to aggregate data before creation of extracts.
* Tableau's extract optimization guidance describing how reducing row counts improves query and visualization performance.
NEW QUESTION # 54
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 Data Source Filter instead of a Dimension Filter.
- B. Create an aggregate expression, and then use that instead of the table calculation.
- C. Filter Category by using a Context Filter instead of a Dimension Filter.
- D. Create a FIXED Level of Detail (LOD) expression, and then use that instead of the table calculation.
Answer: D
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 # 55
A client collects information about a web browser customers use to access their website. They then visualize the breakdown of web traffic by browser version.
The data is stored in the format shown below in the related table, with a NULL BrowserID stored in the Site Visitor Table if an unknown browser version accesses their website.
The client uses "Some Records Match" for the Referential Integrity setting because a match is not guaranteed.
The client wants to improve the performance of
the dashboard while also getting an accurate count of site visitors.
Which modifications to the data tables and join should the consultant recommend?
- A. Add an "Unknown" option to the Browser Table, reference its BrowserID in the Site Visitor Table, and leave the Referential Integrity set to
"Some Records Match." - B. Add an "Unknown" option to the Browser Table, reference its BrowserID in the Site Visitor Table, and change the Referential Integrity to "All Records Match."
- C. Continue to use NULL as the BrowserID in the Site Visitor Table and leave the Referential Integrity set to "Some Records Match."
- D. Continue to use NULL as the BrowserID in the Site Visitor Table and change the Referential Integrity to "All Records Match."
Answer: B
Explanation:
To improve the performance of a Tableau dashboard while maintaining accurate counts, particularly when dealing with unknown or NULL BrowserIDs in the data tables, the following steps are recommended:
* Modify the Browser Table: Add a new row to the Browser Table labeled "Unknown," assigning it a unique BrowserID, e.g., 0 or 4.
* Update the Site Visitor Table: Replace all NULL BrowserID entries with the BrowserID assigned to the "Unknown" entry. This ensures every record in the Site Visitor Table has a valid BrowserID that corresponds to an entry in the Browser Table.
* Change Referential Integrity Setting: Change the Referential Integrity setting from "Some Records Match" to "All Records Match." This change assumes all records in the primary table have corresponding records in the secondary table, which improves query performance by allowing Tableau to make optimizations based on this assumption.
References:
Handling NULL Values: Replacing NULL values with a valid unknown option ensures that all data is included in the analysis, and integrity between tables is maintained, thereby optimizing the performance and accuracy of the dashboard.
NEW QUESTION # 56
A Tableau consultant is tasked with choosing a method of setting up row-level security (RLS) entitlements with tables during a Tableau implementation. The consultant has received a set of roles from a client in one normalized table, and a set of entitlements from the client in another normalized table.
The consultant plans on using the deepest granularity method. However, when the consultant gains access to the final set of data, they discover duplicate values at the lowest level. Most of the regions in the client's dataset contain sub-regions named 'East' and 'West'. However, some regions have a 'Null' value for sub-region.
How should the consultant proceed?
- A. Use sparse entitlements because it defines entitlements at every level of the hierarchy and can handle duplicate values in the dataset.
- B. Use sparse entitlements because it is the most performant and the duplicate values will be handled by the mapping table.
- C. Use the deepest granularity method because it defines entitlements at every level of the hierarchy and can handle duplicate values in the dataset.
- D. Use the deepest granularity method because it is the most performant and the duplicate values will be handled by the mapping table.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau's RLS entitlement design patterns include:
1. Deepest Granularity Method
* Requires one unique role # one unique lowest-level value pairing.
* Fails when the dataset contains duplicate lowest-level values (e.g., multiple "East" sub-regions across different regions).
* Cannot operate correctly when some lowest-level values are NULL.
Thus, the deepest granularity method is not valid here.
2. Sparse Entitlements Method
Tableau documentation states:
* Sparse entitlements define RLS at each level of the hierarchy instead of only at the lowest level.
* This method supports duplicate lowest-level values.
* Handles scenarios where some levels are NULL because higher-level entitlements (e.g. Region = AMER) can still correctly apply.
* More flexible for hierarchical geographic structures (Region # Sub-Region # Country, etc.).
Given the client's dataset:
* Multiple "East" and "West" sub-regions
* Some "Null" sub-regions
* Hierarchical levels present
Sparse entitlements is the only correct and supported choice.
Why the incorrect options are wrong:
A & B - Deepest Granularity
* Deepest granularity fails when the lowest-level values are not unique.
* It cannot handle NULL values at the lowest tier.
* Performance is not superior in this scenario.
D - Sparse because it is most performant
Performance is not the defining advantage.
Flexibility and ability to handle duplicate lowest-level values is.
Thus, C is the correct statement.
* RLS entitlement design patterns: deepest vs. sparse entitlements.
* Rules requiring unique lowest-level identifiers for deepest granularity.
* Guidance stating sparse entitlements should be used when duplicates or NULL values exist in hierarchical structures.
NEW QUESTION # 57
A data analyst sets up a calculation to filter a dashboard so that it displays only the users' information. The dashboard will then be published to Tableau Cloud.
The data analyst plans to use the following calculation to filter the data: USERNAME() = [Correct Answer] Which column in the table below should the data analyst reference in the calculation?
- A. Lower case Name
- B. Email
- C. Abbreviated Name
Answer: B
Explanation:
When dashboards are published to Tableau Cloud, the function USERNAME() returns the user's Tableau Cloud username, which is the email address associated with their Tableau Cloud account.
Tableau documentation states:
* On Tableau Cloud, the value returned by USERNAME() is always the user's email address.
* Row-Level Security (RLS) is typically implemented using a comparison of USERNAME() to an email field in the data source.
* For secure filtering, the field compared to USERNAME() must match the authentication identity exactly.
Looking at the provided table:
* "Abbreviated Name" contains short custom codes like "SMiller," which do not match Tableau Cloud usernames.
* "Lower Case Name" contains names like "sean miller," which also do not match Tableau Cloud usernames.
* "Email" contains the full email address for each user, such as "[email protected]," which is the only field that corresponds to what USERNAME() returns in Tableau Cloud.
Therefore, the correct field to reference is Email.
* Tableau Cloud authentication documentation stating USERNAME() returns the user's email address.
* Row-Level Security setup guidance recommending the comparison USERNAME() = [Email Field].
* Tableau security practices indicating only the email column will match USERNAME() values on Tableau Cloud.
NEW QUESTION # 58
......
Salesforce Analytics-Con-301 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
Exam Questions Answers Braindumps Analytics-Con-301 Exam Dumps PDF Questions: https://pass4sure.dumps4pdf.com/Analytics-Con-301-valid-braindumps.html