Salesforce Updated Analytics-Con-202 Exam Questions and Answers by damir

Data Kits are a native supported deployment mechanism for moving Tableau Next assets from a sandbox to a production Data 360 home org. Salesforce explicitly states that Tableau Next workspaces, visualizations, and dashboards can be deployed through Data Kits, and that Data 360 semantic models on which those analytical assets depend must also use Data Kits for deployment to target home orgs.

CSV export/import is a data-transfer technique, not a Tableau Next metadata lifecycle-management mechanism. It cannot preserve dashboard structure, visualization definitions, semantic-model dependencies, workspace metadata, or the relationships between these assets. Manual recreation would be operationally inefficient, prone to configuration drift, and unnecessary when supported deployment tooling exists.

A technically complete implementation must also account for dependency sequencing. When a Data Kit contains the semantic model and downstream Tableau Next content, Salesforce requires the publishing order to be at least Semantic Models - > Workspaces - > Visualizations - > Dashboards.

References/Topics: Managing Workspaces and Orgs - > Sandbox Development - > Data Kits - > Production Deployment - > Asset Dependencies.

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

Restricted is the correct General Access state. Salesforce documents that newly created Tableau Next assets are restricted by default. When General Access remains restricted, only individual users or Analytics Groups that have been explicitly granted access can open the asset.

For sensitive dashboards, this provides the correct baseline because access is opt-in rather than org-wide. The owner can then grant specific users or groups Viewer access and, where supported at the workspace level, Editor access.

Salesforce also makes an important distinction between Tableau Next asset access and underlying data access. Even if a dashboard is shared with a user, that action does not automatically grant permission to the DLOs, DMOs, or data spaces on which the dashboard depends. Data 360 governance still applies separately.

“Public” and “Shared” are not the documented General Access states that produce the required private-by-default behavior. Current Tableau Next access management uses Restricted as the state in which only explicitly shared users or groups can access an asset.

For sensitive content, the architecture should therefore use Restricted asset access + explicit user/group sharing + Data 360 governance.

References/Topics: Managing Workspaces and Orgs - > General Access - > Restricted - > Asset Sharing - > Data Governance.

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

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.

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

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.

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