Salesforce Analytics-101 Practice Exam Questions & Answers

Tableau provides direct single-click sorting controls from a header, an axis, and a field label, making A, C, and D correct. Tableau's official Sort Data in a Visualization documentation explicitly identifies these three locations. When the user hovers over an appropriate header, numerical axis, or field label, Tableau can display a sort icon. One click typically applies descending sorting, a second click changes it to ascending, and another interaction can clear the sort depending on context. A header is commonly generated by a discrete field and can expose sorting for its members. A numerical axis allows the associated categorical members to be sorted according to measure values. A field label can similarly provide direct sorting when applicable to the view's structure. The Tooltip area of the Marks card controls information displayed when the pointer hovers over a mark; it is not a sorting interface. The Worksheet and Analysis menus contain numerous authoring commands but are not the three direct locations identified by Tableau's single-click sorting workflow in this question. Official Tableau documentation specifically states: 'Quickly sort from an axis, header, or field label,' precisely matching A, C, and D.

The three applicable routes are Tooltip on the Marks card, Format > Font, and Worksheet > Tooltip, so C, E, and F are correct. Selecting Tooltip on the Marks card opens the Edit Tooltip dialog. This editor contains text-formatting controls that allow tooltip content to be formatted, including the application of bold styling to selected text. Tableau also provides an equivalent route through Worksheet > Tooltip, which opens the same tooltip-editing environment for the current worksheet. A third route is through Format > Font. Tableau's worksheet-level font formatting includes a specific Tooltip section. This enables formatting of tooltip text at the worksheet level, including font style settings such as bold. This method is useful when a consistent tooltip font treatment is required rather than individually formatting portions of the tooltip body. The keyboard sequences listed in A and D are not defined Tableau methods for accessing tooltip formatting options merely by hovering over a mark. Right-clicking an arbitrary field and selecting Format is primarily associated with field/view formatting and is not the specified route to the tooltip bolding controls in this question. Official Tableau documentation confirms both Tooltip on the Marks card and Worksheet > Tooltip, while current Font formatting documentation exposes Tooltip as a configurable font target.

A story point is an individual visualization state within a Tableau story, normally represented by a worksheet or dashboard. Therefore, A is correct. Tableau defines a story as a sequence of visualizations that collectively communicate information, provide context, demonstrate relationships, or support a data-driven narrative. Each individual sheet contained in that sequence is called a story point. A story can contain multiple points, and each point can present a different worksheet, dashboard, filter state, annotation, or analytical stage. Option C describes the overall story, not an individual story point. The distinction is important: the story represents the complete ordered narrative, while the story point represents one step within that narrative. Option B is not an official Tableau object or definition. Option D refers to controls within the story workspace and does not define a story point. This functionality allows an analyst to guide viewers through findings in a controlled sequence while preserving interactive visualization capabilities where supported. Official Tableau Desktop documentation explicitly states that a story is a collection of sheets arranged in sequence and that each individual sheet in a story is called a story point.

A Relative dates filter is designed for date ranges that dynamically change relative to the current date, making B correct. This filter can represent periods such as the current week, previous month, year to date, or the last specified number of days, weeks, months, quarters, or years. The important distinction is that a relative date filter is dynamic. As the current date advances, Tableau recalculates the applicable range when the view is opened or refreshed. This behavior is appropriate for requirements based conceptually on TODAY() because the filter should continue tracking the present period rather than retaining fixed start and end dates. A Range of dates filter establishes a specific date interval and is better suited to fixed boundaries. A Starting Date or Ending Date represents an open-ended boundary from a particular date rather than a dynamically shifting interval relative to today. Tableau's official documentation states that relative date filters dynamically update to display a time period relative to when the view is opened. Examples include the current week, year to date, or past ten days. This functionality allows analysts to create dashboards that consistently display the most recent period without manually editing the filter as calendar time progresses. Relevant topics include date fields, relative date filtering, dynamic analysis, and interactive filter configuration.

Tableau provides three principal scope levels for reference lines: Entire Table, Per Pane, and Per Cell. Therefore, A, B, and D are correct. Scope determines the partition of the visualization over which Tableau calculates and displays the reference line. Entire Table computes one reference value based on all applicable marks in the view. This is appropriate for a global benchmark such as overall average Sales. Per Pane creates a separate reference line for each pane. For example, if a visualization is partitioned by Region, Tableau can calculate an independent average for each regional pane. Per Cell is still more granular and can calculate a separate reference line for each cell defined by the row and column structure of the view. Maximum is not a scope; it is a possible statistical value or computation that can be used to determine the reference-line value. Similarly, Fill Above concerns formatting or shading behavior associated with analytical reference objects and does not define the calculation scope. Official Tableau documentation explicitly states that the terms Table, Pane, and Cell define the scope for reference lines and related analytical objects. These options control whether the benchmark applies globally or independently to specific partitions of the visualization.

For a standard custom latitude field, Tableau recommends a Number (decimal) data type and a Measure data role. Therefore, A and B are correct. Latitude represents a numeric coordinate, including fractional values such as 40.7128, so Number (decimal) is the appropriate data type. Treating latitude as a measure enables Tableau to position coordinate values continuously on an axis rather than interpreting each coordinate as an independent categorical member. Tableau's official mapping guidance states that, in most cases, latitude and longitude fields should have a data type of Number (decimal), a data role of Measure, and the corresponding Latitude or Longitude geographic role. When used in a map, Longitude is normally placed on Columns and Latitude on Rows as continuous measures. This differs from geographic fields such as Country, State, or City, which are usually string dimensions. Although specialized mapping scenarios can convert latitude or longitude to dimensions, that is not the standard configuration addressed by this question. The official Tableau mapping documentation explicitly specifies the Number (decimal) + Measure configuration for latitude and longitude fields when preparing geographic data for mapping.

Tableau dashboard actions can directly change Parameters and Sets, so B and C are correct. A parameter action allows a user to modify a parameter value by interacting directly with marks in a visualization. For example, selecting a mark can assign the mark's Sales value to a parameter, which can subsequently drive a calculated field, reference line, filter logic, or another analytical component. Tableau provides the dashboard action type Change Parameter specifically for this purpose. A set action similarly modifies the membership of an existing set based on interaction with marks. The action can assign selected values to the set, add values, or remove values. This enables sophisticated interactive behavior such as proportional brushing, dynamic comparisons, drill-down effects, and conditional calculations. Tableau identifies this action type as Change Set Values. Groups and bins do not have equivalent dashboard action types that dynamically modify their definitions through viewer interaction. They are data organization constructs configured during authoring. The Tableau Actions documentation explicitly lists Change Parameter and Change Set Values among supported action types. Parameter Actions documentation confirms that visualization interaction can update the target parameter, while Set Actions documentation confirms that interactions can modify values contained in a target set.