All Analytics-Con-202 Test Inside Salesforce Questions

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 Next row-level security should be implemented through Data 360 governance policies, making B correct. Salesforce explicitly states that for Data 360 DLOs and DMOs, record-level security is defined through Data 360 policies. Tableau Next dashboards and visualizations built on those objects then inherit the enforced data visibility.

For example, the account dataset can include an attribute identifying the responsible territory or regional manager. A Data Governance access policy can evaluate the current user's relevant attributes and restrict returned records accordingly. Because security is enforced below the semantic and visualization layers, the same rules consistently protect dashboards, metrics, Tableau Agent queries, and other downstream consumers.

Option A describes the traditional Tableau USERNAME() pattern, but current Tableau Next guidance explicitly states that native user functions such as USERNAME() aren't the preferred/current RLS implementation for this architecture. Option C creates serious scalability, maintenance, and consistency problems and violates centralized governance principles.

The architectural rule is: define security as close to the governed data layer as possible so every downstream analytical experience inherits the same policy.

References/Topics: Data Setup - > Data 360 Governance - > Row-Level Security - > Access Policies - > Data Object Security.

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

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.

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

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.

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