(Select two)
In Tableau Server 2024.3, a governance team sets up collections for Q4 dashboards. Which features enable impact analysis before deleting a tagged data source used in 3 collections?
Review favorites count in the data source permissions dialog
Run lineage analysis from the data source Explore page
Enable data-driven alerts on collection subscriptions
Use Metadata API to query upstream dependencies programmatically
Explanation: Collections aggregate content for governance; lineage from Explore shows downstream impacts (workbooks, sheets) across collections. Metadata API (REST endpoints like /sites/{site- id}/dataSources/{datasource-id}/lineage) allows scripted dependency queries. Alerts monitor values, not structure; favorites are user-specific, not structural impact.
(Select All that Apply) In a CRM Analytics lens showing monthly sales by region, you apply a reference band from the analytics pane set to average sales with 95% confidence interval across panes. Which configurations correctly describe the resulting visualization behavior when regions have varying data volumes?
Confidence intervals use t-distribution for small sample sizes per pane
The band width varies per pane due to differing standard deviations
Bands extend to pane total aggregation ignoring cell-level variations
The central line shows weighted average across all panes
Explanation: The reference band with 95% confidence interval computes independently per pane based on the measure's values within that pane, leading to varying band widths when standard deviations differ due to data volumes. It employs t-distribution for panes with smaller samples to accurately reflect uncertainty, ensuring statistical validity in uneven distributions across regions.
In Tableau Server, a published data source extract refresh fails with error code 3000 (connection failure). The same extract refreshes successfully in Tableau Desktop. What is the likely cause?
Incremental refresh misconfigured
Schedule set to full refresh
Data source credentials not embedded
Missing driver on the server or Bridge configuration issue
Explanation: Error 3000 often indicates connection issues on the server side, such as missing database drivers, firewall blocks, or Tableau Bridge not properly configured for on-premises sources. Desktop refreshes succeed because the local machine has the necessary drivers and access.
Prep: Handle null-heavy "Latitude" for geo pivot. Impute spatially?
Generate rows from bounds
Join geo-lookup on ZIP
AVG([Lat]) PARTITION BY [City]
Filter nulls, alias to 0
Explanation: Lookup provides accurate spatial imputation respecting geo data roles over averages.
A data analyst is tasked with identifying the top-performing sales representatives based on total sales. Which method should they use to ensure accurate and up-to-date results?
Filter results based on historical data
Use a dynamic ranking calculation
Create a static report
Manually rank sales representatives each month
Explanation: A dynamic ranking calculation ensures that the top-performing sales representatives are identified based on the most current sales data, providing a real-time view of performance without manual updates.
When building a dashboard, an analyst notices that the objects are snapping to a grid and resizing together. The analyst wants to place a small legend on top of a map in a specific corner. Which setting should be used for the legend?
Floating
Standard
Tiled
Fixed
Explanation: Floating objects can be placed on top of other objects and moved to specific pixel coordinates. Tiled objects, by contrast, snap into a grid and do not overlap.
In a view with a trend line showing correlation, the analyst adds a reference distribution for standard error. What does the shaded band represent?
The range within which the true mean is likely to fall with 95% confidence
The interquartile range around the trend
The prediction interval for future values
The full data distribution excluding outliers
Explanation: Standard error bands in Tableau distributions around a trend line indicate the confidence interval for the estimated mean, typically 95%. Prediction intervals are wider and account for individual observations.
A dataset contains a "Product_ID" field where some values are recorded as "null" and others are empty strings (""). When creating a visualization that counts products, how does Tableau Desktop's "ZN()" function behave toward these two specific data quality issues?
It converts both "null" and empty strings to 0.
It converts "null" to 0 but leaves empty strings as strings.
It converts "null" to an empty string and leaves empty strings alone.
It ignores both "null" and empty strings during count operations.
Explanation: The ZN() function (Zero Null) specifically targets mathematical nulls and converts them to
zero. Since an empty string is a valid string value (length 0), the ZN() function does not affect it; the analyst would need to use a combination of TRIM or IF logic to handle empty strings separately.
What happens if you attempt to use a Spatial Join with two tables that are connected via the Logical Layer (Relationships)?
Tableau currently does not support spatial operators (like Intersects) in the Logical Layer
The spatial data is converted to latitude and longitude automatically
Tableau automatically converts them to a Union
It works exactly like a standard relationship
Explanation: As of current versions, spatial joins (using the "Intersects" operator) must be defined in the Physical Layer. Relationships (Logical Layer) currently support equality operators (=) but not spatial intersection.
In Tableau, which feature would you use to create a visual summary of sales performance across different product categories?
Worksheet
Dashboard
Data source
Story
Explanation: A dashboard is the most suitable feature for creating a visual summary of sales performance across different product categories. Dashboards allow you to combine multiple visualizations and present a comprehensive overview of data, making it easier to analyze performance across categories.
In a dataset where you want to analyze customer purchase frequency, which calculated field would help you derive insights?
SUM([Sales])
COUNT([Order Date])
AVG([Order Count])
DATEDIFF('month', MIN([Order Date]), MAX([Order Date]))
Explanation: The DATEDIFF function calculates the time span between the first and last purchase dates, providing insights into customer purchase frequency over time.
When relationships are not possible due to disparate data sources (e.g., Excel budget vs SQL actuals), you blend on 'Category' with a left join equivalent by editing relationships and filtering nulls. Aggregations show SUM(Actuals) and AVG(Budget)* from secondary.
In what scenario is blending preferred over relationships or joins?
When requiring real-time updates across sources, as blending queries live only.
For same-source tables where physical joins are faster but blending allows dynamic links.
When combining aggregated data from multiple sources without flattening, preserving original queries.
When data sources share keys but blending enforces full outer joins automatically.
Explanation: When combining aggregated data from multiple sources without flattening, preserving original queries is preferred because blending queries sources independently at viz time, ideal for disparate granularities. For same-source tables where physical joins are faster but blending allows dynamic links is incorrect; joins/relationships for same-source. When data sources share keys but blending enforces full outer joins automatically is wrong; default left, configurable. When requiring real-time updates across sources, as blending queries live only works if sources are live, but extracts possible.
In which scenario would you prefer to use a Right Join over a Left Join in Tableau?
When both datasets have identical records.
When you need to include all records from the right dataset regardless of matches.
When you want to analyze data from a single source only.
When you want to retain all records from the left dataset.
Explanation: A Right Join is preferred when you need to include all records from the right dataset regardless of whether they have matching records in the left dataset. This is useful for ensuring that all relevant data from the right dataset is included in the analysis.
When a new image widget is added to the desktop layout for branding, it should appear in mobile layouts too. What ensures this without manual addition?
Manual addition to each layout
Automatic sync of widget additions across device layouts
Use image as dashboard background
Place image in a shared container
Explanation: Widget additions, including images, automatically sync across all device layouts in recent CRM Analytics versions, so adding to one layout propagates to others. Manual addition defeats sync benefits. Background images apply globally but are not widgets. Shared containers do not force sync.
(Select two)
A data steward certifies a data source on Tableau Server but notices uncertiļ¬ed lineage in impact analysis. Which steps ensure full certification propagation?
Use the Certify API endpoint with cascade=true parameter
Run full metadata refresh from Server Admin > Maintenance
Add data source to a collection with certified status
Recertify all dependent workbooks manually
Explanation: Certification is per-asset; dependents must be manually recertified for lineage to show trusted chain. Metadata refresh rebuilds lineage graphs. No cascade API param exists; collections group but don't propagate status.
A consultant is blending data from a CSV file containing "Target_Quota" and a Salesforce dataset "Sales_Results." The CSV uses "Rep_Name" and the Salesforce dataset uses "Full_Name." The consultant notices "Rep_Name" has extra spaces (e.g., "John Doe "). What transformation should be applied before the join?
Concatenate
Substring
Uppercase
Trim
Explanation: When relationships aren't feasible due to data quality issues (like leading or trailing spaces), a "Trim" transformation is essential. Cleaning the data ensures that the join keys match exactly, allowing the blending of the CSV and Salesforce data to succeed.
Scenario: Parameter-driven interactivity for rep dashboard swaps from team summary to individual pipeline on rep name select. Complex setup?
Multi-value list param, action on selector facet updating param, calc field if param contains(rep_name) then detail else summary
Single toggle only for binary swap
No param, use filter actions alone
External JS embedding
Explanation: Multi-value list param, action on selector facet updating param, calc field if param contains(rep_name) then detail else summary handles dynamic multi-rep selection with conditional viz swapping. Binary toggle insufficient. Filter actions lack sheet swap. JS non-native.
You connect to a spatial file (Shapefile) containing country boundaries and a CSV file with sales by country code. To enable accurate mapping, which approach correctly links the spatial and non-spatial data?
Create a relationship using the country code field
Use a cross-database join on geometry field
Perform a union on the spatial and CSV files
Use a spatial join in the physical layer
Explanation: Creating a relationship using the country code field is correct because Tableau supports relationships on non-spatial keys like country codes to link spatial and non-spatial data, preserving detail and enabling accurate mapping without forcing a physical join. Spatial joins in physical layer require geometry matching and can be complex. Unions do not combine geometries properly. Cross-database joins are not needed here.
A dashboard designer notices that adding a new chart widget to the desktop layout automatically appears in phone and tablet layouts. What feature enables this behavior?
Automatic sync of widget additions and changes across all device layouts
Responsive grid without layouts
Floating layout containers
Manual copy-paste between layouts
Explanation: Recent CRM Analytics updates automatically synchronize widget additions, removals, and certain changes across multiple device layouts, ensuring consistency and reducing manual updates when modifying one layout. Manual copy-paste is unnecessary and error-prone. Floating containers and simple responsive grid do not handle device-specific layouts.
What feature in Tableau Cloud allows for automatic scaling of resources based on user demand?
Auto-scaling
Activity logs
Content management
Data governance
Explanation: Auto-scaling is a feature in Tableau Cloud that allows the platform to automatically adjust resources based on user demand. This ensures optimal performance during peak usage times without
manual intervention.
A business requires a report showing "Sales by Product" where the Product data comes from an external Postgres database and Sales data comes from Salesforce. The Postgres data is refreshed once a week, while Salesforce data is live. How should the blending be handled?
Use a Data Prep recipe to join the synced Postgres object and the Salesforce object.
Use a "Direct Data" connection for both.
Use a SAQL "fill" function to bridge the data.
Export Salesforce data to Postgres and do the join there.
Explanation: CRM Analytics is designed to blend disparate sources. By syncing the Postgres data into CRM Analytics (as a connected object) and using a recipe to join it with Salesforce data, you create a performant, unified dataset that respects the refresh schedules of both sources.
To ensure a Tableau dashboard is accessible to color-blind users and those with low vision, which steps are critical? (Select all that apply)
Reduce visual complexity by aggregating data
Rely solely on patterns instead of colors
Use color-blind-friendly palettes and verify contrast ratios
Add detailed alt text to visualizations
Explanation: Color-blind-friendly palettes combined with verified contrast ratios ensure visual elements are distinguishable. Detailed alt text provides textual alternatives for color-dependent information. Aggregating data reduces complexity, aiding comprehension for all users including those with visual impairments. Patterns can supplement but are not a complete replacement.
A dataset has columns 'Region', '2021_Sales', '2022_Sales', and '2023_Sales'. The analyst wants to create a line chart showing sales over time. What transformation should be performed in the Tableau Data Source page?
Join the table to itself
Split the 'Region' column
Use a Wildcard Union
Pivot the 'Year' columns into 'Year' and 'Sales' values
Explanation: Pivoting converts data from a "wide" format (multiple columns for values) to a "tall" format (one column for the category and one for the value). This is essential for creating time-series visualizations where the time component needs to be a single dimension.
A reference band is configured from the 10th to 90th percentile on a profit distribution chart. Which interpretation is correct?
It represents the standard deviation band scaled to percentiles
It highlights only the interquartile range adjusted
It shows the range where 90% of profits lie above the 10th percentile
The band covers the central 80% of profit values, excluding the top and bottom 10%
Explanation: Percentile-based reference bands from 10th to 90th shade the middle 80% of ordered data, trimming the most extreme 10% on each end. This helps focus on typical values while de-emphasizing tails.