Analytics-DA-201 - Publish and Manage Content on Tableau Server and Tableau Cloud (9% of the exam) - Section 4.1
Publish workbooks, data sources, and Prep flows from Desktop or Prep, and export content.
Practice question for this objective
lock_openFree samplePublish and Manage Content on Tableau Server and Tableau Cloudeasy
Which statement correctly describes what a Tableau Prep flow produces when its output step is configured to write to a published data source on Tableau Cloud?
AIt publishes the flow's design canvas so that other authors can open and edit the cleaning steps directly in their browser.
BIt writes the cleaned, shaped data to a data source that workbooks can connect to and refresh on a schedule.check_circle Correct
CIt exports a static image of the flow's results that consumers download and open in spreadsheet software.
DIt converts the flow into a live connection straight to the original raw files, bypassing the cleaning steps.
A Prep flow output to a published data source writes cleaned data that workbooks connect to and a schedule keeps refreshed. The output step runs the flow's transformations and writes the resulting rows to a published data source, which becomes the governed, refreshable input that downstream workbooks query.
Why A is wrong: Writing to a published data source outputs the cleaned data; sharing the editable flow design is a separate action of publishing the flow itself, not the data output.
Why B is correct: Sending a flow output to a published data source stores the transformed data centrally so workbooks connect to it and a scheduled flow run keeps it current.
Why C is wrong: An output to a published data source creates queryable data, not a downloadable picture; static images relate to exporting a view, not a flow output.
Why D is wrong: The whole point of the flow is to apply the cleaning steps; the output reflects the transformed result, not an unprocessed live link to the raw inputs.
Exam traps in Publish and Manage Content on Tableau Server and Tableau Cloud
Answers that look right on this material and are not. Each one is a distractor from a different question in the Analytics-DA-201 bank for this domain.
An output to a local .hyper file saved on the analyst's machine, so the result sits in a folder for manual reuse.
errorWhy it is wrong: A local file output keeps the result on one machine and is not centrally connectable, so multiple workbooks on Tableau Cloud could not refresh from it on a schedule.
A separate packaged workbook for each report, each embedding its own copy of the connection.
errorWhy it is wrong: Embedding a private copy of the connection in every workbook is tempting for simplicity, but it duplicates the model so there is no single shared place for naming and calculations to be governed.
Each individual workbook, scheduling them separately so every one carries its own refresh.
errorWhy it is wrong: Scheduling each workbook separately duplicates effort and, where the data is in a shared published source, still would not be the single run the team wants, so it misses the point of one central refresh.