Study guide
12.1 Certification, Data Quality, Lineage & Permissions
Salesforce Certified Tableau Data Analyst Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Connecting to Data & The Logical Data Model
1.1 Data Connections: Live Connections vs. Hyper Extracts 1.2 The Tableau Data Model: Relationships vs. Physical Joins 1.3 Combining Data: Data Blending vs. Cross-Database Joins
2 Chapter 2: Tableau Prep Builder & Data Wrangling
2.1 Tableau Prep Architecture & Data Cleaning 2.2 Reshaping Data in Prep: Pivots, Splits & Wildcard Unions 2.3 Joins, Aggregations & Output Destinations in Prep
3 Chapter 3: Data Quality, Metadata & Field Configuration
3.1 Data Types, Roles, Organization & Default Properties 3.2 In-Desktop Data Cleaning: Splits, Data Interpreter & Source Replacement 3.3 Managing Slowly Changing Dimensions & Data Quality Warnings
4 Chapter 4: Tableau Fundamentals & Calculations
4.1 Dimensions vs. Measures & Discrete vs. Continuous 4.2 Mastering Dates: Discrete Date Parts vs. Continuous Date Truncations 4.3 Calculations: Logic, Strings, Nulls & Type Conversion 4.4 Aggregation Rules, Granularity & Dealing with the Asterisk (ATTR)
5 Chapter 5: Level of Detail (LOD) Expressions
5.1 Level of Detail Architecture & Scoping Syntax 5.2 FIXED LOD Expressions: Scoping & Baseline Benchmarks 5.3 INCLUDE & EXCLUDE LOD Expressions: Dynamic Granularity 5.4 Real-World LOD Patterns: Cohorts, First/Last Dates & Binning
6 Chapter 6: Table Calculations & Directionality
6.1 Table Calculation Mechanics: Addressing vs. Partitioning 6.2 Essential Table Calculations: Running, Window & Percent of Total 6.3 Navigation & Ranking Functions: LOOKUP, INDEX & RANK 6.4 Secondary & Nested Table Calculations: Multi-Level Scoping
7 Chapter 7: Statistical Analytics, Filtering & Order of Operations
7.1 The Tableau Order of Operations: From Extract to Display Filters 7.2 Sets, Set Actions & Combined Sets vs. Groups 7.3 Parameters, Parameter Actions & Dynamic What-If Analysis 7.4 Analytics Pane: Totals, References, Trends & Forecasts
8 Chapter 8: Chart Types & Comparative Visualizations
8.1 Comparison Visualizations: Bar Charts, Highlight Tables & Bullet Graphs 8.2 Part-to-Whole & Correlation Charts: Treemaps, Scatter Plots & Bubbles 8.3 Trend & Distribution Visualizations: Dual-Axis, Combos & Histograms
9 Chapter 9: Advanced Visualizations & Spatial Analysis
9.1 Specialized Visualizations: Waterfall, Gantt, Sparklines & Bump Charts 9.2 Spatial Data & Mapping: Geographic Layers & Spatial Functions 9.3 Visual Polish: Custom Palettes, Annotations & Viz in Tooltip
10 Chapter 10: Dashboard Design & Interactive Actions
10.1 Dashboard Layout, Devices & Visibility 10.2 Filter, Highlight & URL Actions 10.3 Advanced Interactivity: Parameter, Set & Navigation Actions 10.4 Stories & Visual Storytelling: Sequencing Analytical Narratives
11 Chapter 11: Tableau Server & Cloud: Architecture & Publishing
11.1 Tableau Server & Cloud: Sites, Projects, Roles & Permissions 11.2 Publishing Workbooks, Data Sources & Flows
12 Chapter 12: Data Governance, Security & Operations
12.1 Certification, Data Quality, Lineage & Permissions 12.2 Row-Level Security, Schedules, Subscriptions & Alerts
12.1 Certification, Data Quality, Lineage & Permissions
Key Takeaways Explain This Topic AI
Administrators can certify data sources, as can eligible Creator or Explorer (Can Publish) users who are project owners or Project Leaders.
Certification is a trust signal, not a security rule or a guarantee that current data has no issues.
Data quality warnings communicate current risk without changing data or permissions.
Catalog lineage supports impact analysis for discovered upstream and downstream dependencies.
Locked projects centralize permission rules; effective access still depends on site-role ceilings and explicit rules.
Last updated: September 2026
12.1 Certification, Data Quality, Lineage & Permissions
Governance helps users distinguish trusted content, understand dependencies, and act on warnings without assuming that every published asset is equally authoritative. Certification, data quality warnings, lineage, ownership, and permissions solve different problems.
Certification
A certified data source carries a visible trust indicator and a note identifying who certified it. Certification communicates organizational approval; it does not freeze the asset, prove every value correct forever, or grant access. Consumers still need permission to connect.
The authority to certify a data source is broader than only administrators. A Server or Site Administrator can certify. A Creator or Explorer (Can Publish) can also certify when that user is the project owner or has the Project Leader capability for the project containing the asset. A person who merely owns a data source, without the required project authority or administrator role, cannot necessarily certify it. Governance questions should test both site role and project authority.
Certification can be removed when an asset no longer meets standards. Establish review criteria such as documented ownership, validated definitions, refresh health, security review, and a recertification cadence. Avoid multiple indistinguishable certified sources for the same business concept.
Data quality warnings
A data quality warning communicates a condition such as stale data, maintenance, deprecation, or another important status. High-visibility warnings can surface on downstream content so consumers understand risk before acting. A warning does not modify rows, repair a failed refresh, or replace permissions. Resolve the operational issue separately and clear or update the warning when the status changes.
Certification and warnings can coexist. A generally trusted source may carry a temporary maintenance warning. Certification answers whether the organization endorses the asset; the warning answers whether a current condition deserves attention.
Lineage and impact analysis
Tableau Catalog, when licensed and configured, indexes supported external assets and Tableau content to show upstream and downstream relationships. Starting from a database column, a steward can inspect dependent tables, published data sources, flows, workbooks, and sheets that Catalog recognizes. Starting from a workbook, the steward can trace its sources. This supports impact analysis before renaming or deleting an upstream field.
Lineage is evidence about discovered dependencies, not a guarantee that every external script or unsupported connection has been captured. Confirm the environment's coverage. Before a schema change, identify downstream owners, inspect calculations that use the field, communicate the change, apply an appropriate warning, and retest after deployment.
Ownership, project leadership, and permissions
Ownership usually grants management capabilities for content, subject to the site's rules, role ceiling, and project policy. Project Leaders administer content within a project. Administrators have broader scope. These concepts are not interchangeable: owning a workbook does not make a user a Site Administrator, and being able to publish does not automatically grant certification authority.
In a locked project, content uses the project-level permission rules. This limits asset-level exceptions and makes group-based governance predictable. In a customizable project, eligible users can set child rules. Effective access combines the user's site role with group and user permission rules. An explicit Deny can override an Allow for the same capability. Use Tableau's effective-permissions explanation instead of guessing from one group membership.
Governed-source workflow
Place the asset in the intended project and assign an accountable owner.
Grant Connect, View, Web Edit, Save, and download capabilities only to appropriate groups.
Document fields, calculations, refresh policy, and data-quality checks.
Have an authorized administrator, project owner, or Project Leader review certification criteria.
Add a certification note that explains the scope and contact.
Use Catalog lineage before upstream changes and notify downstream owners.
Apply high-visibility warnings for current issues such as maintenance or deprecation.
Periodically review permissions, ownership, refresh health, warnings, and certification.
Scenario distinctions
If users cannot find a trusted source, improve naming, descriptions, project placement, and certification. If an upcoming column removal may break workbooks, use lineage and impact analysis. If data is temporarily unreliable, use a warning. If a contractor can see too much, repair permissions or row-level security; a warning is not access control. If a capable author cannot certify, inspect whether they are a project owner or Project Leader before assuming an administrator is the only solution.
Good governance combines clear signals with enforceable controls. Trust indicators help users choose; permissions and security determine what they may do; lineage helps stewards predict consequences; operational monitoring keeps the trust signal deserved.