Free Practice Questions for the Salesforce Consultant Analytics-Con-202 Exam (2026 Updated)

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.

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

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

A Logical View is the correct feature when the consultant needs to combine multiple data objects through an explicitly defined join and expose the resulting structure as a single reusable semantic object. Salesforce defines a logical view as a data object that combines multiple underlying objects using joins or unions rather than standard semantic relationships. The resulting logical view can then participate in relationships, calculated fields, metrics, and other semantic definitions as though it were an ordinary data object.

This distinction is fundamental. A standard relationship keeps the participating objects logically separate and describes how Tableau Semantics should traverse between them during query generation. It does not materialize their joined structure into one abstract semantic object. A Calculated Insight is used for more advanced Data 360 calculations and aggregations and does not represent the semantic-model join construct required here.

When configuring a Logical View, the consultant defines the participating objects, join criteria, join type—including an inner join when required—and appropriate cardinality. Correct join and cardinality configuration prevents duplicate or missing analytical results.

References/Topics: Data Setup - > Tableau Semantics - > Logical Views - > Joins - > Cardinality.

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

The documented limitation of Tableau Next Incremental Refresh for accelerated external connections is that it does not process deleted records. Salesforce states that an incremental refresh updates cached data with records that have been added or changed since the previous refresh, but deleted source data is not updated in the cache.

Consequently, options B and C are incorrect. Inserts are specifically part of incremental processing, as are updates to existing records. The limitation applies only to deletions.

This matters architecturally when data freshness requirements include removal of records. If the external source deletes a transaction, customer, product, or other row, repeated incremental refreshes can leave the old cached representation present. A Full Refresh is required to reconcile the cache completely because full refresh deletes the existing cached dataset and replaces it with a fresh source dataset.

Consultants should therefore choose refresh mode based on more than refresh frequency. Incremental refresh is efficient and can run frequently, but Full Refresh is required when complete source-state reconciliation, including deletions, is a business requirement.

References/Topics: Data Setup - > Data Acceleration - > Incremental Refresh - > Full Refresh - > Deleted-Record Handling.

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

A Data Stream Object (DSO) is the output associated with streaming data ingestion in this question. Streaming ingestion is designed to continuously accept incoming records from a connected source and represent that stream in Data 360 so downstream processing and analytics can work with newly arriving data with minimal delay.

A Data Lake Object is used as a persisted data-layer object for broader ingestion and storage scenarios, while a Semantic Model is a downstream analytical abstraction that defines business-friendly measures, dimensions, relationships, metrics, and other semantic logic. Neither option describes the streaming-ingestion output requested by this item.

The exam distinction is to keep the ingestion pipeline separate from the semantic layer. Streaming data first enters through the streaming/data-stream construct, where the Data Stream Object represents the incoming stream. That data can then participate in downstream mapping, modeling, and Tableau Next analytics. The semantic model does not serve as the raw ingestion target; it consumes prepared and governed data structures to provide analytical meaning.

References/Topics: Data Setup - > Streaming Data Ingestion - > Data Stream Objects.

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

The Conversations tab is specifically designed to expose related Slack discussions associated with Tableau Next analytical assets. When a Tableau Next metric, dashboard, or visualization is shared in Slack, users can open its preview and select Conversations to browse related Slack channels, threads, or direct-message discussions that they are authorized to access.

This directly addresses the scenario: sales and marketing are already discussing the same analytical content, but those discussions are fragmented. Surfacing related conversations in the asset context enables teams to discover existing dialogue instead of unknowingly creating duplicate parallel threads.

Option A changes how metrics are surfaced but does not address visibility into conversations already occurring around those metrics. Option C creates yet another broadcast mechanism and does not consolidate or expose existing contextual discussions.

A key design point is that Slack permissions continue to apply. The Conversations tab does not reveal conversations that the current user is unauthorized to access. Instead, it creates analytical context across conversations the user can already legitimately view, preserving Slack security while improving cross-team awareness.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next in Slack - > Related Conversations - > Conversations Tab.

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

