Free Practice Questions for the Salesforce Foundations Analytics-101 Exam (2026 Updated)

A multi-connection data source created for a cross-database join can be filtered and can also be converted to or used with an extract, making A and C correct. Cross-database joins allow Tableau to combine tables originating from different supported connections into one logical data source. Tableau supports these joins with either live connections or in-memory extracts. Consequently, the associate can create an extract of the resulting multi-connection data source. Data source filters can also be used to reduce the records Tableau brings into the analytical environment, subject to connector-specific limitations. The other two choices conflict with documented multi-connection restrictions. Tableau explicitly states that stored procedures are not available for multi-connection data sources, eliminating B. A union appends rows from structurally similar tables. In a multi-connection environment, Tableau Desktop requires tables being unioned to come from the same connection; tables from different databases cannot be unioned directly in Tableau Desktop. Therefore, D does not meet the scenario involving tables across multiple connections. Tableau's official cross-database documentation explains that a cross-database join requires a multi-connection data source, supports both live and extract-based operation, prohibits stored procedures for such sources, and limits unions to tables within the same connection.

The associate should select More under To a Server, making D correct. Tableau Desktop organizes available connectors on the Connect pane into broad categories such as To a File and To a Server. Frequently used server connectors may be displayed directly, but Tableau provides the More option to expose the complete list of supported server-based connection types available in the installation. Official Tableau connector documentation repeatedly states: For a complete list of data connections, select More under To a Server. This workflow is used when locating database and server connectors such as Microsoft SQL Server, PostgreSQL, SharePoint Lists, and other supported platforms. Selecting More under To a File instead displays file-based connection types and therefore does not satisfy a requirement specifically involving server connections. Choosing File > New creates a new workbook and does not expose the complete server connector list. "Connecting to Data" is not the command required to reveal all server options. This distinction is operationally important because the Connect pane intentionally surfaces common connector choices while More exposes the broader connector catalog. Current Tableau documentation for multiple server connectors confirms the More under To a Server workflow for viewing the complete connection list.

To create a join in a data source that already uses relationships, the associate must double-click a logical table in the canvas, making C correct. Tableau's data model has two layers. The top-level logical layer contains logical tables connected by relationships. A join cannot be created directly between these logical tables because joins operate in the underlying physical layer. Double-clicking a logical table opens its physical Join/Union canvas. From there, the associate can drag or double-click additional physical tables and define the required join clauses and join type. This distinction is fundamental to Tableau's modern data model. Relationships connect logical tables while keeping them separate and preserving their natural level of detail. Joins merge physical tables into one logical table using an explicitly defined join configuration. Selecting Add in the Connections pane adds another connection; it does not itself create the join. Dragging a table directly onto the top-level logical canvas generally creates a relationship rather than a physical join. Double-clicking a table in the Tables pane is not the step used to enter the physical layer of an existing logical table. Tableau's official documentation explicitly instructs users to double-click a logical table to open the physical layer where joins and unions can be created.

A continuous date field produces a green pill and generates an axis, making B and C correct. Tableau uses color as an immediate visual cue for discrete versus continuous fields. Green pills represent continuous fields, whereas blue pills represent discrete fields. A date can function in either form. When the analyst chooses a continuous date value such as continuous Month or continuous Year, Tableau represents the field as an unbroken temporal range rather than a finite collection of date-part headers. When this continuous date is placed on the Rows shelf, Tableau generates a continuous axis corresponding to the selected temporal granularity. The axis behaves similarly to other continuous quantitative axes in the sense that values occupy positions along an uninterrupted scale. Option A instead characterizes a discrete date part, such as discrete Month, where Tableau creates categorical headers or labels like January, February, and March. Option D is likewise associated with discrete fields because discrete pills are blue. Tableau's official Continuous Dates documentation states that continuous dates create an axis and that converting a date field to continuous causes the field to turn green. Tableau's general field-role documentation separately confirms that continuous fields create axes while discrete fields create headers.

