Generative AI capabilities in Tableau Semantics can directly accelerate semantic-model authoring by drafting calculated-field formulas and semantic descriptions, making A the correct choice. Salesforce supports Draft with Einstein, where the consultant describes the calculation in natural language and Einstein generates the calculated-field definition, including formula-related configuration that the author can review and save.

Salesforce also provides AI-generated semantic descriptions. These descriptions supply business context to downstream conversational analytics and help Tableau Agent correctly discover and interpret objects and fields.

Identity resolution and DMO mapping belong to Data 360 data-modeling and identity-management workflows, not the semantic-model generative-authoring capability described in this scenario. Dashboard and visualization construction is also a separate analytics-authoring process rather than the specified operation within the semantic data model configuration canvas.

The exam principle is that Tableau Agent/Semantics AI reduces semantic-authoring friction by translating natural-language analytical intent into semantic definitions, relationships, descriptions, and calculations.

References/Topics: Agentic Experiences - > generative AI for Tableau Next components; Create Semantic Models - > AI-assisted calculated fields and descriptions.

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

Tableau Next applies both asset-sharing permissions and platform permission sets. Granting Editor access through workspace sharing cannot elevate a user's capabilities beyond those granted by the administrator. Salesforce explicitly states that sharing doesn't override permissions set by the admin and that a user who lacks the permission set required to edit Tableau Next assets cannot edit an asset even when granted Editor access.

Therefore, C is correct.

Workspace-level access is designed to simplify administration. Users and Analytics Groups can be granted Viewer or Editor access to a workspace, with appropriate access applying to contained assets subject to underlying security and permission requirements. Consequently, B is incorrect as a general explanation.

Option A is also incorrect. Workspace owners can share assets subject to their own permissions, but inability of the affected user to edit is not because dashboards universally require a separate owner-assigned Editor permission.

Think of Tableau Next authorization as multiple gates: license - > Tableau Next permission set - > asset sharing - > underlying data access. A more permissive setting at a downstream sharing layer cannot bypass a restrictive upstream administrative permission.

References/Topics: Managing Workspaces and Orgs - > Workspace Sharing - > Editor Access - > Tableau Next Permission Sets - > Permission Inheritance.

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

A semantic model created from a Tableau Cloud Published Data Source remains directly connected to the PDS. Salesforce states that the PDS acts as the external data definition and query source, and the integration does not create a corresponding Data 360 data object. Queries remain federated through the PDS connection.

For users configured in Tableau Cloud, Salesforce further states that record-level security and data access are inherited from the PDS. Consequently, a Tableau Next user can have access to the Tableau Next workspace, semantic model, dashboard, and visualization but still receive no usable data if their Tableau Cloud identity lacks access to the underlying Published Data Source.

Option B is incorrect because a PDS is a direct external connection and isn't represented as a DLO in Data 360. Option C is inconsistent with the scenario because the user already has the required Tableau Next asset permissions and access; moreover, the actual PDS authorization boundary remains relevant independently.

This question tests an important cross-platform rule: Tableau Next asset sharing does not override access controls enforced by the connected Tableau Cloud PDS.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Published Data Sources - > Tableau Cloud Trust - > PDS Authentication and Governance.

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

The administrator must enable Collaborate with Slack and Tableau Next, making A correct. Salesforce's documented setup requires connecting the Salesforce org to Slack and then navigating to Tableau Next Administration settings to confirm that Collaborate with Slack and Tableau Next is enabled.

For Inspector Proactive Data Alerts specifically, Salesforce states that Slack must first be enabled for Tableau Next. Users can then receive Inspector alerts through Slack after the Agentforce app and associated connection are configured.

Option B is not the documented prerequisite. Tableau Next relies on appropriate Tableau Next permissions plus Salesforce/Slack identity and connection configuration; assigning a generic “Slack User” permission set is not the required answer.

Option C is also inaccurate as written. A properly configured Analytics and Visualization agent must contain the relevant Data Analysis and Data Alert Management capabilities, but administrators do not necessarily need to create an entirely new agent solely because Slack is being enabled; an existing qualifying agent can be configured and activated.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next with Slack - > Inspector Alerts - > Collaboration Settings - > Agentforce App.

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

Tableau Unmetered Self-Service Consumer is the best match because these users only require consumption and conversational-analysis functionality rather than administrative or authoring privileges.

Salesforce's current permission-set documentation states that users assigned Tableau Unmetered Self-Service Consumer can browse, view, and interact with Tableau Next production assets and can use Tableau Agent. They can also view dashboards, visualizations, metrics, and other supported analytics without receiving the broader content-management capabilities associated with analyst or administrator roles.

The Tableau Unmetered Admin permission set provides substantially excessive privileges, including platform configuration, user administration, asset management, and governance capabilities. Assigning it would directly violate least-privilege design.

