Analytics-Con-202 Salesforce Certified Tableau Next Consultant Free Practice Exam Questions (2026 Updated)

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.

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

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

The correct security mechanism is the Einstein Trust Layer's PII masking capability. Salesforce guidance for AI-assisted calculated-field creation states that the agent may use information from the semantic model, including its schema and metadata, and that personally identifiable information is masked by the Einstein Trust Layer before information is sent to the LLM.

This allows Tableau Next's generative functionality to receive the semantic context required to construct useful calculated fields while applying Salesforce's enterprise AI security controls.

Option A describes a whole-model encryption/decryption workflow that is not the documented Tableau Next processing model. Option C is also incorrect because the system does not simply prohibit every field that could potentially contain PII. Instead, the Trust Layer applies masking and other controls to protect sensitive information while retaining useful analytical context.

More broadly, Salesforce states that Tableau Agent and Agentforce inherit the Einstein Trust Layer's security, governance, and trust mechanisms, including protections designed to prevent customer data from being retained by external LLMs for model training.

References/Topics: Agentic Experiences - > Einstein Trust Layer - > PII Masking - > Generative AI Calculated Fields.

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

The administrator must enable Collaborate with Slack and Tableau Next, making A correct. Salesforce's documented setup requires connecting the Salesforce org to Slack and then navigating to Tableau Next Administration settings to confirm that Collaborate with Slack and Tableau Next is enabled.

For Inspector Proactive Data Alerts specifically, Salesforce states that Slack must first be enabled for Tableau Next. Users can then receive Inspector alerts through Slack after the Agentforce app and associated connection are configured.

Option B is not the documented prerequisite. Tableau Next relies on appropriate Tableau Next permissions plus Salesforce/Slack identity and connection configuration; assigning a generic “Slack User” permission set is not the required answer.

Option C is also inaccurate as written. A properly configured Analytics and Visualization agent must contain the relevant Data Analysis and Data Alert Management capabilities, but administrators do not necessarily need to create an entirely new agent solely because Slack is being enabled; an existing qualifying agent can be configured and activated.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next with Slack - > Inspector Alerts - > Collaboration Settings - > Agentforce App.

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

The consultant should configure a Salesforce Flow action on the dashboard widget. Tableau Next supports single-click dashboard actions that can directly initiate Salesforce Flows using dashboard context. Salesforce even documents a virtually identical use case: enabling sales representatives to create a follow-up task directly from a dashboard widget displaying at-risk opportunities.

When configuring the action, the consultant selects Salesforce Flow as the action type, chooses an eligible flow, and maps the flow's input variables to static or dynamic dashboard values. Tableau Next currently supports standard screen flows and autolaunched flows for this capability.

A parameter action is fundamentally an analytical interaction mechanism and is not the native mechanism for executing a Salesforce Flow. Option C refers generally to Salesforce actions on visualization records, but the scenario explicitly identifies a dashboard widget that must initiate an existing Salesforce Flow. The dedicated Flow action is therefore the precise implementation.

This capability illustrates Tableau Next's actionable-analytics design: the user moves directly from recognizing an analytical condition to initiating an operational Salesforce process without leaving the dashboard.

References/Topics: Visualizations and Dashboards - > Single-Click Actions - > Salesforce Flow Actions - > Dynamic Input Mapping.

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

Option A, Draft with Einstein, can generate a calculation from natural language, but the question specifically asks about the multi-turn conversational agent experience, where the agent interacts with the user and refines the requirement. Therefore it is not the best answer. Option B addresses optimization/readiness rather than calculated-field authoring.

References/Topics: Agentic Experiences - > Tableau Agent - > Semantic Modeling/Data Pro - > Conversational Calculated Fields - > Natural-Language Authoring.

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

Tableau Next Personal Org supports reusing governed production assets without requiring the analyst to recreate or independently govern those assets. The documented procedure is to open or create the Personal Org workspace, select Add - > Data, choose Production from the Org dropdown, identify the production workspace and asset type, and then add the required asset to the workspace.

Therefore, A precisely matches the official workflow.

The reused production asset remains governed by production controls. Salesforce notes that assets reused from production are effectively read-only references; if the source asset is removed or the user loses access, the corresponding reused asset in the Personal Org stops functioning.

Cloning the DMO is unnecessary and would contradict the intended reuse model. A Data Kit is a deployment mechanism used to move supported assets between managed environments; it is not the Personal Org workflow for referencing an individual production DMO.

This design supports self-service analytics while maintaining centralized governance: analysts can combine authoritative enterprise data with their own analytical work without creating unmanaged duplicate definitions.