Because the group field contains an enabled Other group, ungrouping one of the explicitly grouped members causes that member to be placed into Other. Therefore, A is correct. Tableau groups allow analysts to combine individual members of a dimension into higher-level categories. When the Include "Other" option is enabled, all members that are not assigned to one of the explicitly defined groups are collected automatically into an Other category. Tableau's official Group Your Data documentation specifically describes the behavior of removing members from an existing group. The analyst opens Edit Group, selects the member, and chooses Ungroup. Tableau removes the selected member from its current explicit group. Critically, the documentation states that if an Other group exists, the removed members are added to it. The underlying original dimension member is not deleted. However, option B is incomplete for this exact scenario because the question explicitly states that the Other group exists; Tableau does not merely leave the member ungrouped—it places it into Other. No new single-member group is automatically created, eliminating C, and removing one member does not delete the entire group, eliminating D. This behavior is central to Tableau's dimension grouping and Other-category management.

A relationship is particularly appropriate when the tables being combined contain data at different levels of detail, making D correct. Tableau relationships operate in the logical layer of the data model and preserve each logical table's native granularity. Tableau determines the necessary joins dynamically during analysis according to the fields used in the visualization. This behavior is materially different from a physical join. A join merges records into a single physical table before analysis. If tables have different granularities, a physical join can duplicate measure values or remove records depending on the join structure and matching keys. Relationships reduce that risk because Tableau aggregates relevant information according to each table's natural level of detail before combining results as required by the visualization. Official Tableau guidance explicitly recommends relationships for combining data from different levels of detail. Relationships also preserve independent logical tables rather than flattening them into a single physical table. Option B merely describes where tables reside and does not determine whether a relationship or join is preferable. Options A and C likewise do not identify the principal modeling scenario addressed by relationships. Relevant Tableau Desktop concepts include logical tables, physical tables, relationships, joins, aggregation behavior, and preservation of level of detail.

To convert the existing bar chart into a stacked bar chart, the associate should drag another dimension to Color on the Marks card. The initial bar chart already contains a dimension on Columns and a measure on Rows. Adding another categorical dimension to Color partitions each bar according to the members of that second dimension. Tableau assigns a separate color to each resulting group and, because automatic stacking is enabled for bar marks by default, those groups are displayed cumulatively within each bar. For example, if Category is on Columns and SUM(Sales) is on Rows, adding Segment to Color divides each Category bar into Consumer, Corporate, and Home Office segments while preserving the bar's total Sales magnitude. Dragging another dimension to Size changes the visual size encoding rather than creating standard stacked segments. Adding another measure to Rows typically introduces an additional axis or measure structure. A measure placed on Color generally creates a quantitative gradient rather than categorical stacked segments. Tableau's official Stack Marks documentation describes this exact construction: a dimension on Columns, a measure on Rows, and another dimension used to color-encode the marks.

Dimensions are fields Tableau uses primarily to categorize, segment, and describe data. They typically contain qualitative information such as names, geographic locations, categories, dates, and identifiers. Therefore, C is correct. Tableau also states that dimensions affect the level of detail in a visualization. Adding another dimension can partition existing marks into more granular groups because Tableau incorporates the field's members into the view's dimensional structure. Therefore, B is correct. The dimension/measure classification is independent from the discrete/continuous classification. Although dimensions are commonly discrete, a dimension can also be continuous. Date fields are a standard example: a date may be represented as a discrete date part or a continuous date value. Therefore, E is correct. Option D instead describes measures, which generally contain quantitative numeric values and are aggregated. Option A is not an inherent defining characteristic of dimensions; formatting behavior depends on how a field is used and whether it is discrete or continuous. Official Tableau guidance identifies dimensions as qualitative fields that group or segment data and explicitly states that dimensions affect the level of detail in the view.

Double-clicking a continuous numeric measure such as Sales in an empty Tableau worksheet automatically produces a bar chart, making C correct. Tableau uses intelligent defaults when fields are double-clicked in the Data pane. With a single measure and no dimensions already defining the view, Tableau aggregates the measure—normally using its default aggregation such as SUM—and adds it to the visualization. The Automatic mark type resolves to a bar, producing a single bar representing the aggregated Sales value. Tableau's official documentation provides this exact construction using the Profit measure. It states that double-clicking Profit automatically adds the field to the view in an intelligent way, and the documented resulting visualization is a bar chart of Profit. Sales is the same type of field—a quantitative measure—so the same automatic-view rule applies. A line chart ordinarily requires an ordered dimension such as a date field to provide a sequence across which values can be connected. A pie chart requires additional categorical structure for meaningful segmentation. A text table is generally created when a dimension is double-clicked first and subsequent fields refine that cross-tabular structure. Therefore, a lone continuous numeric measure double-clicked in a new worksheet produces the automatic single-measure bar visualization.