Free Analytics-Con-301 sample questions

Correct answer: Tableau will keep the tables separate and perform context-aware aggregations at runtime, preventing measure duplication.

Relationships (the 'noodle' connections in the Logical Layer) differ from physical joins. They do not merge tables into a single flat table immediately. Instead, Tableau queries them independently at the appropriate level of detail during analysis, ensuring that measures from the 'Targets' table (monthly) are not duplicated for every row in the 'Sales' table (transactional).

Correct answer: Change the 'Region' filter to a Context Filter.

In Tableau's Order of Operations, Dimension Filters are applied *after* Top N filters. This means the Top 10 are calculated on the entire dataset first, and then the Region filter hides rows. By adding the Region filter to Context, it moves up the pipeline (before Top N), ensuring the Top 10 are calculated *within* the filtered subset. flowchart TD A[Extract Filters] --> B[Data Source Filters] B --> C[Context Filters] C --> D[Fixed LODs] D --> E[Top N Filters] E --> F[Dimension Filters] style C fill:#f9f,stroke:#333,stroke-width:2px style E fill:#bbf,stroke:#333,stroke-width:2px

Correct answers: Using a specific join type (like Full Outer Join) that is not supported by the Relationship heuristics for the given data source.; Implementing Row-Level Security (RLS) using a join to an entitlement table that results in row duplication (Row Multiplication).

While Relationships support most join logic, specific requirements for a forced Full Outer Join or specific join clauses often require dropping into the Physical Layer.

RLS often relies on 'exploding' rows when a user has multiple roles or entitlements (Row Multiplication), which is a behavior of physical joins. Relationships attempt to preserve the native level of detail and avoid duplication, which can break RLS models dependent on row multiplication.

Correct answer: AVG({FIXED [Customer Name] : SUM([Sales])})

This expression first calculates the total sales for each customer (inner aggregation) regardless of the view level, and then the outer aggregation (AVG) averages those customer totals based on the dimensions in the view (Region).

Correct answer: False

False. Tableau Prep (and Desktop) Wildcard Union is permissive. If columns do not match, it will union the matching columns and create nulls for the mismatched columns in the respective rows. It does not fail immediately; it creates a superset of all columns.

Correct answer: Use a FIXED LOD expression for the readmission flag: {FIXED [Patient ID] : COUNT([Admission ID])} > 1. Keep 'Hospital Wing' as a normal Dimension filter.

A FIXED LOD expression is calculated *before* Dimension filters (unless they are in Context). By using {FIXED [Patient ID]...}, Tableau calculates the total admissions for the patient across the entire dataset. When the user filters by 'Hospital Wing', the view is filtered, but the patient's classification as 'Readmitted' remains consistent based on their global history.