References/Topics: Managing Workspaces and Orgs - > Personal Org - > Reuse Production Org Assets - > Add Data.

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

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.

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

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 semantic model should form a single coherent connected cluster whenever the objects are intended to participate in the same analytical domain. Therefore, the consultant should establish valid relationships for the disconnected objects or remove them from the model when they do not belong.

Salesforce's current AI-readiness guidance explicitly warns about island tables and isolated objects. Disconnected objects can confuse both users and Tableau Agent because a query can imply relationships that the model has not defined. Salesforce recommends ensuring that all relevant objects are part of a single connected cluster and avoiding ambiguous or unjoined objects that could cause invalid agent responses.

Leaving objects isolated, as proposed by A, therefore preserves the exact modeling condition that decreases agent confidence. Option B is also architecturally incorrect. Business Preferences provide business terminology and interpretation guidance; they are not a substitute for structural relationships between data objects.

This principle is especially important for Tableau Agent because its semantic query generation relies on the relationship graph to determine valid navigation paths between dimensions and measures. A connected, unambiguous model substantially reduces unsupported joins and misleading answers.

References/Topics: Data Setup - > Semantic Model AI Readiness - > Connected Model Structure - > Relationships - > Remove Ambiguous Objects.

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

Tableau Next applies a deterministic precedence model for conditional formatting. When multiple conditions overlap, Tableau Next attempts to combine their formatting. When the formatting definitions actually conflict—for example, two matching rules specify incompatible formatting for the same property—the most recently created rule takes precedence. Therefore, B precisely matches documented Tableau Next behavior.

The conditions are not discarded simply because they overlap, so A is incorrect. Likewise, Tableau Next does not give permanent precedence to the earliest rule, making C incorrect.

This behavior is important when designing KPI text components or executive dashboards containing several threshold-based rules. Rule ordering can materially affect what users see when a measure simultaneously satisfies multiple business conditions. Consultants should therefore inspect overlapping ranges and understand which formatting attributes can coexist versus which produce a direct conflict.

Salesforce specifically documents two applicable principles: overlapping conditions have their formats combined, and conflicting rules resolve in favor of the most recently created rule.

References/Topics: Visualizations and Dashboards - > Analyze and Share Data - > Create Effective Dashboards - > Conditional Formatting.

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

The correct approach is to use the Tableau Semantics connector from Tableau Cloud. Salesforce explicitly supports connecting Tableau Desktop and Tableau Cloud directly to semantic models defined in Data 360/Tableau Semantics. This allows downstream Tableau authors to consume the same governed measures, dimensions, calculations, relationships, metrics, and business definitions that Tableau Next uses.

Option B would undermine the principal benefit of the semantic layer. Reconnecting directly to Data 360 objects and recreating joins would force analysts to reconstruct business logic and could lead to inconsistent calculations or relationships across analytical applications. Option C is also incorrect because Data Kits are Salesforce/Data 360 deployment mechanisms; they are not used to install semantic models into Tableau Cloud as independent Tableau data models.

This interoperability capability is strategically important: Tableau Semantics provides one governed analytical definition layer that can be consumed across Tableau Next, Tableau Cloud, Tableau Desktop, AI experiences, and other supported Salesforce applications. Analysts can therefore create custom Tableau Cloud visualizations without duplicating semantic logic.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Semantics Connector - > Tableau Cloud - > Reusable Semantic Models.

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

The existing parent-account filter is causing the metric to operate at Account scope, so merely adding another filter does not correctly express the desired record context. The consultant should remove that Account-based mapping and configure the metric dimension Opportunity ID to equal the Opportunity ID of the current Salesforce record. Therefore, B is correct.

Salesforce's embedded Tableau Next components support Record Value filtering on Lightning record pages. With Record Value, the filter dynamically retrieves a field from the Salesforce record currently being viewed and compares it against the selected field or dimension in the Tableau Next data model.

Option A fails to remove the inappropriate parent Account filter, leaving conflicting or overly restrictive context. Option C maps unlike identifiers—Opportunity ID against Account ID—which is logically invalid.

This question tests contextual embedding architecture: the metric definition must expose the required dimension, while Lightning App Builder supplies the current record value used to dynamically scope the embedded metric.

References/Topics: Visualizations and Dashboards - > Embedded Tableau Next Metrics - > Record Value Filters - > Lightning Record Context.

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

Tableau Next provides native interoperability with Tableau Cloud Published Data Sources (PDSs). Salesforce allows a consultant to create a Data 360 semantic model by connecting directly to an existing PDS after establishing the required trust between the Salesforce org and Tableau Cloud site.

The PDS remains the external data definition and query source. Tableau Next inherits fields such as their names and data types, and the semantic model can then be enriched with calculated fields, metrics, descriptions, and business context. Critically, Salesforce states that this approach allows organizations to use existing Tableau content without data or metadata migration.

