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
When using a data source that has relationships, how can a Tableau associated add a join between two or more tables?
Answer(s): A
A is correct because double-clicking a logical table opens that table’s physical layer where you can add explicit joins between the physical tables that compose the logical table.Tableau separates the logical (relationship) layer from the physical (join) layer: relationships are managed at the logical canvas and preserve table-level context, while joins are defined among physical tables. Double-clicking a logical table drills into its physical representation, exposing the physical tables and join editor so the analyst can create, edit, or combine joins within that logical table scope. This approach is the intended, supported workflow for turning relationship-linked tables into joined tables without changing the overall logical model — a subtle but important distinction on the exam. Using the physical canvas ensures join types, keys, and join clauses are set explicitly and are applied when Tableau needs a flattened, physical result for a given query.Why the other choices are incorrect:B: From the Tables pane, double-click a table — double-clicking a table in the Tables pane adds that table to the logical canvas (creates or adds a logical table/relationship), it does not open the physical join editor for composing joins among physical tables. C. From the Connections pane, select Add — adding a connection creates an additional data source or connection, not a join between existing tables within the current logical/physical model. D. From the Tables pane, drag a table on top of an existing logical table — dragging a table onto the logical canvas typically establishes a relationship (logical-level link). To create a physical join between physical tables you must open the logical table’s physical layer (double-click) and define the join there.References: https://help.tableau.com/current/pro/desktop/en-us/multiple_connections_relationships.htmhttps://help.tableau.com/current/pro/desktop/en-us/joining_tables.htmhttps://help.tableau.com/current/pro/desktop/en-us/data_model.htm
References: https://help.tableau.com/current/pro/desktop/en-us/multiple_connections_relationships.htmhttps://help.tableau.com/current/pro/desktop/en-us/joining_tables.htmhttps://help.tableau.com/current/pro/desktop/en-us/data_model.htm
What are three ways to access bolding options for the text in a tooltip? (Choose three.)
Answer(s): D,E,F
DEF are correct because Tableau exposes text-formatting controls for tooltips via the Tooltip editor (accessible from the Marks card or Worksheet menu) and via the Format → Font controls, all of which include bolding options.Reasoning: Clicking Tooltip on the Marks card or choosing Worksheet → Tooltip opens the Tooltip editor, which includes a rich-text toolbar with bold, italic and font controls for tooltip text; this is the primary,contextual way to format individual tooltip content. The Format → Font command opens the Format pane where you can target fonts for different sheet elements (including tooltips) and apply bold/weight changes at the sheet or workbook level, providing a second, global access point to change tooltip text appearance. Together these three UI entry points (Tooltip on Marks, Worksheet → Tooltip, and Format → Font) are documented Tableau mechanisms for applying bolding to tooltip text and are the exam-expected answers.Why the other choices are incorrect:A: Hover + CTRL+B: Not a documented or supported shortcut for toggling bold in the tooltip editor; Tableau’s tooltip editor uses on-screen formatting controls rather than a universal Ctrl+B hotkey. B. Hover + ALT+F: ALT+F is typically the Windows menu accelerator for the File menu and is not a Tableau command for opening tooltip formatting or toggling bold. C. Right-click Field → Format: That action opens field- or axis-specific formatting panes (formatting for axis, headers, or marks) but does not directly open the tooltip editor or the tooltip-specific bold control used to edit tooltip text content.References: https://help.tableau.com/current/pro/desktop/en-us/tooltips.htmhttps://help.tableau.com/current/pro/desktop/en-us/formatting_fonts.htmhttps://help.tableau.com/current/pro/desktop/en-us/formatting_tooltips.htm
References: https://help.tableau.com/current/pro/desktop/en-us/tooltips.htmhttps://help.tableau.com/current/pro/desktop/en-us/formatting_fonts.htmhttps://help.tableau.com/current/pro/desktop/en-us/formatting_tooltips.htm
A Tableau associate has the following visualization.Where should the associate place a field named Region to show multiple distinct lines on the same axis?
D. Color on the Marks card.To create multiple distinct lines on the same axis in Tableau, you must add a dimension to the Marks card that breaks the data into separate series.
Which type of chart can a Tableau associate create without using a dimension?
Answer(s): C
C is correct because Tableau will render a bar mark from a single aggregated measure (placed on Rows or Columns) without requiring any dimension to partition the view.Reasoning: Tableau separates fields into dimensions (discrete partitioning) and measures (aggregates); when only a measure is placed on an axis Tableau produces an aggregated numeric axis and a single mark (or continuous axis of marks) whose mark type can be set to Bar, yielding a valid bar chart without any dimension. This behavior follows Tableau’s aggregation and mark-generation rules: marks are created from the combination of discrete pills (dimensions) and continuous pills (measures), and a lone continuous pill still defines a valid quantitative mark. From an exam perspective, the minimal construct for a bar is therefore a measure + mark type = bar; additional dimensions only segment or color the bars. Creating stacked or segmented bars, treemaps, or highlight tables requires discrete partitioning (one or more dimensions) because those visual forms depend on categorical subdivision to create multiple cells, rectangles, or stack segments.Why the other options are incorrect:A: Highlight table — requires at least one dimension for rows or columns so cells can be formed and colored by a measure; a lone measure yields a single aggregated value, not a tabular grid of highlights. B. Treemap — is a space-filling hierarchical representation that depends on one or more dimensions to define rectangles (hierarchy/groups) sized by a measure; without a dimension there is no hierarchy or multiple rectangles to render. D. Stacked bar — requires a discrete field (dimension or discrete measure) to partition the bar into stacked segments (typically placed on Color or Columns/Rows); a single measure alone cannot produce stacked segments.References https://help.tableau.com/current/pro/desktop/en-us/buildviews_bar.htmhttps://help.tableau.com/current/pro/desktop/en-us/visual_analysis_highlight_tables.htmhttps://help.tableau.com/current/pro/desktop/en-us/visual_analysis_treemap.htm
What is a Tableau story point?
D is correct because a story point is an individual worksheet or dashboard saved as a discrete “slide” within a Tableau Story.A story point encapsulates the visual state (worksheet or dashboard), accompanying caption and navigation position so authors can present a narrative by sequencing these discrete visual states; it is the atomic unit that a Story composes, preserving filters, marks and layout for that step. In practice authors create multiple story points to guide viewers through an analytical argument, while the Story container provides sequencing, layout and navigation controls. Story point behavior differs from dashboards and worksheets only in that it references them as a snapshot for storytelling rather than being a workspace for analysis. This distinction is why D is the best, exam-focused definition: it maps directly to Tableau’s terminology where each point is a saved view used in the Story sequence.Why the other options are incorrect:A: Incorrect — story size is a Story-level property (the Story pane or Story options control size), not the definition or role of a story point. B. Incorrect — a collection of sheets arranged in sequence describes the Story as a whole, not a single story point; the Story is the sequence composed of multiple story points. C. Incorrect — while a story point may include a caption or talking points, it is not defined as a collection of talking points; it is a single view (worksheet or dashboard) used to present one step of the narrative.https://help.tableau.com/current/pro/desktop/en-us/stories.htmhttps://help.tableau.com/current/pro/desktop/en-us/buildstories.htmhttps://www.tableau.com/learn/articles/data-storytelling
A Tableau associate is creating a combined axis chart. Where should the associate drag the second measure after dragging the first measure to the Rows shelf?
A is correct because dropping the second measure onto the vertical axis (the Rows shelf axis) places both measures on the same continuous coordinate system, creating a combined axis with a single shared scale.Placing measures onto the Rows shelf binds them to the same orthogonal dimension (vertical axis) so Tableau overlays their values on one continuous scale rather than creating separate panes; this is the semantic and operational definition of a combined-axis view in Tableau’s rendering model. The Tableau interface provides explicit visual feedback (axis highlight) for the correct drop target, and when both measures occupy the same axis they inherit the same aggregation and axis domain unless explicitly edited — producing a single, directly comparable encoding of magnitude. This differs from dual-axis composition (two independent scales sharing the same pane), which is produced through different placement and axis-specific commands; combined axes require alignment to the same shelf/axis. The Rows/Columns shelf semantics map directly to vertical/horizontal axes respectively, so the axis object in the view is the deterministic target for combining measures.B: The horizontal axis in the view — incorrect because that corresponds to the Columns shelf and would orient measures horizontally (or place the second measure on a different shelf), not combine them on the vertical (Rows) axis. C. The Filter card — incorrect because dropping a measure on Filters constrains data values rather than positioning the measure as an axis or encoding its scale in the view. D. The Marks card — incorrect because the Marks card controls mark attributes (color, shape, size, label, detail) and encodings, not axis placement; placing a field on Marks encodes visual properties but does not create or combine axes.https://help.tableau.com/current/pro/desktop/en-us/dual_combined_axes.htmhttps://help.tableau.com/current/pro/desktop/en-us/shelves_cards.htmhttps://help.tableau.com/current/pro/desktop/en-us/marks_card.htm
Share your comments for Salesforce Certified Tableau Desktop Foundations exam with other users:
AWESOME and Thanku
Question 24:Question 24 asks which three actions are needed to set up intercompany accounting between two legal entities. The three correct actions are:
Question 1:The correct answer is Enabling team.
Question 1:
Question 1:The best solution is A: Configure a SetupComplete.cmd batch file in the %windir%\setup\scripts directory. Why this is correct:
SetupComplete.cmd
%windir%\setup\scripts
Question 9:Question 9 asks about how GitHub Copilot identifies public code matches when the public code filter is on.
Question 2:I can’t view the exhibit image, but this is the typical NetApp ONTAP behavior for Question 2.
Question 23:Question 23 describes a multimodal model where users can upload unsafe images that could contain hidden instructions. The goal is to implement controls to mitigate this risk. Key points to understand
beautiful exams
You need to implement the date dimension in the data store. The solution must meet the technical requirements. What are two ways to achieve the goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point. Populate the date dimension table by using a dataflow. Populate the date dimension table by using a Copy activity in a pipeline. Populate the date dimension view by using T-SQL. Populate the date dimension table by using a Stored procedure activity in a pipeline.Please answer
Question 14:
Question 5:Question 5 asks how to identify min and max values for each column in a Dataflow result. Correct options: B and E.
Question 18:Question 18: Why not A?
Question 4:Question 4 is about when to use batch processing.
Question 5:I can’t see the [Image] in Question 5, but I can explain the likely reasoning.
Question 12:Here’s why Question 12’s correct choices are C and D.
Question 3:Question 3 asks for two valid ways to meet the purchase order creation validation (warn if the vendor is on the exclusion list for the customer/product and block/alert accordingly). Correct answers: C and D
Question 12:Here’s how to understand question 12.
Question 6:Here’s how question 6 works. Key constraint: All new and extended objects must be in an existing model named FinanceExt. Creating a brand-new model is not allowed. Why the two correct options work:
Question 2:I don’t have the text for Question 2 here. Please paste the exact Question 2 (including all answer choices) or describe the topic it covers. Once I have it, I’ll:
Which statement is true about using default environment variables? The environment variables can be read in workflows using the ENV: variable_name syntax. The environment variables created should be prefixed with GITHUB_ to ensure they can be accessed in workflows The environment variables can be set in the defaults: sections of the workflow The GITHUB_WORKSPACE environment variable should be used to access files from within the runner.Correct answer: The statement "The GITHUB_WORKSPACE environment variable should be used to access files from within the runner." is true. Why the others are false:
${{ env.VARIABLE }}
$VARIABLE
GITHUB_
defaults:
run
GITHUB_WORKSPACE
${{ github.workspace }}
$GITHUB_WORKSPACE/...
${{ github.workspace }}/...
As an administrator for this subscription, you have been tasked with recommending a solution that prohibits users from copying corporate information from managed applications installed on unmanaged devices. Which of the following should you recommend? Windows Virtual Desktop. Microsoft Intune. Windows AutoPilot. Azure AD Application Proxy.
Question 34:
Policy
function of appnav in sdwan
Question 5:
Why this is correct
Question 7:
Question 104:
clustering keys
Q23: Fabric Admin is correct. Because Domain admin cannot create domains. Only Fabric Admin can among the given options. Q51: Wrapping @pipeline.parameter.param1 inside {} will return a string. But question requires the expression to return Int, so correct answer should be @pipeline.parameter.param1 (no {})
Question 62:
ZDX
Analyze Score
Y Engine
Question 32:
Question 3:
date = sys.argv[1]
sys.argv[1]
date = spark.conf.get("date")
input()
date = dbutils.notebooks.getParam("date")
dbutils.notebook.run
Keeping this site free takes real effort. We constantly battle automated scraping and unauthorized content copying. A quick account helps us protect the community and keep the site free.
To continue studying for your Certified Tableau Desktop Foundations, please sign in or create a free account.