The fundamental purpose of Tableau Semantics is to establish consistent, governed business definitions that can be reused across analytical and AI experiences. Salesforce describes semantic models as the place where organizations define and govern business metrics, relationships, dimensions, calculations, and familiar business terminology.

This means sales and service teams can use the same authoritative definitions rather than implementing independent calculations within each dashboard. For example, concepts such as Annual Recurring Revenue, Case Resolution Time, Customer Lifetime Value, or Gross Margin can be defined centrally and then reused across dashboards, metrics, Tableau Agent conversations, and other Data 360-powered experiences.

Option B is far too narrow. Semantic models can support efficient query generation, but their primary benefit is not merely dashboard rendering performance.

Option C is also incorrect. Tableau Next inherits RLS and other governance controls from Data 360 security policies; a semantic model does not automatically create record-level security simply by existing.

The exam principle is: Tableau Semantics = reusable, centrally governed meaning, ensuring humans, dashboards, metrics, and AI reason from the same business definitions.

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

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

The additional requirement is to enable Slack for Tableau Next, represented by option B's Collaboration with Slack and Tableau Next setting. Salesforce's current administrative workflow requires Salesforce and Slack to be connected and the Collaborate with Slack and Tableau Next option enabled in Tableau Next Administration.

For proactive alerts specifically, Salesforce states that an administrator must enable Slack for Tableau Next and configure Agentforce in Slack. Once properly configured, Inspector Proactive Data Alerts can deliver notifications into Tableau Next and Slack when a user-defined metric condition is satisfied.

Assigning a generic “Slack User” permission set is not the documented Tableau Next prerequisite in this scenario. Users instead require an eligible Tableau Next permission set and access to the relevant asset. Likewise, a separate analytics agent created specifically for Slack is not required merely to receive Inspector alerts.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Slack Integration - > Inspector Proactive Data Alerts - > Collaborate with Slack and Tableau Next.

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

The consultant must enable Template Builder in Tableau Next Administration. Salesforce describes Template Builder as the functionality that allows users to convert existing Tableau Next dashboards into standardized, reusable templates that can subsequently be made available through the Tableau Next Marketplace.

The administrative workflow is explicit: navigate to Tableau Next - > Administration - > Settings - > General, and enable Template Builder. Once enabled, eligible dashboard authors can use the Generate Template action to transform a dashboard into a configurable template. They can then define supporting metadata, configuration steps, descriptions, and preview information.

Tableau Next Auditing has an entirely different function: it captures user-interaction activity for governance and monitoring. It does not enable dashboard templating. “Templated Data 360 Home Org Operations” is not the documented switch for converting dashboards into Tableau Next templates.

References/Topics: Basic Setup and Admin - > Administration Settings - > Template Builder - > Tableau Next Marketplace.

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

Tableau Next MCP sessions operate using the OAuth-authenticated identity of the individual user, so B is correct. The external MCP client does not become the authoritative security boundary. Instead, Tableau Next continues to enforce Salesforce/Tableau permissions and governance while exposing analytical capabilities to the external AI environment.

Salesforce's Tableau Next MCP documentation explicitly states that MCP sessions use OAuth-authenticated users and that permissions and restrictions associated with the user's profile apply to the MCP session. Tableau user permissions, semantic-model definitions, and Trust Layer protections therefore remain effective when the user accesses Tableau Next through an external MCP-compatible client.

Salesforce's broader hosted-MCP architecture follows the same principle: tools enforce per-user authentication and standard Salesforce security controls rather than granting universal access based on connector configuration.

This design preserves governance across interoperability boundaries: Tableau Next remains the governed analytical source, while the external client functions as another interaction surface.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Integrate Analytics Across Platforms - > Tableau Next MCP Server - > Permissions and Governance.

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

The correct mapping is Dynamic Widget Field with a Selection interaction because the flow input must depend specifically on a value that the user selects in another dashboard widget. Salesforce distinguishes two dynamic interaction types when mapping dashboard data to Salesforce Flow inputs: Selection and Result. A Selection interaction passes the value resulting from the user's selection in a widget, whereas a Result interaction passes a value derived from the widget query results.