That precisely addresses the customer's concern about preserving substantial prior investment in Tableau Cloud modeling and calculations.

Options A and B introduce mechanisms that are not the native Tableau Next interoperability pattern documented for PDS reuse. There is no requirement to translate the PDS into Snowflake SQL or convert it into a CRM Analytics recipe.

This architecture enables Tableau Next to extend rather than replace mature Tableau investments, while exposing existing governed analytical logic to Tableau Agent.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Cloud PDS - > Tableau Semantics - > Create Semantic Model from Published Data Source.

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

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.

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

Tableau Unmetered Admin is the correct permission set because the user needs full Tableau Next administrative capability rather than analytical authoring alone. Salesforce states that Tableau Unmetered Admin permits access to Tableau Next Setup and edit capabilities across Tableau Next features in the production environment. Administrative users can configure the product and provision users with appropriate Tableau Next permission sets.

Salesforce specifically requires Tableau Unmetered Admin or Tableau Next Admin to access Tableau Next Administration and enable Tableau Next. When Tableau Next is enabled, the administrator also receives the associated Data Cloud Architect capabilities required for underlying Data 360 configuration.

The Platform Analyst role is intended primarily for creating, managing, and sharing governed Tableau Next analytical assets. It does not represent the full administrative persona required to configure Tableau Next and manage users. Self-Service Analyst focuses primarily on Personal Org and self-service analytical workflows and is even further removed from the stated administration requirement.

This question follows least-privilege role design: administrative tasks require the Admin persona; content creation alone generally requires an Analyst persona.

References/Topics: Basic Setup and Admin - > Tableau Next Permission Sets - > Tableau Unmetered Admin - > User Management - > Tableau Next Setup.

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

Agent Scoping is specifically designed for situations in which Tableau Agent receives a question without clear analytical context. Salesforce defines Agent Scoping as the administrator-controlled list of semantic models that Tableau Agent can search when context cannot otherwise determine which model should answer the user's question.

Typical examples include Tableau Agent being used in Slack or embedded on a page that does not contain a Tableau Next dashboard, metric, or other asset capable of supplying context. The configured semantic-model list serves as a fallback list. Tableau Agent can then determine which approved model should be used to resolve the user's request.

Agent Scoping does not run indiscriminately for every question, which eliminates B. When Tableau Agent is invoked from an analytical surface that already provides clear semantic context, that existing context guides the interaction. C is also overly restrictive; Agent Scoping is not limited to metric-details pages or scenarios involving multiple models attached to a metric.

Administrators can configure approved fallback semantic models for active Analytics and Visualization agents using the Data Analysis subagent.

References/Topics: Agentic Experiences - > Tableau Agent - > Agent Scoping - > Fallback Semantic Models - > Context Resolution.

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

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.

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

A Personal Org is specifically designed for self-service analysis where an analyst needs to combine governed corporate information with personal or specialized data without introducing that experimental dataset into the managed production governance environment.

Salesforce states that Personal Org enables analysts to combine production data with local or specialized datasets, create semantic models and visualizations, and iterate independently without affecting governed production content. Production assets can also be reused inside Personal Org while their existing production governance remains intact.

Once the analysis is ready, the Personal Org owner can share the relevant workspace with another eligible analyst and grant Viewer or Editor access. Salesforce explicitly documents sharing Personal Org workspaces with Tableau Next Analyst users.

Option B does not provide the isolated self-service environment intended for ungoverned analytical experimentation. Option C unnecessarily moves the analytical workflow into an external MCP client and does not represent the native Tableau Next solution for this use case.

References/Topics: Managing Workspaces and Orgs - > Personal Org - > Combine Governed and Personal Data - > Workspace Sharing.

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

Generative AI capabilities in Tableau Semantics can directly accelerate semantic-model authoring by drafting calculated-field formulas and semantic descriptions, making A the correct choice. Salesforce supports Draft with Einstein, where the consultant describes the calculation in natural language and Einstein generates the calculated-field definition, including formula-related configuration that the author can review and save.

Salesforce also provides AI-generated semantic descriptions. These descriptions supply business context to downstream conversational analytics and help Tableau Agent correctly discover and interpret objects and fields.

Identity resolution and DMO mapping belong to Data 360 data-modeling and identity-management workflows, not the semantic-model generative-authoring capability described in this scenario. Dashboard and visualization construction is also a separate analytics-authoring process rather than the specified operation within the semantic data model configuration canvas.

The exam principle is that Tableau Agent/Semantics AI reduces semantic-authoring friction by translating natural-language analytical intent into semantic definitions, relationships, descriptions, and calculations.

References/Topics: Agentic Experiences - > generative AI for Tableau Next components; Create Semantic Models - > AI-assisted calculated fields and descriptions.

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