Preparation20% of the exam
Data connections, drivers and published data sources
How Tableau Server reaches data: the repository port and direct connection path, which nodes need database drivers, file versus relational versus cube sources, live versus extract query execution, the Run As account, and why published data sources help administrators.
1.8 Data Source Identification: 1.8.1 Identify the ports required; 1.8.2 Identify the necessary database drivers; 1.8.3 Understand the differences between: 1.8.3.1 File vs. Relational vs. Cube, 1.8.3.2 Extract vs. Live Connections; 1.8.4 Explain the benefits of published data sources.
~8 min read · 8 practice questions
What the exam expects
- Identify the ports and connection path used to reach the Tableau Server repository, including behind a load balancer.
- Identify which nodes need database drivers and how to replace a driver safely.
- Classify a connection as file-based, relational or cube, and state what cube sources cannot do on Server.
- Contrast live and extract connections, including which engine answers the queries.
- Explain the benefits and editing restrictions of published data sources, and the Run As account's role in reaching data.
Key terms:
- Database driver: software a Tableau connector needs to talk to the database.
- Cube (multidimensional, OLAP) data source: a source whose hierarchies and aggregations were built in advance by its designer.
- Extract: a compressed snapshot of data saved separately from the original source and queried by the Data Engine.
- Published data source: a data connection shared on Tableau Server that other workbooks connect to.
- Run As service account: the Windows account Tableau Server runs as when it accesses resources.
Key facts
Repository port
- Detail
pgsql.port, default 8060; databaseworkgroup
Not in
list-ports- Detail
- 8060 and 8061 are not dynamically mapped
Apache load balancer
- Detail
- Custom admin views connect directly to the repository
Driver nodes
- Detail
- Initial node plus nodes running Application Server, Backgrounder, Data Server or VizQL
Driver updates
- Detail
- Stop Server first (recommended, not always required)
Cube definition
- Detail
- Hierarchies and aggregations created in advance
Cube on Server
- Detail
- Stored and downloadable; no pass-through, no new workbook
Extract queries
- Detail
- Answered by the Data Engine (Hyper)
Published source updates
- Detail
- All connected workbooks pick up changes
Default Run As
- Detail
- NT Authority\Network Service
Sources for this section (8)
- Collect Data with the Repositoryhelp.tableau.com (opens in a new tab)
- TSM Portshelp.tableau.com (opens in a new tab)
- Add a Load Balancerhelp.tableau.com (opens in a new tab)
- Database Drivershelp.tableau.com (opens in a new tab)
- Cube Data Sourceshelp.tableau.com (opens in a new tab)
- Tableau Server Data Enginehelp.tableau.com (opens in a new tab)
- Tableau Server Data Sourceshelp.tableau.com (opens in a new tab)
- Run As Service Accounthelp.tableau.com (opens in a new tab)
- Why does downloading a workbook that connects to an extract-based published data source reduce network traffic?
- Why is custom SQL a reason to prefer an extract?
- When does Tableau prompt you to extract a text file?
- On which Tableau Desktop platform are cube data sources supported?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Tableau Server Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 34 lessons of the Tableau Server Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both