A Static String would supply the same manually configured value every time and therefore cannot satisfy a requirement in which the flow input changes according to what the user clicks.

Operationally, the consultant configures the Salesforce Flow action, identifies the required flow input, selects Dynamic Widget Field, chooses the source widget and field, and sets the interaction type to Selection. This creates an actionable analytical experience where a user's interaction with dashboard data can directly feed contextual values into a Salesforce business process.

References/Topics: Visualizations and Dashboards - > Analyze and Share Data - > Add Single-Click Actions to Your Data - > Salesforce Flow Actions.

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

The most effective improvement is to ensure that time dimensions and metric semantics are clearly and correctly defined. Tableau Agent's Data Analysis capability natively supports trend analysis, period-over-period comparisons, and date filtering, including year, quarter, month, week, day, fiscal periods, and relative date ranges.

For a question such as “How has customer satisfaction trended this quarter compared to last?”, Tableau Agent must identify the correct customer-satisfaction measure or metric, understand its business definition, and resolve which date dimension establishes the comparison period. Clear metric descriptions and correct temporal metadata therefore materially improve query generation and response consistency.

Option A could create redundant semantic logic because Tableau Agent already supports period-over-period reasoning natively. A dedicated “Quarter over Quarter” calculated field is unnecessary unless there is genuinely specialized business logic that differs from the standard comparison. Option C is also inappropriate: Salesforce already provides trend and period-over-period capabilities through the Data Analysis subagent.

Well-designed semantic models—not unnecessary proliferation of specialized agents—are the primary mechanism for improving grounded conversational analytics.

References/Topics: Agentic Experiences - > Tableau Agent - > Trend Analysis - > Period-over-Period Questions - > Semantic Model AI Readiness.

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

A Creator license is required to set proactive alerts for pipeline metrics in the scenario described. Creating an alert is more than passive consumption: the user defines a monitored condition, configures when that condition should trigger, and establishes an ongoing analytical action against the governed metric. Those capabilities fall within the Creator-level analytical configuration persona.

A Consumer can view and interact with published analytical content but does not receive the complete authoring and configuration privileges associated with creating alert definitions. The Viewer choice is even more limited and does not provide the required proactive-alert setup capability. Therefore, assigning Creator access is the appropriate licensing decision for users who must establish their own alerts.

The broader certification principle is to align licenses with the user's intended role. Users who only consume metrics should remain on the consumption tier, while users who need to create or configure analytical behavior—including proactive alert definitions—require the higher authoring entitlement. This separates governance and cost while ensuring that only appropriately licensed users can create monitoring rules.

References/Topics: Agentic Experiences - > Proactive Data Alerts - > Creator License Requirements.

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

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.

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

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

Optimize Model is the feature designed to assess semantic models for AI readiness and recommend improvements. Salesforce describes Semantic Model AI Optimization as evaluating model quality, diagnosing problems, and supplying guided remediation that improves reliability for Tableau Agent. After the feature is enabled, an Optimize Model indicator appears in Semantic Model Builder and shows the model's AI-readiness strength.

Opening the Optimize Model panel provides a breakdown of AI-readiness indicators together with recommended corrective actions. The rating is recalculated as the semantic model changes, allowing consultants to iteratively improve metadata, structure, and agent compatibility.

Q & A Calibration serves a different purpose: it tests representative natural-language questions and helps calibrate how Tableau Agent responds. Business Preferences provide explicit business context and rules, such as how ambiguous terminology should be interpreted. Neither performs the automated holistic readiness evaluation described in the question.

References/Topics: Data Setup - > Semantic Model AI Optimization - > Optimize Model - > AI-Readiness Strength - > Recommended Actions.

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

Tableau Next row-level security should be implemented through Data 360 governance policies, making B correct. Salesforce explicitly states that for Data 360 DLOs and DMOs, record-level security is defined through Data 360 policies. Tableau Next dashboards and visualizations built on those objects then inherit the enforced data visibility.

