Free Salesforce Tableau Next Consultant Practice Test Questions

Explanation:

To migrate dashboards (and related Tableau Next assets) from a sandbox org to production, the correct deployment mechanism is Data Kits. Data kits package Tableau Next assets — such as dashboards, semantic models, metrics, and their dependencies — so they can be deployed/migrated between orgs (sandbox → production) in a governed, repeatable way. This is the native deployment approach for Tableau Next assets.

Why the other options are incorrect:

B. CSV export/import:
CSV only handles flat data, not dashboard definitions, semantic models, or asset metadata. It cannot migrate Tableau Next dashboards or their dependent assets.

C. Manual recreation:
Rebuilding dashboards by hand is error-prone, inefficient, and not a deployment mechanism. It risks inconsistency and defeats the purpose of a proper migration process.

📚 References:

Tableau Next Documentation – Data Kits and Deployment: Data kits are the mechanism for packaging and deploying Tableau Next assets (dashboards, semantic models, metrics) across orgs.

Tableau Next Best Practices – Sandbox-to-Production Migration: Recommends Data Kits for governed, repeatable asset migration.

Explanation:

To migrate Tableau Next assets and the underlying Data 360 semantic models from a sandbox to a production org together in a single step, the consultant should use a Data Kit. Data Kits are the native packaging/deployment mechanism that bundles Tableau Next assets (dashboards, metrics, semantic models) along with their dependencies — including the underlying Data 360 semantic models — so everything can be deployed as one unit in a single operation.

Why the other options are incorrect:

A. Salesforce CLI:
The Salesforce CLI deploys Salesforce metadata (Apex, objects, flows, etc.). It does not package or deploy Tableau Next assets and Data 360 semantic models together as a single unit.

B. Change Set:
Change Sets move Salesforce metadata components between orgs. They do not support Tableau Next assets or Data 360 semantic models, so they cannot achieve this migration.

References:

Tableau Next Documentation – Data Kits: Data kits bundle Tableau Next assets and their underlying Data 360 semantic models for single-step deployment across orgs.

Tableau Next Best Practices – Sandbox-to-Production Deployment: Recommends Data Kits for migrating Tableau Next assets with dependencies intact.

Explanation:

To ensure that no one can see dashboards by default, the consultant should set the workspace's General Access to Restricted. Under Restricted access, dashboards are not visible to anyone by default — users must be explicitly granted access. This is the appropriate setting for sensitive dashboards where access must be tightly controlled.

Why the other options are incorrect:

B. Public:
Public access makes dashboards visible to everyone by default — the exact opposite of the requirement and inappropriate for sensitive data.

C. Shared:
"Shared" implies broader visibility to a group/audience by default, which does not guarantee that no one can see the dashboards. It does not meet the "no one by default" requirement.

📚 References:

Tableau Next Documentation – Workspace General Access Settings: Restricted ensures no default visibility; Public and Shared grant broader visibility.

Tableau Next Best Practices – Securing Sensitive Dashboards: Recommends Restricted general access for sensitive content requiring explicit grants.