Free Salesforce Analytics-Con-202 Practice Exam with Questions & Answers | Set: 2

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.

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

Agent Scoping determines which approved semantic models Tableau Agent can search when a user's question lacks sufficient analytical context. Salesforce describes Agent Scoping as defining a fallback list of semantic models for a particular analytics agent. This fallback is used when Tableau Agent cannot infer the appropriate model from the current page or analytical asset.

Examples include asking Tableau Agent a question from Slack or embedding the agent on a page that contains no Tableau Next metric or dashboard. In those circumstances, the agent uses its approved fallback models to determine the appropriate semantic context.

When a user asks a question from a dashboard or metric that already supplies clear analytical context, Salesforce states that Tableau Agent uses the semantic models associated with that asset instead of the fallback list. User permissions remain enforced at runtime; placing a model on the fallback list never grants unauthorized access.

Option B is incorrect because Agent Scoping does not enforce row-level security; Data 360 governance and user permissions perform that function. Option C is unrelated to agent routing.

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

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

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.

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

Enable Query Cache is the appropriate short-term performance optimization for a frequently accessed Tableau Next dashboard. Query caching reduces repeated execution of expensive live analytical queries by temporarily reusing previously calculated query results.

Salesforce specifically positions dashboard query caching as a mechanism to accelerate page load times for frequently visited dashboards. Current Tableau Next functionality can store and reuse query results for up to approximately 30 minutes, thereby reducing system overhead and improving the end-user experience.

This is precisely appropriate when the consultant wants a rapid tactical improvement before investigating deeper issues such as semantic-model complexity, source performance, query design, data architecture, or excessive dashboard density.

Disabling Reflow concerns dashboard layout behavior and responsive presentation rather than query-processing latency. Turning off Tableau Agent likewise does not address the underlying query execution performed to render dashboard widgets.

Caching does involve a freshness tradeoff because viewers may temporarily receive cached rather than newly executed query results. For dashboards requiring immediately current information, live mode may still be necessary. The consultant should therefore treat caching as a deliberate performance-versus-freshness decision.

References/Topics: Visualizations and Dashboards - > Dashboard Performance - > Query Cache - > Cached Data Mode.

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

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.

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

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.

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

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

The consultant should modify the metric definition in the underlying semantic model. Tableau Next metrics are semantic-layer objects. Salesforce defines a metric as a business KPI derived from one or more measures together with a date field, and metrics are built from semantic models.

Therefore, selecting which date dimension governs the metric's time trend is part of the metric's semantic definition rather than dashboard presentation logic. The dashboard consumes the governed metric; changing the dashboard would not correct the authoritative metric definition.

Option B is also inappropriate. Data Lake Objects and Data Model Objects define the underlying physical/logical data available in Data 360. Because the correct date field already exists in the semantic model, there is no requirement to modify the underlying DLO or DMO. The problem lies specifically in which existing semantic field the metric uses for its temporal definition.

This reflects a central Tableau Next architectural principle: reusable analytical business logic—including metrics, calculations, temporal semantics, and contextual definitions—should reside in Tableau Semantics, while dashboards remain downstream consumption and presentation layers.

References/Topics: Data Setup - > Semantic Models - > Metrics - > Measure and Date Field Configuration.

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

Tableau Next asset sharing and Data 360 data access are separate layers. Granting users Viewer access to a workspace can provide inherited access to its dashboards, visualizations, and semantic models, but it does not automatically grant access to the underlying Data 360 data. Salesforce explicitly states that access to a semantic model requires access to the data space containing the model as well as access to the objects and fields used by that model.

Therefore, C is correct.

End users do not require Edit access to underlying Data 360 objects merely to view dashboard data, making A unnecessarily privileged. Similarly, B is incorrect because Consumer-level permission sets can view Tableau Next assets; Platform Analyst or Self-Service Analyst permissions are not universally required for dashboard consumption.

The architecture can be understood as three layers: license/permission access, Tableau Next asset sharing, and Data 360 data visibility/governance. Successful dashboard rollout requires all applicable layers to authorize the user. Sharing alone cannot override an administrator's data-space, DMO, DLO, field, or policy restrictions.

References/Topics: Managing Workspaces and Orgs - > Asset Sharing - > Data Spaces - > Data 360 Governance - > Semantic Model Access.

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

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.

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

The semantic model should be enriched so the agent can associate the organization's business language “Earnings” with the existing Profit Margin concept. Therefore, B is the correct answer. Semantic models provide the business-context layer that allows Tableau Agent to translate natural-language terminology into governed analytical definitions. Salesforce recommends clear, contextual names and descriptions and explicitly highlights synonyms as an important semantic consideration for agent readiness.

Salesforce's Tableau Semantics training also explains that synonyms broaden the agent's understanding of terminology used by business users, allowing alternate terms to map back to authoritative metrics and definitions.

Creating a duplicate metric merely to support another phrase introduces redundant semantic definitions and increases ambiguity. Salesforce specifically recommends eliminating redundant or overlapping calculated definitions rather than multiplying them. Changing aggregation from Average to Sum would alter mathematical behavior and does nothing to resolve a terminology-discovery problem.

References/Topics: Data Setup - > Create Semantic Models - > Design Semantic Models for AI Readiness - > field descriptions, synonyms, ambiguity resolution.

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