A Tableau associate needs to display the complete list of potential data connections when connecting to a server. Which action should the associate perform?
Answer(s): B
B is correct because the Tableau Desktop Connect pane exposes the full set of server and cloud connectors only when you expand the "More" option under "To a Server."Reasoning: Tableau’s UI semantically partitions connectors into "To a File" and "To a Server"; the "More" control under "To a Server" is the explicit affordance to enumerate all supported server endpoints (Tableau Server/Online, cloud warehouses, managed databases and ODBC/JDBC targets). From an information-architecture perspective, this preserves a concise start experience while enabling deterministic discovery of enterprise connectors when expanded. For exam purposes, selecting "More" under "To a Server" is the required procedural step to verify connector availability, required drivers, and authentication options before attempting a connection or troubleshooting access. This choice directly corresponds to Tableau’s documented workflow for server connections and aligns with practical deployment checks in enterprise environments.Why the other options are incorrect:A — Select More under To a File: incorrect because that control only expands file-format connectors (Excel, text, spatial, statistical files) and does not list server or cloud connection types. C — Select File on the menu, and then select New: incorrect because creating a new workbook does not itself expose the complete connector catalog; you still must open the Connect pane and expand the appropriate category. D — Select Connecting to Data: incorrect/ambiguous because merely opening the general "Connect" area or a shortcut may show common entries but does not guarantee the full, explicit enumeration of server connectors that is revealed by "More" under "To a Server."References: https://help.tableau.com/current/pro/desktop/en-us/connect_to_data.htmhttps://help.tableau.com/current/pro/desktop/en-us/startpage.htmhttps://help.tableau.com/current/pro/desktop/en-us/connecting_to_servers.htm
References: https://help.tableau.com/current/pro/desktop/en-us/connect_to_data.htmhttps://help.tableau.com/current/pro/desktop/en-us/startpage.htmhttps://help.tableau.com/current/pro/desktop/en-us/connecting_to_servers.htm
A Tableau associate has the following legend.What occurs when the associate clicks the icon to the right of Air Ticketing Cabin Type Name?
Answer(s): A
A. The highlighter toggles on or off. In Tableau, clicking the icon to the right of a legend title (such as Air Ticketing Cabin Type Name) activates or deactivates the data highlighting feature. This icon, which often resembles a small highlighter or light bulb, allows users to hover over or click items in the legend to highlight corresponding marks in the visualization while dimming unrelated data.
A Tableau associate has a data set that builds a union between two tables. The associate needs to extract the data set. What should the associate use to extract the data set?
Answer(s): C
Why C is correct: Because a union is executed at Tableau’s physical-table level and produces a single consolidated physical table that is extracted as a single-table extract.In Tableau’s logical/physical data model, unions concatenate rows from multiple inputs into one physical table; the extract engine materializes that unified physical table into a single .hyper extract rather than preserving separate table extracts. This single-table extract aligns with database principles of physical-materialization and enables Tableau optimization (columnar storage, compression, and in-extract query planning) on the flattened row set. From an exam and practical perspective, recognize that “union” implies physical-level row concatenation → single physical table → single-table extract.Why the other options are incorrect:A — Incorrect: Logical tables (relationships) are a different abstraction that keep tables separate and can produce multi-table logical queries; they do not represent union behavior or guarantee a single-table extract. B — Incorrect: Multiple physical-table extracts would imply separately materialized physical tables; a union removes that separation by combining rows into one physical table, so multiple extracts are unnecessary and inconsistent with a union. D — Incorrect: Logical tables with multiple-table extracts describe relationship-driven, multi-table extraction scenarios, not a physical union that yields a single consolidated extract.References: https://help.tableau.com/current/pro/desktop/en-us/data_model.htmhttps://help.tableau.com/current/pro/desktop/en-us/unions.htmhttps://help.tableau.com/current/pro/desktop/en-us/extracts.htm
References: https://help.tableau.com/current/pro/desktop/en-us/data_model.htmhttps://help.tableau.com/current/pro/desktop/en-us/unions.htmhttps://help.tableau.com/current/pro/desktop/en-us/extracts.htm
Which type of date filter can a Tableau associate use to choose a range of dates based on TODAY ()?
Because the Relative Dates filter type lets you define moving windows anchored to TODAY(), it directly supports dynamic ranges like “last N days/months” or “next N periods.”Reasoning: Relative date filters operate on the semantics of continuous date values and compute membership relative to a moving reference point (TODAY()), enabling automated, reproducible filtering for reporting and dashboards without manual adjustment. This filter type exposes granular options (days, weeks, months, quarters, years) and modes (last, next, or relative to a specific boundary) that are evaluated at render time, which is essential for time-series reporting and freshness checks. From an implementation perspective, using TODAY() as the anchor yields time-variant predicates that are evaluated by Tableau’s query planner against the data source, whereas static filters would require manual updates or scheduled parameter changes. For exam purposes, the key distinction is that “relative” denotes dynamism tied to a temporal anchor (TODAY()), while other names imply static endpoints or explicit range selection.Why the other options are incorrect:A: Starting date — This implies choosing a fixed lower bound; it does not by itself create a dynamic, TODAY()-anchored window and therefore cannot express “last N days” without additional logic. C. Range of dates — This is a manual slider or fixed start/end selection for absolute date spans; it creates a static interval rather than a moving window driven by TODAY().D: Ending date — Like Starting date, this designates a fixed upper bound; it does not provide the relative, anchor-based semantics required for TODAY()-driven ranges.References: https://help.tableau.com/current/pro/desktop/en-us/dates_relative.htmhttps://help.tableau.com/current/pro/desktop/en-us/filtering.htmhttps://help.tableau.com/current/pro/desktop/en-us/dates.htm
References: https://help.tableau.com/current/pro/desktop/en-us/dates_relative.htmhttps://help.tableau.com/current/pro/desktop/en-us/filtering.htmhttps://help.tableau.com/current/pro/desktop/en-us/dates.htm
What are two methods for renaming a field in a visualization? (Choose two.)
Answer(s): A,C
AC is correct because Tableau’s Data pane supports both the field drop-down “Rename” command and direct in-place editing via click-and-hold, which are the standard, supported mechanisms for changing a field’s name in a workbook.Reasoning: Renaming a field is a metadata change at the workbook/data-pane level, and Tableau exposes that capability through the field context menu (drop-down → Rename) for explicit, discoverable edits and through an in-place edit affordance (click-and-hold or pause on the name) for rapid, modal editing; both produce the same metadata update and propagate the new label to views that reference the field. From an expert perspective, these two methods are functionally equivalent but differ in interaction pattern (contextual command vs direct manipulation), which is why both are tested as valid exam responses. Renaming is distinct from aliasing or view-level label edits: it changes the field identifier shown in the Data pane and across the workbook (unless later overridden in a specific axis/header).Why the other options are incorrect:B — Format menu, Field Labels: The Format menu controls visual styling (font, alignment, shading) of labels and headers, not the underlying field name in the Data pane; it does not provide a Rename operation. D — Replace References: Replace References substitutes one field for another throughout a workbook (to rewire dependencies), it does not edit the textual name of an existing field; using Replace References changes references, not the metadata label.References https://help.tableau.com/current/pro/desktop/en-us/data_rename_fields.htmhttps://help.tableau.com/current/pro/desktop/en-us/formatting.htmhttps://help.tableau.com/current/pro/desktop/en-us/calculations_replace_references.htm
Post your Comments and Discuss Salesforce Certified Tableau Desktop Foundations exam prep with other Community members: