Which Tableau feature allows organizations to map their governance needs effectively to Tableau's functionality?
Data extracts
Tableau Catalog
Tableau Online
Tableau Server
Explanation: Tableau Catalog provides visibility into the data assets within Tableau, helping organizations understand their data landscape and governance needs. It allows tracking of data lineage and usage, which is essential for effective governance.
To ensure data quality in governance strategy, which feature combination minimizes warnings while certifying sources?
Disable warnings
Use only uncertified sources
Warn on all sources and certify post-publish
Certify sources after lineage review and apply warnings only to uncertified lineage dependents
Explanation: Proactive certification after lineage validation reduces warnings. Applying warnings selectively to uncertified dependents encourages cleanup without overwhelming users.
Which of the following is a recommended practice for optimizing performance when using calculations in Tableau?
Simplify calculations where possible and move them upstream
Rely solely on Tableau's default calculations
Use as many calculations as needed for detailed analysis
Always use calculated fields instead of raw data
Explanation: Simplifying calculations and moving them upstream to the data source can significantly enhance performance by reducing the workload on Tableau and leveraging database processing capabilities.
Troubleshoot slow calc: {FIXED [Customer]: SUM({INCLUDE [Order]: [Sales]})} for customer lifetime. Returns wrong total. Cause?
Filter nulls
Use SUM instead
Inner INCLUDE causes overcounting; use FIXED only or adjust aggregation
Use AVG
Explanation: INCLUDE inside FIXED can over-aggregate if not matched. Use consistent FIXED or pre- aggregate per customer upstream.
A social media platform's user interaction database uses a key-value store. Evaluation identifies risks in handling complex queries for trend analysis due to lack of secondary indexes. What does this risk manifest as?
Over-provisioned memory for caching
Minimal write throughput during peak hours
Seamless integration with ETL tools
Increased read amplification leading to higher I/O costs
Explanation: Increased read amplification leading to higher I/O costs occurs because without secondary indexes, trend analysis queries must scan entire partitions, multiplying disk operations and escalating expenses in a high-volume interaction environment.
Data conn plan: External API hourly, granularity minute-level est.
Interpolate transform
Aggregate
Reject
Hourly sync only
Explanation: Interpolation meets est granularity needs.
Troubleshooting a dashboard where a RANK_PERCENTILE(SUM([Sales])) calc ranks incorrectly when a [Category] filter is applied, showing ranks over the full dataset instead of filtered, what order of operations violation is at play, and which advanced fix involves LOD expressions?
Table calcs post-filters; use {EXCLUDE [Category]: RANK_PERCENTILE(SUM([Sales]))}
Parameters override; dynamize rank via parameter
Filters before calcs; add category to calc partition
LODs precede; nest rank in FIXED LOD
Explanation: Table calculations like RANK_PERCENTILE occur after dimension filters, so they rank the filtered view correctly, but if partitioning excludes [Category], it might aggregate broadly. The issue is mispartitioning; using EXCLUDE LOD computes rank post-filter, excluding [Category] for accurate filtered ranking. Filters before calcs; add category to calc partition adjusts compute using for proper grouping. LODs precede; nest rank in FIXED LOD fixes pre-filter but alters percentile logic. Parameters override; dynamize rank via parameter doesn't address order directly.
Fintech: 500M trades/day with FIX tags → normalized trades. Strategy?
Flink Table API with dynamic tables
Apache NiFi for schema mediation
Direct BigQuery load with JSON_EXTRACT
Use dbt macros for tag mapping with Jinja conditionals
Explanation: dbt provides reproducible transformations with testing. NiFi routing, not analytics. JSON_EXTRACT fragile.
A dashboard uses a parameter-driven date filter with complex fiscal quarter logic via DATEADD and DATETRUNC in a calculated field used as a filter. Live connection causes slow filter application. What optimization maximizes caching?
Use relative date filters instead of custom calc
Convert fiscal logic to a data source calculated field or extract, then use as context filter
Parameterize only the year
Switch to discrete dates
Explanation: Custom calculated date filters on live connections prevent cache reuse if logic changes per parameter. Defining fiscal periods upstream (Prep or source) and using as context filter allows consistent queries for cache hits; context filters also reduce data before other filters.
In a Performance Recording, what does a long "Query Execution" bar for a Tableau Data Extract (.hyper) usually indicate? (Select One)
The Tableau Server is out of RAM
The network latency between the user and the Tableau Server is too high
The client machine has a slow GPU
The query is too complex or the extract is not optimized (e.g., lacks indexing or has too many columns)
Explanation: 'Query Execution' measures the time taken by the data engine (Hyper) to process the request. If this is high for an extract, it suggests that the calculations are complex, the data volume is massive, or the extract includes many unused columns. Optimizing the extract by hiding unused fields and rolling up data can reduce this time.
Planning transformation for sensor data at minute level, but analysis at hour. Minimum granularity to recommend for performance and accuracy?
Machine-hour
Hour-global
Minute-machine
Day-machine
Explanation: Machine-hour aggregates appropriately for hourly trends while keeping machine context for drill or filters, optimizing storage.
A user wants to create a dashboard where clicking on a specific bar in a "Sales by State" chart will open a web browser and search for that state's government website using a dynamic URL. Which feature should be used?
Parameter action
Filter action
Data densification
URL action
Explanation: URL actions allow Tableau to point to a web page, file, or other web-based resource outside of Tableau. By using a dynamic URL action, you can insert field values (like the State name) into the URL string as a variable, so that the destination URL changes based on the specific mark selected by the user.
When translating analytical requirements into a Tableau context, which practice is essential to ensure clarity and effectiveness?
Using complex calculations without documentation
Avoiding the use of filters to simplify data
Incorporating user feedback during the design process
Relying solely on default Tableau visualizations
Explanation: Incorporating user feedback during the design process is essential for translating analytical requirements into Tableau effectively. This practice helps ensure that the final dashboards and reports meet user needs and are intuitive, ultimately enhancing user engagement and adoption.
Comparing trigger-based RLS simulation in older MySQL vs. native in modern databases for an upgrade path. In a legacy migration scenario, which factors favor native RLS?
Better performance due to optimizer awareness
Compatibility with old clients
Simpler syntax in triggers
Easier auditing with triggers
Explanation: Better performance due to optimizer awareness in native RLS. Easier auditing with triggers is false. Simpler syntax in triggers is not. Compatibility with old clients is irrelevant.
In a scenario where a finance team needs to share sensitive financial dashboards, which access control method should be prioritized?
Use a guest account for external stakeholders
Set up user groups with restricted permissions
Allow all users to edit the dashboard
Publish the dashboard to Tableau Public
Explanation: Setting up user groups with restricted permissions ensures that only authorized personnel can access sensitive financial information. Publishing to Tableau Public or using guest accounts would compromise data security.
Which administrative view is most appropriate for identifying governance risks from over-provisioned schedules causing performance degradation?
Traffic to Views
Data Connections
User Activity
Background Tasks for Schedules and Jobs
Explanation: This view monitors schedule performance, failures, and overloads, helping admins optimize for governance by preventing resource contention impacting certified content reliability.
Which of the following describes a "Group-based" RLS approach as opposed to a "User-based" approach? (Select One)
Creating a calculated field: `ISMEMBEROF('Regional_East_Managers') AND [Region] = 'East'`
Joining the sales table to a table containing every employee's unique ID
Assigning specific rows in a CSV to specific email addresses
Using the `USERDOMAIN()` function to filter data by active directory branch
Explanation: A group-based approach relies on the user's membership in a predefined set (Group) on the server. The calculation `ISMEMBEROF('Regional_East_Managers')` checks if the user belongs to that specific group. This is different from a user-based approach, which would typically involve checking a unique identifier (like a username or ID) against a specific value in the data.
Which Tableau feature allows users to visualize the impact of filters on performance?
Data Source Filters
Workbook Optimization
Performance Recording
Dashboard Actions
Explanation: The Performance Recording feature in Tableau enables users to see how filters impact performance by tracking the time taken for each query and visual element. This insight helps in optimizing filter usage for better performance.
You are implementing RLS in Azure SQL for a ticketing system, where group functions handle
department-wide access, and user functions handle assigned tickets. In a high-concurrency scenario, which differentiation ensures that group functions don't leak data to unauthorized users within the group?
Make group function return broader filter, refined by user function in a chained policy
Embed user checks within group function using SUSER_SNAME()
Define user function as SECURITY DEFINER to override group
Use SESSION_CONTEXT to flag group vs user mode and switch logic
Explanation: Embedding user checks within group function using SUSER_SNAME() prevents leaks by combining checks. Making group function return broader filter, refined by user function in a chained policy isn't supported. Using SESSION_CONTEXT to flag group vs user mode and switch logic adds complexity. Defining user function as SECURITY DEFINER to override group alters privileges incorrectly.
Transformation plan for multi-language product catalog, granularity SKU-language pair.
Compute union by language filter
External pivot
Raw with query locale
Single table with lang columns
Explanation: Compute union maintains pair granularity scalably.
A user wants advanced interactivity where hovering over a bar in a sales trend chart updates a parameter that controls a reference line on a separate forecast sheet, adjusting the threshold based on the hovered bar's value without full selection. Which action facilitates this hover-based parameter change?
Parameter action on menu
Viz in tooltip with parameter
Filter action on hover
Set action on hover
Explanation: While direct hover parameter actions aren't standard, using viz in tooltip with embedded sheets can simulate by passing values, but for true parameter update on hover, parameter actions support select/hover triggers in newer versions, but the query implies parameter action. Wait, correcting: Parameter action can be set to run on hover for dynamic updates like reference lines. Filter action on hover filters,
not params. Parameter action on menu limits to click. Set action on hover manages sets. Viz in tooltip with parameter embeds views but not direct param updates.
In a complex enterprise system using SQL Server, you need to differentiate between group-based and user-based RLS functions for a projects table. In a scenario where users inherit permissions from groups
but can have overriding user-specific rules, which syntax in the security predicate function would correctly prioritize user functions over group ones? (Select all that apply)
Use IF EXISTS (SELECT 1 FROM user_entitlements WHERE user_id = SUSER_SID() AND project_id = @project_id) THEN return user-specific filter ELSE group filter
Join user and group tables with LEFT JOIN and use ISNULL to fallback to group
Define separate policies for users and groups and enable them conditionally via session context
Implement a COALESCE in the predicate to return user_permission if not null, else group_permission
Explanation: Using IF EXISTS (SELECT 1 FROM user_entitlements WHERE user_id = SUSER_SID() AND project_id = @project_id) THEN return user-specific filter ELSE group filter allows explicit checking for overrides. Joining user and group tables with LEFT JOIN and using ISNULL to fallback to group handles prioritization efficiently. Implementing a COALESCE in the predicate to return user_permission if not null, else group_permission assumes single values, not filters. Defining separate policies for users and groups and enabling them conditionally via session context is not supported in SQL Server RLS.