A Tableau Prep flow at Brindle Freight cleans a daily shipments file and must deliver the cleaned result to two audiences: a fleet of Tableau workbooks that refresh from a single curated source on Tableau Cloud, and a finance reporting tool outside Tableau that reads a table in the company analytics database. The analyst wants both consumers served from the one flow without each Tableau workbook re-running the cleaning logic. Which two flow output types should the analyst configure? Select TWO.
- AA published data source output on Tableau Cloud, so many workbooks share one curated source that they refresh from on a schedule. Correct
- BA database table output that writes the cleaned rows into the analytics database, so the external finance tool can read the table directly. Correct
- CA local .hyper extract saved to the analyst's own laptop, so each Tableau workbook opens that single file from disk during analysis.
- DA live connection from every workbook straight to the raw shipments file, so each book applies the cleaning steps itself at view time.
- EA flow output saved as a packaged workbook, so the finance tool and the Tableau books both open the cleaned data from that one file.
Why A is correct: A published data source lets multiple workbooks draw from one curated source and refresh on a schedule without rerunning the flow.
Why B is correct: A database table output writes the result into the warehouse where non-Tableau tools such as the finance reporting tool can query it.
Why C is wrong: A local extract on one laptop is not shareable on a schedule across many workbooks, so it fails the curated shared-source need.
Why D is wrong: A live connection to raw data forces every workbook to redo the cleaning, which is exactly what the analyst wants to avoid.
Why E is wrong: A packaged workbook is not a Prep flow output type and cannot be read as a table by an external finance tool.