Connect to files, relational databases, extracts, and published data sources, choose between live connections and extracts, and replace the data source for an existing sheet.

An analyst finishes a dashboard built on a development extract file and now needs it to run against a published data source on Tableau Server that exposes an identically structured table. They open Replace Data Source and choose the published source as the replacement. Which detail most determines whether every worksheet keeps working after the replace?

• AWhether the original development extract and the published source share the same file path on disk, so Tableau can relink the .hyper location.
• BWhether the replacement source contains exactly the same number of rows as the development extract, so the row counts reconcile during the replace.
• CWhether the analyst first converts the published source back to a live connection, because replace cannot target a published data source.
• DWhether the published replacement source exposes field names that match those the worksheets and calculations already reference, so the references resolve cleanly.check_circle Correct

Why A is wrong: A published data source has no local file path to match; replace works by remapping field references, not by aligning extract file locations.

Why B is wrong: Row counts are irrelevant to whether references resolve; replace cares about matching fields, and views happily show whatever rows the new source returns.

Why C is wrong: A published data source is a valid replacement target, and no conversion is needed; the deciding factor is field-name matching, not connection type.

Why D is correct: Replace Data Source remaps references by matching field names; when the replacement exposes the same field names, worksheets and calculations bind to them and keep working.