For example, the account dataset can include an attribute identifying the responsible territory or regional manager. A Data Governance access policy can evaluate the current user's relevant attributes and restrict returned records accordingly. Because security is enforced below the semantic and visualization layers, the same rules consistently protect dashboards, metrics, Tableau Agent queries, and other downstream consumers.

Option A describes the traditional Tableau USERNAME() pattern, but current Tableau Next guidance explicitly states that native user functions such as USERNAME() aren't the preferred/current RLS implementation for this architecture. Option C creates serious scalability, maintenance, and consistency problems and violates centralized governance principles.

The architectural rule is: define security as close to the governed data layer as possible so every downstream analytical experience inherits the same policy.

References/Topics: Data Setup - > Data 360 Governance - > Row-Level Security - > Access Policies - > Data Object Security.

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

The Tableau Next Analytics Embedding SDK supports an AnalyticsAgent component with both single-context and multi-component operating modes. In Multi-Component mode, the application omits the contextConfig property. The agent then automatically tracks the embedded AnalyticsDashboard and AnalyticsMetric components present on that page.

Therefore, B directly describes the intended architecture for a portal containing multiple analytical components.

Option A describes single-context mode, where contextConfig explicitly binds the agent to one dashboard, metric, or semantic model. That mode exists but is not a platform limitation. Option C introduces a same-semantic-model restriction that the current Embedding SDK documentation does not impose. The SDK explicitly describes automatic context tracking across embedded dashboard and metric components.

This capability is particularly important in embedded analytics because it allows conversational analytics to understand the broader analytical surface rather than forcing the external application to continually rebind the agent as users move between embedded components.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next Embedding SDK - > AnalyticsAgent - > Multi-Component Mode.

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

Batch Data Transforms are designed to perform repeatable data-shaping operations before downstream analytical consumption. Salesforce describes batch transforms as canvas-based processing flows capable of adding, manipulating, joining, aggregating, filtering, and applying formulas or other transformations to data before writing the resulting dataset to a target object.

This makes A the appropriate solution when the requirement involves multiple structural transformations—such as pivots, aggregations, and calculations—before the resulting dataset becomes part of a semantic model.

Identity Resolution solves a different problem: reconciling and matching records across data sources to build unified profiles. It does not provide the generalized transformation pipeline required here.

Calculated fields can create derived values, but they are insufficient when the preparation requirement involves broad reshaping and aggregation of the underlying dataset. The transformations should occur at the Data 360 data-preparation layer, after which the output object can be used by downstream analytics.

Batch transforms can write to supported DLO or DMO output nodes depending on the source and design, providing a persistent transformed object that semantic modeling and other Data 360 processes can consume.

References/Topics: Data Setup - > Data 360 - > Batch Data Transforms - > Aggregate, Join, Transform, and Output Nodes.

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

Tableau Agent's conversational analytics depends on an AI-ready Tableau semantic model, making A correct. Salesforce positions Tableau Semantics as the governed business layer between connected Data 360 sources and analytical or AI consumption experiences. Semantic models define standardized measures, dimensions, relationships, calculations, metrics, terminology, and business context that Tableau Agent uses to interpret natural-language questions.

For Snowflake data, the consultant establishes an appropriate Data 360 connection—including supported zero-copy federation where appropriate—and exposes the required Snowflake data through Data 360. The consultant then builds and prepares a semantic model containing the marketing concepts that Tableau Agent must analyze. Salesforce's Tableau Agent implementation guidance explicitly requires determining the required data, connecting it through Data 360, and creating suitable semantic foundations before configuring conversational analytics.

CSV export is unnecessary and creates an avoidable duplicate dataset. Building dashboards directly in Snowflake also does not establish Tableau Agent's governed semantic context.

The architecture is therefore: Snowflake - > Data 360 connectivity - > Tableau Semantic Model - > Tableau Agent - > Conversational Analytics.

References/Topics: Data Setup - > Snowflake Integration - > Data 360 - > Tableau Semantics - > AI-Ready Semantic Models.

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

