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.