Pass the Salesforce Salesforce Consultant Analytics-Con-202 Questions and answers with CertsForce

For a Tableau Next Metric widget to respond dynamically to dashboard filtering, two conditions must be satisfied. First, the metric widget must be configured to receive dashboard filters. Second, the dimensions being used by those dashboard filters must exist in the metric definition as supported dimensions. Salesforce specifically documents that a Metric widget can only be filtered by dimensions explicitly included in the metric definition, typically as Additional Dimensions.

Therefore, C is the only complete answer.

Option A fails because enabling dashboard-filter reception is not enough if the metric definition lacks the necessary dimensions. Tableau Next cannot apply a filter against a dimensional grain the metric does not expose. Option B has the required dimensions but explicitly disables receipt of dashboard filters, preventing the widget from responding to dashboard interactions.

This distinction is important because visualizations and metric widgets have different interaction requirements. A dashboard visualization can participate naturally in interactive filtering, whereas a governed metric must expose the appropriate dimensions in its semantic definition before those dashboard selections can alter the displayed metric result.

References/Topics: Visualizations and Dashboards - > Metric Widgets - > Receive Dashboard Filters - > Metric Additional Dimensions.

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

User Interaction Logging is the capability used to begin collecting interaction data for governance and adoption analysis. In this scenario, Cloud Kicks needs visibility into how users interact with Tableau Next dashboard assets so administrators can evaluate usage patterns, adoption, and engagement. Enabling interaction logging creates the foundation for capturing those user events and making them available for downstream monitoring and analysis.

Tableau Next Auditing is associated with broader administrative audit and governance use cases, while Session Tracing is oriented toward tracing agent sessions and AI behavior. Neither is the specific capability identified here for initiating dashboard interaction collection. The requirement is centered on user activity against Tableau Next assets rather than agent reasoning or session diagnostics.

A consultant should distinguish telemetry collection from downstream analysis. First, interaction events must be captured through User Interaction Logging; those events can then be analyzed to understand which assets are used, how users engage with dashboards, and where adoption or governance attention is required. This supports operational oversight without changing the analytical content itself.

References/Topics: Basic Setup and Admin - > Tableau Next User Interaction Logging - > Governance and Adoption Monitoring.

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

The minimum general Tableau Next persona that can view, explore, and follow metrics is the Tableau Unmetered Consumer level represented by B.

Salesforce documents that Consumer users can access the Tableau Next home experience, use Tableau Agent, view workspaces, dashboards, and visualizations, and view, explore, and follow metrics. Salesforce's metric-specific documentation likewise identifies Tableau Unmetered Consumer and equivalent Consumer/Self-Service Consumer permission sets as sufficient to follow metrics.

A Self-Service Analyst can also perform these actions, but that persona includes significantly broader capabilities and therefore is not the minimum required level. Analysts can work with Tableau Next Studio and, depending on the permission set, create or edit analytical content.

An Included App license is narrower. Included App/Limited Consumer personas are designed primarily to interact with prepackaged Tableau Next Apps for Salesforce rather than provide general Tableau Next home and metric exploration capabilities.

The exam principle is to select the least-privileged persona that fully satisfies the requirement, rather than assigning authoring permissions merely because they also include consumption capabilities.

References/Topics: Basic Setup and Admin - > Tableau Next Licenses and Permission Sets - > Consumer - > Metric Exploration and Following.

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

The most likely cause is that the consultant used Copy Link in a way that shared the dashboard's default state rather than preserving the interactive filter state that was applied during analysis. A standard dashboard link can reopen the asset without carrying the sender's temporary filter and selection context, which explains why the colleague sees an unfiltered dashboard.

Option A is incorrect because dashboard views can be shared; the problem is the type of link or view state being shared, not a blanket prohibition on sharing filtered analysis. Option C is also incorrect because there is no separate permission category whose purpose is specifically to display filters contained in a shared dashboard view. The recipient still needs ordinary access to the dashboard and its underlying governed data, but permissions do not explain why the filters disappeared.

For exam purposes, remember the distinction between sharing the dashboard asset itself and sharing the user's current analytical state. When identical filter context matters, the consultant must use the mechanism that preserves that current view rather than a generic/default asset link.

References/Topics: Visualizations and Dashboards - > Dashboard Sharing - > Copy Link - > Filtered View State.

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

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.

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