For agent-specific business context about how Gross Margin % should be understood or interpreted, Business Preferences are the best choice. Salesforce uses Business Preferences to add organization-specific knowledge and instructions to a semantic model so Tableau Agent can interpret users' analytical questions according to the organization's terminology and business logic.

A calculated field is appropriate when Gross Margin % itself must be mathematically derived—for example, (Revenue - Cost) / Revenue. However, the question does not ask where to implement the mathematical calculation; it asks where to define context for AI-generated insights. Contextual instructions, such as what “healthy gross margin” means or which business interpretation to apply, belong in Business Preferences.

A dashboard-scoped calculated field is even less suitable because it confines logic to a specific downstream analytical artifact instead of enriching the governed semantic context used by Tableau Agent across conversational experiences.

Salesforce's broader semantic architecture reinforces this separation: semantic models provide standardized business logic and definitions, while Business Preferences augment those models with business-specific interpretive knowledge for conversational analytics.

References/Topics: Agentic Experiences - > Business Preferences - > Tableau Agent Context - > Semantic Model Enrichment.

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

The limiting factor in this scenario is the user's license level. Setting proactive data alerts through Tableau Agent is an authoring-oriented capability that requires Tableau Next Creator access. A Consumer user can view and interact with published analytical content, but the Consumer persona does not receive the full set of creation and configuration capabilities needed to define alert conditions.

The fallback semantic model in option B is used when Tableau Agent lacks clear analytical context, such as when a user invokes the agent from a surface that does not already identify the relevant Tableau Next asset. Here, the user is explicitly accessing Tableau Agent from a page that contains Tableau Next content, so lack of fallback scoping is not the primary issue. Option A can prevent analysis of a particular metric, but the question establishes a broader inability to set the alert and emphasizes that the user has a Consumer license.

The appropriate remediation is therefore to use the Creator-level entitlement for users who must configure proactive alerts. This preserves the distinction between consumption permissions and analytical creation/configuration permissions.

References/Topics: Agentic Experiences - > Tableau Agent - > Proactive Data Alerts - > Creator Permissions.

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

The correct requirement is to enable the conversational analytics capability represented by Agentforce for Analytics, now called Tableau Agent. Salesforce explicitly lists the Salesforce Mobile app as a supported surface for Tableau Agent with the Data Analysis subagent. Users can ask natural-language analytical questions within Salesforce and receive grounded answers and visualizations based on their semantic models.

The terminology in option A is older but still maps directly to the current capability. Salesforce states that, beginning in July 2026, Agentforce for Analytics in Tableau Next is called Tableau Agent, while Concierge: Analytics Q & A became the conversational analytics capability enabled by Data Analysis.

No custom Lightning component is required merely to expose this supported conversational experience on Salesforce mobile. Likewise, deploying traditional dashboards to mobile would enable dashboard consumption but would not itself provide the requested natural-language Q & A experience.

References/Topics: Agentic Experiences - > Tableau Agent - > Data Analysis - > Salesforce Mobile - > Conversational Analytics.

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

A Salesforce action executed from a Tableau Next visualization must know which Salesforce record the user is acting upon. Salesforce documentation therefore requires the consultant to select the appropriate record ID when configuring the action. The record ID is the primary identifier for the Salesforce object, and it must be available as part of the visualization. For Contact-based actions, this means mapping the Contact ID so that Tableau Next can invoke the action against the correct Contact record.

The multi-row selection setting in A is not the fundamental record-context requirement for a standard Salesforce action. Likewise, B is misleading. Users certainly require authorization to execute the underlying Salesforce action, but Tableau Next does not require the consultant to create a special Tableau-specific custom permission set merely to map the action.

Architecturally, Tableau Next integrates the analytical and transactional layers by associating visualization data with Salesforce object identifiers. Once a user selects the relevant data element, Tableau Next can pass the corresponding record identity into the configured Salesforce action.

References/Topics: Visualizations and Dashboards - > Add Actions to Visualizations - > Salesforce Actions - > Record ID Mapping.

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