Enhance Your Career With Available Preparation Guide for Analytics-Con-301 Exam
Get Special Discount Offer of Analytics-Con-301 Certification Exam Sample Questions and Answers
Salesforce Analytics-Con-301 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 11
A multi-national company wants to have a Tableau dashboard that will provide country-level information for both its forecast summaries and year-on-year metrics. The company wants to toggle between these two views while leaving main key performance indicators (KPIs) visible on the main dashboard.
Which method is the most efficient in achieving the company's requirements?
- A. Create a parameter that accepts values from a list that contains "Forecast View" and "Year-on-Year View."
. Right-click the parameter and select Add to Sheet for both worksheets.
. Navigate back to the dashboard and to the upper corner of the two worksheets.
. Enable the Use as Filter option. - B. Create a Boolean parameter with the two names of the views as aliases and a corresponding calculated field with the following calculation: True.
. Add the forecast summary sheet to the dashboard and add the year-on-year metrics sheet to the same dashboard as a Floating dashboard object. - C. Create a single worksheet with all the measures required for both the forecast summary and the year-on-year views.
. Create a Boolean parameter and a corresponding calculated field with the following calculation: True.
. Add a blank dashboard object and in the Layout tab, check the box for "Control visibility using value" and select the parameter you created. - D. Create a dashboard with the sheets containing the main KPIs and the forecast summary worksheet.
. Duplicate this dashboard and replace the forecast view worksheet with the year-on-year metrics worksheet.
. Add navigation buttons to both dashboards.
Answer: B
Explanation:
. Add the calculated fields as a Detail under the Marks card of the floating view, create a "Change Parameter" action, and set the
"Target Parameter" and "Source Fields" to the parameter and calculated field you created.
. Check the box for "Control visibility using value" in the Layout tab of the floating view and select the parameter you created.
Explanation:
The most efficient method for toggling between two views (forecast summaries and year-on-year metrics) while keeping main KPIs visible involves using a parameter and calculated fields for controlling visibility:
Create a Boolean Parameter: This parameter will have two aliases representing the two views ("Forecast View" and "Year-on-Year View"). This allows the user to select which view they wish to see directly from the dashboard.
Calculated Field: Create a calculated field that always returns True. This field acts as a constant placeholder to enable the visibility control tied to the parameter.
Dashboard Setup: Place both the forecast summary and the year-on-year metrics sheets on the dashboard. Set the year-on-year metrics sheet as a floating object over the forecast summary.
Visibility Control: Use the "Control visibility using value" option in the Layout tab for the floating year-on-year metrics view. Tie this setting to the Boolean parameter so that changing the parameter will show or hide this view without affecting the main KPIs displayed on the dashboard.
Interactivity: Implement a "Change Parameter" dashboard action where selecting different options in the dashboard (e.g., clicking on certain parts) triggers the parameter to change, thus toggling the visible view.
References
This method leverages Tableau's dashboard interactivity features including parameters, calculated fields, and visibility settings, as recommended in Tableau's user guide on dynamic dashboard design.
NEW QUESTION # 12
A client calculates the percent of total sales for a particular region compared to all regions.
The Sales percentage is inadvertently recalculated each time the filter is applied to the Region.
Which calculation should fix the automatic recalculation on the % of total field?
- A. {FIXED [Region]: SUM([Sales])} / {FIXED :SUM([Sales])}
- B. {FIXED [Region]: SUM([Sales])} / { [Sales] }
- C. {FIXED [Region]: SUM([Sales])} / SUM([Sales])
- D. {FIXED [Region]: SUM([Sales])}
Answer: A
Explanation:
The problem:
The client wants:
Percent of total sales for each region compared to ALL regions,
even when Region is filtered.
However, the calculation currently behaves like a table calculation:
SUM([Sales]) / TOTAL(SUM([Sales]))
This recalculates the total after Region filters are applied, so removing a region changes the denominator.
Tableau Documentation - How to prevent recalculation:
To keep percent-of-total unchanged when filtering, Tableau's recommended method is to use FIXED LOD expressions to lock the granularity.
Two values must be fixed:
* Numerator: Sales for that specific region{ FIXED [Region] : SUM([Sales]) }
* Denominator: Total sales across all regions, independent of filters{ FIXED : SUM([Sales]) }(FIXED with no dimension = entire data set) Then compute the percentage:
{ FIXED [Region] : SUM([Sales]) } / { FIXED : SUM([Sales]) }
This ensures:
* The region sales remain accurate.
* The overall total remains constant, even if filters remove regions.
* Region filtering no longer recalculates percent-of-total.
Why the other options are incorrect:
A). {FIXED [Region]: SUM([Sales])} / SUM([Sales])
The denominator is still affected by filters # recalculates % of total.
B). {FIXED [Region]: SUM([Sales])} / { [Sales] }
{[Sales]} is not valid syntax and does not fix granularity.
D). {FIXED [Region]: SUM([Sales])}
This gives only the numerator - no percent-of-total calculation.
The only correct LOD solution is option C.
* Tableau LOD Expression Guide: FIXED for filter-independent calculations.
* Tableau Percent-of-Total Best Practices: use FIXED LOD to avoid recalculation when filters change.
* Order of Operations: FIXED LODs occur before dimension filters, keeping totals stable.
NEW QUESTION # 13
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. DATENAME('iso-weekday', [Order Date])>=6
- B. DATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7
- C. DATEPART('weekday', [Order Date])>=6
- D. DATEPART('iso-weekday', [Order Date])>=6
Answer: B
Explanation:
The calculation DATEPART('iso-weekday', [Order Date])=1 or DATEPART('iso-weekday', [Order Date])=7 is recommended because the ISO standard considers Monday as the first day of the week (1) and Sunday as the last day (7). This calculation will correctly identify Saturdays and Sundays regardless of the locale settings of the workbook's data source, ensuring that the report includes these days as specified by the client.
References: The use of the 'iso-weekday' part in the DATEPART function is consistent with the ISO 8601 standard, which is independent of locale settings. This approach is supported by Tableau's documentation on date functions and their behavior with different locale settings123.
To accurately identify weekends across different locale settings, using the 'iso-weekday' component is reliable as it is consistent across various locales:
ISO Weekday Function: The ISO standard treats Monday as the first day of the week (1), which makes Sunday the seventh day (7). This standardization helps avoid discrepancies in weekday calculations that might arise due to locale-specific settings.
Identifying Weekends: The calculation checks if the 'iso-weekday' part of the date is either 1 (Sunday) or 7 (Saturday), thereby correctly identifying weekends regardless of the locale settings.
References:
Handling Locale-Specific Settings: Using ISO standards in date functions allows for uniform results across systems with differing locale settings, essential for consistent reporting in global applications.
NEW QUESTION # 14
A consultant is tasked with improving the performance of a large workbook that contains multiple dashboards, each of which leverages a separate data source. What is one way to improve performance?
- A. Convert Data Source filters to Quick Filters.
- B. Restrict the users who can access the workbook.
- C. Convert any extracted data sources to live data sources.
- D. Split the workbook into multiple workbooks.
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau's performance best-practice documentation explains that large workbooks containing many dashboards, multiple data sources, and complex interactions have heavier memory and CPU requirements. When a workbook grows too large, Tableau must:
* Load every data source
* Cache metadata for all sheets
* Maintain connections across all dashboards
* Render more worksheets simultaneously
This increases workbook load time and slows dashboard performance.
A documented method for improving performance is to split a large workbook into multiple smaller workbooks, each containing only the dashboards relevant to a particular audience or subject area. Smaller workbooks:
* Reduce the amount of metadata Tableau must load
* Reduce extract sizes per workbook
* Improve caching efficiency
* Improve dashboard loading and rendering time
Options A, B, and C do not improve workbook performance:
* A. Converting Data Source Filters to Quick Filters reduces performance because Quick Filters (interactive filters) are more expensive than Data Source filters and slow down rendering.
* B. Converting extracts to live connections typically worsens performance because live sources depend on database query speed, network latency, and server load.
* C. Restricting users does not change workbook performance, only access.
Splitting the workbook is a recognized Tableau strategy for improving performance of large, multi-dashboard workbooks.
* Tableau Performance Optimization guidelines encouraging splitting large workbooks into smaller ones.
* Workbook design best practices emphasizing reduced complexity and smaller metadata footprints.
* Documentation on performance costs associated with Quick Filters and multiple data sources.
NEW QUESTION # 15
A consultant used Tableau Data Catalog to determine which workbooks will be affected by a field change.
Catalog shows:
* Published Data Source # 7 connected workbooks
* Field search (Lineage tab) # 6 impacted workbooks
The client asks: Why 7 connected, but only 6 impacted?
- A. The field being altered is not used in the seventh workbook.
- B. The consultant lacked sufficient permissions to see the seventh workbook.
- C. The field is used twice in a single workbook.
- D. The seventh workbook is connected via Custom SQL so it didn't appear in the list.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Key Tableau Catalog behaviors:
* Connected workbooks = any workbook linked to the published data source.
* Impacted workbooks = only workbooks that use the specific field.
* If a workbook connects to the data source but never uses the field, it appears as "connected" but not impacted.
This explains EXACTLY why:
* 7 workbooks are connected
* Only 6 use the changed field
* Therefore only 6 are impacted
This matches Option C.
Why the other options are incorrect:
A). Field used twice
Still counts as one workbook - does not explain discrepancy.
B). Permission issue
If permissions blocked visibility, the data source would not list 7 connections.
D). Custom SQL use
Catalog can still detect field usage through metadata lineage; Custom SQL does NOT hide workbook dependency.
Thus, only Option C logically explains the scenario.
* Data Catalog lineage rules: "Connected vs. Impacted" distinction.
* Field-level impact analysis documentation.
* Workbook dependency logic within Tableau Catalog.
NEW QUESTION # 16
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 Prep Conductor
- B. Tableau Catalog without Tableau Data Management Add-on
- C. Tableau Catalog with Tableau Data Management Add-on
- D. Tableau Catalog with Tableau Server Management Add-on
Answer: C
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 # 17
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 the deepest granularity method because it is the most performant and the duplicate values will be handled by the mapping table.
- B. Use sparse entitlements because it defines entitlements at every level of the hierarchy and can handle duplicate values in the dataset.
- C. Use sparse entitlements because it is the most performant and the duplicate values will be handled by the mapping table.
- D. Use the deepest granularity method because it defines entitlements at every level of the hierarchy and can handle duplicate values in the dataset.
Answer: B
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 # 18
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 Creators have connected to the data source in Tableau Desktop but have not yet published a workbook.
- B. Some workbooks have not been viewed by enough users yet.
- C. Some of the workbooks connected to the data source are not visible to the user due to permissions.
- D. Some workbooks have been connected to the data source, but do not use any fields from it.
Answer: C
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 # 19
A client has many published data sources in Tableau Server. The data sources use the same databases and tables. The client notices different departments give different answers to the same business questions, and the departments cannot trust the data. The client wants to know what causes data sources to return different data.
Which tool should the client use to identify this issue?
- A. Tableau Prep Conductor
- B. Tableau Catalog
- C. Ask Data
- D. Tableau Resource Monitoring Tool
Answer: B
Explanation:
The Tableau Catalog is part of the Tableau Data Management Add-on and is designed to help users understand the data they are using within Tableau. It provides a comprehensive view of all the data assets in Tableau Server or Tableau Online, including databases, tables, and fields. It can help identify issues such as data quality, data lineage, and impact analysis. In this case, where different departments are getting different answers to the same business questions, the Tableau Catalog can be used to track down inconsistencies and ensure that everyone is working from the same, reliable data source.
References: The recommendation for using Tableau Catalog is based on its features that support data discovery, quality, and governance, which are essential for resolving data inconsistencies across different departments12.
When different departments report different answers to the same business questions using the same databases and tables, the issue often lies in how data is being accessed and interpreted differently across departments. Tableau Catalog, a part of Tableau Data Management, can be used to solve this problem:
Visibility: Tableau Catalog gives visibility into the data used in Tableau, showing users where data comes from, where it's used, and who's using it.
Consistency and Trust: It helps ensure consistency and trust in data by providing detailed metadata management that can highlight discrepancies in data usage or interpretation.
Usage Metrics and Lineage: It offers tools for tracking usage metrics and understanding data lineage, which can help in identifying why different departments might see different results from the same underlying data.
References:
Tableau Catalog Usage: The Catalog is instrumental in providing a detailed view of the data environment, allowing organizations to audit, track, and understand data discrepancies across different users and departments.
NEW QUESTION # 20
A client wants guidance for Creators to build efficient extracts from large data sources.
What are three Tableau best practices that the Creators should use? Choose three.
- A. Use aggregate data for visible dimensions, whenever possible.
- B. Use only live connections as they are always faster than extracts.
- C. Hide all unused fields.
- D. Keep only the data required for analysis by using extract filters.
- E. Include all the data from the original data source in the extract.
Answer: A,C,D
Explanation:
To build efficient extracts from large data sources, it is crucial to minimize the load and optimize the performance of the extracts:
A . Keep only the data required for analysis by using extract filters: This best practice involves using filters to reduce the volume of data extracted, thus focusing only on the data necessary for analysis.
B . Use aggregate data for visible dimensions, whenever possible: Aggregating data at the time of extraction reduces the granularity of the data, which can significantly improve performance and reduce the size of the extract.
E . Hide all unused fields: Removing fields that are not needed for analysis from the extract reduces the complexity and size of the data model, which in turn enhances performance and speeds up load times.
These practices are endorsed in Tableau's official documentation and training sessions as effective ways to enhance the performance of Tableau extracts and optimize dashboard responsiveness.
NEW QUESTION # 21
A consultant migrated a data source to improve performance. The consultant wants to identify which workbooks need to be updated to point to the new data source.
Which Tableau tool should the consultant use?
- A. Tableau Advanced Management
- B. Data Management
- C. Activity Log
- D. Prep Conductor
Answer: A
Explanation:
To identify which workbooks need to be updated to point to a new data source after a migration, a consultant should use Tableau Advanced Management. This component of Tableau provides comprehensive management capabilities including the ability to track workbook dependencies and data source usage across your entire Tableau environment. Using Tableau Advanced Management allows consultants to assess the impact of changes in the data source on connected workbooks and efficiently manage updates.
NEW QUESTION # 22
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. Continue to use NULL as the BrowserID in the Site Visitor Table and leave the Referential Integrity set to "Some Records Match."
- B. Continue to use NULL as the BrowserID in the Site Visitor Table and change the Referential Integrity to "All Records Match."
- C. 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."
- D. 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."
Answer: C
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 # 23
A client is evaluating which user roles to assign to managers. The managers need to view dashboards, create Data-Driven Alerts, and perform ad hoc analysis of existing Tableau data sources. A consultant must provide a solution that minimizes licensing costs.
Which role should the consultant recommend be assigned to the managers?
- A. Creator
- B. Viewer
- C. Explorer
- D. Site Administrator
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Tableau documentation clearly defines user capabilities per license:
Viewer
* Can view dashboards only.
* Cannot create Data-Driven Alerts.
* Cannot perform ad hoc analysis.# Insufficient.
Explorer
* Can view dashboards.
* Can create Data-Driven Alerts.
* Can perform ad hoc analysis using existing published data sources.
* Does NOT require full creator-level capabilities.# Meets all requirements at lower cost than Creator.
Creator
* Full authoring, data source creation, and prep capabilities.
* Higher cost.# Overkill and violates "minimizes licensing costs."
Site Administrator
* Includes Creator capabilities plus admin privileges.
* Most expensive.# Not appropriate for managers.
Therefore, the correct and most cost-efficient role is Explorer.
* Tableau role capability matrix showing Explorers can create alerts and analyze existing data sources.
* Licensing guidance recommending Explorer for ad hoc analysis without data-source creation.
NEW QUESTION # 24
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 all workbooks in a single project
- B. Three separate Tableau Cloud instances for Finance, Strategy, and Marketing
- C. One Tableau Cloud instance with two sites for Strategy and Marketing, and one Tableau Server instance for Finance
- D. One Tableau Cloud instance configured with a Finance project folder, Strategy project folder, and Marketing project folder
Answer: D
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.
References
This 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 # 25
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. Compatibility with newer Tableau Desktop and Prep Builder versions that users might want to install
- B. Users are complaining of performance; the upgrade will reduce the server's hardware requirements
- C. The security team has a report of bugs and security vulnerabilities in older versions of Tableau
- D. The need to access new features and improvements from Tableau Cloud
Answer: A,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 # 26
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. The Split option
- C. The Aliases option
- D. A calculated field that uses the TRIM function
Answer: B
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 # 27
A client calculates the percent of total sales for a particular region compared to all regions.
Which calculation will fix the automatic recalculation on the % of total field?
- A. {FIXED [Region]:[Sales]}/{FIXED: SUM([Sales])}
- B. {FIXED [Region]:sum([Sales])}
- C. {FIXED [Region]:sum([Sales])}/{FIXED :SUM([Sales])
- D. {FIXED [Region]:sum([Sales])}/SUM([Sales]}
Answer: D
Explanation:
To correctly calculate the percent of total sales for a particular region compared to all regions, and to ensure that the calculation does not get inadvertently recalculated with each region filter application, the recommended calculation is:
* {FIXED [Region]: sum([Sales])}: This part of the formula computes the sum of sales for each region, regardless of any filters applied to the view. It uses a Level of Detail expression to fix the sum of sales to each region, ensuring that filtering by regions won't affect the calculated value.
* SUM([Sales]): This part computes the total sum of sales across all regions and is recalculated dynamically based on the filters applied to other parts of the dashboard or worksheet.
* Combining the two parts: By dividing the fixed regional sales by the total sales, we get the proportion of sales for each region as compared to the total. This calculation ensures that while the denominator adjusts according to filters, the numerator remains fixed for each region, accurately reflecting the sales percentage without being affected by the region filter directly.
References
This calculation follows Tableau's best practices for using Level of Detail expressions to manage computation granularity in the presence of dashboard filters, as outlined in the Tableau User Guide and official Tableau training materials.
NEW QUESTION # 28
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. Current custom access will be maintained, but new custom permissions will not be granted.
- B. Users will be notified that they will automatically lose access to content after 30 days.
- C. Users will be prompted to manually update permissions for all nested projects.
- 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 # 29
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. Booleans are fastest, followed by integers, and then strings.
- 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 # 30
A client is migrating their data warehouse. They visualize the data in workbooks hosted on Tableau Server with Tableau Data Management enabled and want to see how many workbooks will be impacted.
What should the consultant do to quickly identify how many workbooks will be impacted?
- A. Open each workbook and identify the data source.
- B. Complete the migration and let users report errors as they are noticed.
- C. In Tableau Server, select the database from External Assets, then select the Lineage tab.
- D. Leverage the Tableau Developer API to query the workbooks' metadata.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When Tableau Data Management is enabled, Tableau Catalog provides Lineage capabilities that map connections between:
* External databases
* Tables
* Data sources
* Workbooks
* Fields
Tableau documentation states that the Lineage tab for any external asset (such as a database or table):
* Shows all connected workbooks
* Shows dependencies and impact analysis
* Allows admins to instantly assess how many analytics assets will be affected by a data warehouse migration Option A directly uses Tableau Catalog to perform exactly this task.
Option B is unnecessary because the Catalog lineage tool already provides this information without development effort.
Option C is completely inappropriate because it offers no analysis or planning.
Option D is too time-consuming and unnecessary, especially when Tableau Catalog provides an automated dependency map.
Therefore, the correct method is to use the Lineage tab in External Assets.
* Tableau Catalog lineage documentation showing how to view impacted workbooks.
* External Assets and data source dependency features in Tableau Data Management.
* Impact analysis best practices for data warehouse migration using Tableau Catalog.
NEW QUESTION # 31
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. Email
- B. Abbreviated Name
- C. Lower case Name
Answer: A
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 # 32
SIMULATION
Refer to the exhibit.
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 # 33
A multi-national company wants to have a Tableau dashboard that will provide country-level information for both its forecast summaries and year-on-year metrics. The company wants to toggle between these two views while leaving main key performance indicators (KPIs) visible on the main dashboard.
Which method is the most efficient in achieving the company's requirements?
- A. Create a parameter that accepts values from a list that contains "Forecast View" and "Year-on-Year View."
. Right-click the parameter and select Add to Sheet for both worksheets.
. Navigate back to the dashboard and to the upper corner of the two worksheets.
. Enable the Use as Filter option. - B. Create a Boolean parameter with the two names of the views as aliases and a corresponding calculated field with the following calculation: True.
. Add the forecast summary sheet to the dashboard and add the year-on-year metrics sheet to the same dashboard as a Floating dashboard object.
. Add the calculated fields as a Detail under the Marks card of the floating view, create a "Change Parameter" action, and set the
"Target Parameter" and "Source Fields" to the parameter and calculated field you created.
. Check the box for "Control visibility using value" in the Layout tab of the floating view and select the parameter you created. - C. Create a single worksheet with all the measures required for both the forecast summary and the year-on- year views.
. Create a Boolean parameter and a corresponding calculated field with the following calculation: True.
. Add a blank dashboard object and in the Layout tab, check the box for "Control visibility using value" and select the parameter you created. - D. Create a dashboard with the sheets containing the main KPIs and the forecast summary worksheet.
. Duplicate this dashboard and replace the forecast view worksheet with the year-on-year metrics worksheet.
. Add navigation buttons to both dashboards.
Answer: B
Explanation:
The most efficient method for toggling between two views (forecast summaries and year-on-year metrics) while keeping main KPIs visible involves using a parameter and calculated fields for controlling visibility:
* Create a Boolean Parameter: This parameter will have two aliases representing the two views ("Forecast View" and "Year-on-Year View"). This allows the user to select which view they wish to see directly from the dashboard.
* Calculated Field: Create a calculated field that always returns True. This field acts as a constant placeholder to enable the visibility control tied to the parameter.
* Dashboard Setup: Place both the forecast summary and the year-on-year metrics sheets on the dashboard. Set the year-on-year metrics sheet as a floating object over the forecast summary.
* Visibility Control: Use the "Control visibility using value" option in the Layout tab for the floating year-on-year metrics view. Tie this setting to the Boolean parameter so that changing the parameter will show or hide this view without affecting the main KPIs displayed on the dashboard.
* Interactivity: Implement a "Change Parameter" dashboard action where selecting different options in the dashboard (e.g., clicking on certain parts) triggers the parameter to change, thus toggling the visible view.
References
This method leverages Tableau's dashboard interactivity features including parameters, calculated fields, and visibility settings, as recommended in Tableau's user guide on dynamic dashboard design.
NEW QUESTION # 34
A new Tableau user created a simple dashboard on Tableau Server using supply chain data. Now, the user wants to know if they created the dashboard in accordance with specific performance best practices.
Which approach should the consultant recommend for the client to make this determination?
- A. Use Performance Recording in Tableau Desktop.
- B. Run Workbook Optimizer.
- C. Use inbuilt dashboards in Tableau Server to troubleshoot the performance.
- D. Use Performance Recording on Tableau Server.
Answer: B
Explanation:
The Workbook Optimizer is a tool specifically designed to evaluate a workbook against performance best practices. It provides feedback on key design characteristics and offers concrete guidance on how to improve workbook performance. This tool is beneficial for both new and experienced Tableau users to ensure their dashboards are optimized for performance1.
References: The Workbook Optimizer's functionality is detailed in Tableau's official documentation, which explains how it assesses workbooks against a set of rules derived from best practices1. Additionally, the Performance Recording feature in Tableau Desktop and Server can be used to identify performance issues, but the Workbook Optimizer gives a more comprehensive analysis of the workbook's adherence to best practices23.
NEW QUESTION # 35
......
Updated Analytics-Con-301 Dumps Questions Are Available For Passing Salesforce Exam: https://www.dumpsfree.com/Analytics-Con-301-valid-exam.html
New Analytics-Con-301 Dumps For Preparing Salesforce Consultant Certified Salesforce Exam Well: https://drive.google.com/open?id=1yxAhQr0m2GQjlP9da9raauYBYq5Ow_8Y