The Tableau Unmetered Platform Analyst permission set is intended for users who create, manage, and share governed Tableau Next assets. Those capabilities are unnecessary because the stated users will not create dashboards or semantic models.

The certification principle is straightforward: license and permission assignment should reflect the minimum required analytical persona. Conversational consumption alone does not justify authoring or administrative privileges.

References/Topics: Basic Setup and Admin - > Tableau Next Licenses and Permission Sets - > Self-Service Consumer - > Tableau Agent Access.

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

The correct security mechanism is the Einstein Trust Layer's PII masking capability. Salesforce guidance for AI-assisted calculated-field creation states that the agent may use information from the semantic model, including its schema and metadata, and that personally identifiable information is masked by the Einstein Trust Layer before information is sent to the LLM.

This allows Tableau Next's generative functionality to receive the semantic context required to construct useful calculated fields while applying Salesforce's enterprise AI security controls.

Option A describes a whole-model encryption/decryption workflow that is not the documented Tableau Next processing model. Option C is also incorrect because the system does not simply prohibit every field that could potentially contain PII. Instead, the Trust Layer applies masking and other controls to protect sensitive information while retaining useful analytical context.

More broadly, Salesforce states that Tableau Agent and Agentforce inherit the Einstein Trust Layer's security, governance, and trust mechanisms, including protections designed to prevent customer data from being retained by external LLMs for model training.

References/Topics: Agentic Experiences - > Einstein Trust Layer - > PII Masking - > Generative AI Calculated Fields.

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

Tableau Next's distinctive value is its agentic, conversational, and actionable analytics layer, so C is correct. Salesforce positions Tableau Next as an end-to-end agentic analytics platform combining Tableau analytics, Agentforce AI, and the Data 360 semantic layer. It enables users to ask freeform analytical questions, receive grounded text and visual answers, obtain proactive insights, and initiate actions where work occurs.

The platform is therefore complementary to existing analytical investments. Tableau Cloud can continue supporting sophisticated traditional analytics and executive exploration, while CRM Analytics can continue supporting embedded Salesforce analytical use cases. Tableau Next introduces a governed semantic and agentic layer that makes data conversational and actionable.

Option A is too absolute. Salesforce interoperability capabilities explicitly support connecting Tableau Cloud to Tableau Semantics, illustrating coexistence rather than mandatory replacement. Option B also mischaracterizes Published Data Source integration: Tableau Next can build semantic models directly from supported Tableau Cloud PDS content; its purpose is not merely extraction into DMOs.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next Positioning - > Tableau Agent - > Tableau Cloud and CRM Analytics Coexistence.

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

The Tableau Next Connect REST API is the appropriate interface when a developer or consultant needs to programmatically configure or update Tableau Next visualization assets. Salesforce documents that the API supports creating and updating visualizations and workspaces and exposes dedicated visualization resources through the /tableau/visualizations endpoints.

Because visualization appearance and configuration are properties of the visualization asset, a programmatic modification to its color configuration belongs to the Tableau Next REST API development surface.

The Semantic Layer DX VS Code Extension is focused on semantic-layer development and metadata associated with semantic models; it is not the primary API for editing visualization presentation properties. Salesforce CLI is an extensible deployment and administration tool, but it is not the dedicated Tableau Next runtime interface for modifying visualization configuration.

Salesforce's Tableau Next development documentation explicitly positions the Connect REST APIs as the developer interface for configuring and managing Tableau Next visualizations and workspaces. The API therefore provides the correct abstraction when visualization changes must be automated, integrated into an application, or performed through code.

References/Topics: Embedding, Cross-Cloud, and Interoperability - > Tableau Next Development - > Connect REST API - > Visualization Resources.

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

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.

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

Zero Copy Data Federation is the correct architectural approach because it allows Tableau Next and Data 360 to work with Snowflake-hosted data without creating a separate duplicated dataset. The Snowflake tables remain in the source platform while the federation layer exposes them for governed analytical use. This directly addresses both storage-cost concerns and the compliance risk associated with maintaining synchronized copies.

Option B would move the data into Salesforce custom objects through an integration flow, which creates another persisted copy and increases synchronization and governance overhead. Option C also creates replicated data through scheduled batch processing and therefore violates the stated requirement to avoid duplication. Zero-copy access keeps the source system authoritative while making the dataset available for semantic modeling and Tableau Next analysis.

The important architecture pattern is federation rather than extraction: connect Snowflake, expose the required federated data objects, apply the necessary governance, and then build the Tableau Next semantic layer over those objects. This minimizes data movement while preserving analytical accessibility.

References/Topics: Data Setup - > Data 360 - > Snowflake - > Zero Copy Data Federation - > Tableau Next.

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