Salesforce Certified Tableau Next Consultant Analytics-Con-202 Exam Questions

Answer : A

Full Refresh is required when the accelerated Tableau Next cache must reflect records that were deleted in the external source. Salesforce documentation distinguishes the two acceleration modes explicitly. An Incremental Refresh adds or updates records that changed after the previous refresh, but it does not update deleted records.

By contrast, a Full Refresh removes all previously cached data during each refresh cycle and replaces it with a newly retrieved copy of the current source dataset. If a source record has been deleted, it no longer exists in the replacement dataset and consequently disappears from Tableau Next.

Incremental refresh can operate as frequently as every 15 minutes, making it attractive for high-frequency changes, but that frequency does not alter its deletion limitation. If deletion synchronization is a requirement, the architecture must account for periodic or continuous full-refresh behavior according to supported refresh intervals.

''Snapshot refresh'' is not one of the documented Tableau Next Acceleration refresh methods for this use case.

This is the same architectural principle tested earlier: Incremental = added/changed data; Full = complete cache replacement, including removal of deleted source records.

Reference/Topics: Data Setup -> Acceleration for Data Connections -> Cache Refresh Method -> Full versus Incremental Refresh.

===========================================================================

Answer : A

Semantic Data Models are specifically intended to establish standardized, reusable definitions for analytical concepts and metrics. Salesforce describes Tableau Semantics as a semantic layer that maps data to familiar business terminology and standardized logic so information can be interpreted consistently across Salesforce. Semantic models become a single source of truth for metrics, calculations, relationships, dimensions, and other analytical definitions.

Therefore, if several business units must calculate and interpret a metric consistently, the correct architecture is to define that KPI through the governed semantic model rather than recreating logic independently in each dashboard or workspace.

Workspace-level color palettes address visual presentation and branding rather than analytical definitions. Dashboard templates can standardize dashboard structure and reuse assets, but they do not provide the authoritative semantic definition layer required to guarantee that the same business metric has the same meaning everywhere.

Salesforce explicitly states that semantic models are first-class Salesforce metadata and can power analytics and data-driven experiences throughout Data 360 and Tableau Next. This reusable semantic architecture prevents divergent metric logic from developing between departments.

Reference/Topics: Data Setup -> Tableau Semantics -> Semantic Data Models -> Metrics -> Standardized Business Logic -> Single Source of Truth.

===========================================================================

Answer : A

A parameter is a user-controllable variable that can influence calculations, filtering, reference lines, and other interactive analytical behavior. Salesforce documents parameters as a mechanism for modeling scenarios and allowing dashboard users to provide inputs that affect analytical results. Parameters can be created for different data types and then referenced by calculated fields or dashboard controls.

For example, an organization could define a parameter named Target Discount and allow a user to enter 15%. A calculated field could then compare actual discount values with the parameter and dynamically change the resulting visualization. Tableau Next also supports parameter widgets that accept manually entered values or derive dynamic values from dashboard queries.

Option B incorrectly describes semantic-model relationship configuration. Relationships between DMOs are defined through relationship metadata and cardinality rather than parameters. Option C confuses parameters with governance and authorization controls.

The certification distinction is: parameters provide variable analytical input; calculated fields consume that input; semantic relationships define object connectivity; Data 360 governance controls security.

Reference/Topics: Data Setup -> Semantic Models -> Parameters -> Calculated Fields -> Interactive Scenario Modeling.

===========================================================================

Answer : A

Data Lake Object (DLO) is the correct answer among the available choices. A Data 360 Batch Data Transform requires an Output node where the transformed results are persisted. Salesforce documents that a Batch Data Transform can write its results to a new or existing target Data Lake Object, which can subsequently serve as input to identity resolution, calculated insights, segmentation, semantic modeling, or additional transforms.

A Data Stream Object is not the destination used to persist transformed output. Data streams provide ingestion pipelines that bring source data into Data 360. A Semantic Data Model is also not the physical output storage target; Tableau Semantics consumes governed Data 360 objects to provide measures, dimensions, relationships, calculations, and business context.

Reference/Topics: Data Setup -> Data 360 -> Batch Data Transforms -> Output Nodes -> Data Lake Objects.

===========================================================================

Answer : B

Tableau Next provides generative AI capabilities that translate a user's natural-language description of a calculation into a calculated-field formula. This directly addresses scenarios where an analyst understands the required business logic but lacks familiarity with Tableau Next formula syntax.

With Draft with Einstein, the user describes the calculation they need in natural language. Einstein can propose the field name, description, data type, aggregation type, and formula. The agentic calculated-field experience also supports conversational refinement, allowing the user to explain requirements and respond to clarification questions before reviewing the proposed field.

A batch transform, as described in A, is a data-preparation mechanism and is unrelated to helping an analyst overcome formula-authoring syntax problems. C is less accurate because the defining generative-AI capability being tested is the transformation of natural-language analytical intent into a proposed formula.

The generated output remains subject to user review before creation, preserving human control over the final semantic definition while substantially reducing formula-authoring friction.

Reference/Topics: Agentic Experiences -> Generative AI -> Draft with Einstein/Data Pro -> Natural-Language Calculated Fields.

===========================================================================

Answer : B

For a live Tableau Next preview inside a Slack canvas, Salesforce instructs users to paste the Tableau Next asset URL into the canvas and select Card from the Paste As menu. The resulting card can display a metric, dashboard, or visualization and regularly refresh its underlying data.

This behavior differs materially from sharing a static Tableau Next preview in an ordinary Slack channel or direct message. In a Canvas, Salesforce retrieves the data from each viewer's perspective. Consequently, each person must have appropriate Tableau Next access to the underlying asset and data. Unauthorized users receive an access message instead of seeing protected data. This preserves individual data governance while still providing a rich collaborative experience.

Option A does not describe the documented Slack Canvas workflow. Option C produces a static image and therefore fails the requirement for regularly refreshed information.

The exam distinction is important: standard Slack message preview = snapshot governed by sharing behavior; Slack Canvas Card = live, refreshable preview evaluated against each viewer's access.

Reference/Topics: Embedding, Cross-Cloud, and Interoperability -> Tableau Next in Slack -> Slack Canvas -> Paste As Card -> Viewer-Based Data Access.

===========================================================================

Answer : A

Data Kits are a native supported deployment mechanism for moving Tableau Next assets from a sandbox to a production Data 360 home org. Salesforce explicitly states that Tableau Next workspaces, visualizations, and dashboards can be deployed through Data Kits, and that Data 360 semantic models on which those analytical assets depend must also use Data Kits for deployment to target home orgs.

CSV export/import is a data-transfer technique, not a Tableau Next metadata lifecycle-management mechanism. It cannot preserve dashboard structure, visualization definitions, semantic-model dependencies, workspace metadata, or the relationships between these assets. Manual recreation would be operationally inefficient, prone to configuration drift, and unnecessary when supported deployment tooling exists.

A technically complete implementation must also account for dependency sequencing. When a Data Kit contains the semantic model and downstream Tableau Next content, Salesforce requires the publishing order to be at least Semantic Models -> Workspaces -> Visualizations -> Dashboards.

Reference/Topics: Managing Workspaces and Orgs -> Sandbox Development -> Data Kits -> Production Deployment -> Asset Dependencies.

===========================================================================