Free Practice Questions for Salesforce Analytics-Con-301 Exam

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.

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.

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.

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.

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.

For implementing row-level security (RLS) without the Tableau Data Management Add-on, the best approach is to integrate user filters into the published data source:

Creating User Filters on Published Data Source: This method involves defining user filters that apply directly to the data source before it is published to the Tableau Server. This ensures that any workbook or view leveraging this data source inherently respects the row-level security settings.

To implement this, create a calculated field in Tableau that defines the security logic, typically using a formula that references user functions (like USERNAME() or ISMEMBEROF()). Drag this field to the Filters shelf and configure it to match the security rules (who can see what data).

Once configured, publish the data source to Tableau Server with these filters in place. This approach centralizes security management, making it easier to maintain and update security policies as they are applied universally to all workbooks using this data source.

This strategy is safe as it reduces the risk of accidental data exposure through individual workbook misconfiguration and simplifies long-term maintenance of security policies.

References

This method follows Tableau’s best practices for implementing row-level security as detailed in Tableau’s security management resources. It ensures robust, maintainable security measures that scale with organizational needs without requiring additional add-ons.

Comprehensive and Detailed Explanation From Exact Extract:

The requirement is:

Compute total sales per customer, not per transaction.

Then compute the average of those customer totals, grouped by region.

Tableau documentation states that FIXED LOD expressions are used to calculate values at a specific level of granularity regardless of the view.

To solve the business need:

Step 1:

Calculate total customer sales for each Customer ID within each Region:

{ FIXED [Customer ID], [Region] : SUM([Sales Amount]) }

This produces one number per customer per region.

Step 2:

Compute the average of those totals:

AVG( { FIXED [Customer ID], [Region] : SUM([Sales Amount]) } )

This yields:

Average total customer sales by region

This is exactly option C.

Why the other options are incorrect:

A. EXCLUDE Region: Would combine regions and incorrectly calculate overall totals.

B. FIXED Region: AVG(Sales Amount): Computes average of line-level sales, not customer totals.

D. FIXED Customer ID + Region: AVG(Sales Amount): Averages individual transactions, not customer totals.

Only option C matches the required two-step logic.

LOD Expressions: FIXED for computing customer-level aggregates.

Nested LOD usage for first calculating customer totals, then averaging them at a higher level.

Tableau guidance: SUM inside FIXED for per-customer totals, AVG outside for averaging customers.

Tableau’s official in-place upgrade steps for single-node Tableau Server require:

Disable scheduled tasks (to prevent extract failures during upgrade).

Run the upgrade script for the new version.

Validate and test the server after upgrade.

The critical detail:

An in-place upgrade means upgrading the existing production environment directly, not installing in a separate environment or cloning VMs.

Option B matches exactly the documented operational steps for an in-place upgrade.

Why the other options are incorrect:

A: Uninstalling Tableau Server is not part of an in-place upgrade workflow.

C: This describes a migration or test upgrade in a separate environment, not an in-place upgrade.

D: VM cloning and restoring is not required for in-place upgrades and is not part of Tableau’s official procedure.

Only B represents the correct in-place upgrade sequence.

Tableau Server in-place upgrade instructions: disable tasks → run upgrade script → test.

Single-node upgrade guidelines noting that uninstalling is not required.

Tableau Server administration materials clarifying the difference between in-place upgrade and sandbox testing.

When migrating content between Tableau servers, certain types of content may require special consideration or different tools for migration:

Tableau Prep Flows: These are specific to Tableau Prep and are not included in the standard content migration capabilities of the Tableau Content Migration Tool. Tableau Prep flows often require separate processes for migration due to their distinct setup and integration with data sources and workflows.

Published Data Sources and Workbooks: These can typically be migrated directly using the Tableau Content Migration Tool, which supports moving published data sources (both live connections and extracts) and workbooks without requiring additional tools.