What are two correct methods for creating a visual group? (Choose two.)
Answer(s): A,C
A and C are correct because dragging one dimension onto another in the Data pane creates a combined field (a visual grouping of dimensions) and selecting marks in the view allows creation of a member-based group tied to the visualization.Combined fields (created by dragging a dimension onto another) produce a single discrete field that visually aggregates the component dimensions for partitioning and shelf placement, which is a UI-level grouping construct distinct from source-level changes. Selecting marks in the view and using the Group command forms a member-level group that consolidates specific mark values into a single logical category while preserving underlying data fidelity—this is the canonical visual grouping workflow for mark-based aggregation. Both approaches are explicit, supported Tableau UI workflows that create visual groupings without modifying the original data source schema. Recognizing the distinction between structural combined fields and mark-level groups is essential for correct exam-level reasoning about where and how grouping occurs in the Tableau interface.Option B — Incorrect: right-clicking a dimension only opens the context menu; a subsequent explicit action (for example Create → Group) is required to produce a group, so the mere act of right-clicking is not itself a method of creating a visual group.Option D — Incorrect: the Data pane drop-down governs pane management and display options and does not provide a direct single-step command to create visual groups; grouping is performed via field/context menus or by interacting with the view.https://help.tableau.com/current/pro/desktop/en-us/groups.htmhttps://help.tableau.com/current/pro/desktop/en-us/combine_fields.htmhttps://help.tableau.com/current/pro/desktop/en-us/data_pane.htm
Which string function return a Boolean values as a result?
Answer(s): C
C is correct because STARTSWITCH (Tableau's STARTSWITH) is a predicate that tests a string prefix and returns a Boolean TRUE/FALSE.STARTSWITH is designed as a Boolean-returning predicate used directly in calculated fields, filters, and conditional expressions to indicate whether the target string begins with the specified substring. From a type-theory and calculation-design perspective, predicate functions produce logical values that control flow and filtering without needing additional comparison operators. In contrast, the other options are transformation or extraction functions that yield non-Boolean types and therefore cannot serve as direct logical predicates.Critical evaluation of the other options (structured):A: CHAR — returns a single-character string corresponding to a numeric code; its return type is string, not Boolean. B. FIND — returns the numeric index (integer) position of a substring or 0 when not found; its return type is integer and requires comparison (e.g., >0) to become a Boolean. D. UPPER — returns the input string converted to uppercase; its return type is string, not Boolean.Exam strategy takeaway: identify verbs that denote predicates (STARTSWITH, CONTAINS, ISNULL, etc.) as Boolean-producing, and distinguish them from functions that transform or extract strings/numbers which require an explicit comparison to yield Boolean semantics.https://help.tableau.com/current/pro/desktop/en-us/functions_functions_string.htmhttps://help.tableau.com/current/pro/desktop/en-us/functions.htmhttps://help.tableau.com/current/pro/desktop/en-us/calculations_calculatedfields.htm
What are two outcomes when a Tableau associate drags a continuous date value to the Rows shelf? (Choose two.)
Answer(s): C,D
Because a continuous date is treated as a continuous field in Tableau, it appears as a green pill and generates a continuous (quantitative) axis when placed on Rows.Reasoning: Tableau uses color-coded pills to distinguish data-role semantics—green indicates continuous (measure-like) behavior and blue indicates discrete (categorical/header) behavior; a continuous date inherits the continuous semantics and thus the green pill denotes an axis-based, quantitative scale with range and tick marks rather than discrete headers. This continuous axis behavior permits numeric axis operations (aggregation across a numeric domain, axis editing, range and tick formatting) that are not available when dates are placed discretely. In practice, switching a date to continuous changes the mark-placement model from header/grid to an analytic, continuous coordinate system, producing the quantitative axis described in option C and the green pill described in option D.Why the other options are incorrect:A: The pill is blue — incorrect because blue denotes discrete/date-part behavior; continuous dates are green and do not render as blue pill headers. B. The date part is disabled as labels — incorrect because date parts and exact date modes remain available via the pill’s context menu or field type conversion; you can switch between discrete date parts and continuous date ranges and still label or format dates as needed.https://help.tableau.com/current/pro/desktop/en-us/discrete_continuous.htmhttps://help.tableau.com/current/pro/desktop/en-us/dates.htmhttps://help.tableau.com/current/pro/desktop/en-us/axes.htm
What are three geographic roles that a Tableau associate can assign to a field? (Choose three.)
Answer(s): A,C,D
ACD is correct because Tableau’s built-in geographic role list includes City, Country (Country/Region), and Airport as discrete roles that Tableau uses for geocoding and map rendering.Reasoning (compact, exam-focused): Tableau geographic roles are a taxonomy that maps textual field values to spatial locations so the engine can resolve latitude/longitude and place marks on maps; City, Country/Region, and Airport are explicitly supported roles with internal geocoding tables (including airport IATA/ICAO codes) and therefore are appropriate choices for the associate exam. Assigning one of these roles instructs Tableau to interpret the field as place-level geography (enabling map layers, geographic hierarchies, and spatial joins) rather than as generic strings. Selecting an appropriate geographic role improves match rates in Tableau’s geocoder and avoids ambiguous or incorrect point placement that would occur if the field were left as a plain dimension.Critical evaluation of the other options:B — Time zone: Incorrect. Time zone is temporal/offset metadata (used to express UTC offsets and daylight-saving behavior) and is not part of Tableau’s geographic role set used for geocoding or map placement. E — Address: Incorrect in this exam context. While full postal addresses can be used to derive location through external geocoding or by splitting into country/state/city/postal components, “Address” is not treated as a primary predefined geographic role in Tableau’s standard role list for built-in geocoding on the Desktop Foundations exam.References (authoritative Tableau documentation):https://help.tableau.com/current/pro/desktop/en-us/maps_assign_roles.htm https://help.tableau.com/current/pro/desktop/en-us/maps_geocoding.htm https://help.tableau.com/current/pro/desktop/en-us/maps.htm
To which type of element can a Tableau associate apply a default aggregation?
Answer(s): D
D is correct because Tableau’s default-aggregation property is a metadata-level summarization attribute that applies to quantitative fields categorized as measures.Tableau’s data model distinguishes discrete categorical fields (dimensions) from continuous quantitative fields (measures); default aggregation (SUM, AVG, MIN, etc.) is stored and applied automatically for measures when they are placed in a view, because aggregation is the operation that reduces numeric values across the view’s level of detail. Default aggregation is semantically meaningful only for numeric, aggregable data and is therefore implemented as a measure property in the data pane. Measures are evaluated and aggregated at query time according to that metadata, which is why the exam expects the simple rule: default aggregation → measures.Why the other options are incorrect:A: Dimensions — incorrect: dimensions are grouping keys (discrete) used to slice data, not numeric quantities to be summarized by a default aggregation, so Tableau does not expose a default-aggregation property for them. B. Calculated columns that are aggregated — incorrect as stated: while a calculated field that yields a numeric measure can have a default aggregation assigned, the option’s wording conflates two concepts; expressions that already contain aggregate functions are evaluated at aggregate levels and are not the target of Tableau’s “default aggregation” setting in the general case. C. Binned values — incorrect: bins create discrete intervals (treated like dimensions) derived from measures, and the bin itself is a categorical partitioning rather than a numeric field to which a default aggregation is applied.References https://help.tableau.com/current/pro/desktop/en-us/data_default_properties.htmhttps://help.tableau.com/current/pro/desktop/en-us/data_fields.htmhttps://help.tableau.com/current/pro/desktop/en-us/bins.htm
Post your Comments and Discuss Salesforce Certified Tableau Desktop Foundations exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Certified Tableau Desktop Foundations content, but please register or login to continue.