Salesforce Analytics-Con-202 Practice Exam Questions & Answers

Tableau Agent is optimized for conversational, exploratory analytics in which a business user asks natural-language questions and receives grounded answers and visualizations. A request such as, ''What are my top accounts by Annual Contract Value this quarter?'' maps directly to Tableau Agent's supported descriptive-analysis capabilities. Salesforce explicitly lists Top-N questions, aggregations, dimensional breakdowns, comparisons, and other business-oriented analytical questions among the supported conversational patterns.

A fixed monthly-close report for a board is better represented by a governed dashboard or reporting asset because its structure, presentation, and recurring content are predetermined. Likewise, Tableau Agent is not positioned as a general-purpose data-science workflow development environment.

The architectural distinction is important for the exam: dashboards provide curated, repeatable analytical experiences, whereas Tableau Agent adds an interactive conversational layer over semantic models. It translates the user's business question into semantic analytical operations and returns contextual text and visual output.

Reference/Topics: Agentic Experiences -> Analyze and Share Data in Tableau Next -> About Conversational Analytics -> Supported Questions and Surfaces.

Among the listed choices, Inbound and Outbound Change Sets are the appropriate native Salesforce deployment mechanism. Tableau Next supports Salesforce Metadata API-based deployment capabilities, including change sets, for moving Tableau Next workspaces, visualizations, and dashboards between supported sandbox and target organizations. The workflow uses an outbound change set in the source org and an inbound change set in the target org.

The Data 360 Ingestion API is intended for bringing data into Data 360 rather than lifecycle deployment of Tableau Next metadata. The Tableau Cloud Site Migration Tool pertains to Tableau Cloud site migration and is not the Salesforce metadata deployment mechanism described here.

Reference/Topics: Managing Workspaces and Orgs -> Organize and Deploy Analytical Assets -> Deploy Tableau Next Assets.

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.

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

The user should select Sources. Tableau Agent's conversational analytics experience exposes a Sources control specifically to provide transparency into how a response was generated.

Salesforce documents that after Tableau Agent returns an analytical answer, users can select Sources to review details about how the agent analyzed the request, including the data sources and metrics used during the analysis. Salesforce also states that conversational analytics responses include information about the sources and reasoning used in the analysis, supporting traceability and user trust.

Option B concerns visualization configuration rather than agent reasoning and source grounding. Option C is not the documented Tableau Agent workflow for exposing reasoning provenance to end users.

This capability is important because Tableau Agent performs semantic queries against the underlying semantic model, synthesizes the returned data into a textual response, and generates a suitable visualization. Sources helps users understand the analytical basis of that output rather than requiring them to accept an opaque AI-generated answer.

Reference/Topics: Agentic Experiences -> Tableau Agent -> Conversational Analytics -> Sources -> Response Transparency and Grounding.

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.