Analytics-Con-202 Practice Tests - Salesforce Certified Tableau Next Consultant

Prévia do material em texto

1 / 9
Exam : Analytics-Con-202
Title :
https://www.passcert.com/Analytics-Con-202.html
Salesforce Certified Tableau
Next Consultant
2 / 9
1.A Tableau Next Consultant is asked to configure proactive alerts for executives.
Which delivery channels are supported?
A. Slack and Email.
B. SMS only.
C. Microsoft Teams only.
Answer: A
Explanation:
Tableau Next proactive alerts support delivery through Slack and Email, making option A the correct
choice. The purpose of proactive alerting is to notify users when an important metric condition is met
without requiring them to continually open dashboards and check the metric manually. Supporting
collaboration and messaging channels allows the alert to reach executives in the tools they already
monitor.
SMS-only delivery is not the supported model described here, and Microsoft Teams is not the exclusive
proactive-alert channel. The alerting workflow is tied to Tableau Next metrics and the configured
notification integrations. Once the metric, alert condition, and delivery configuration are in place, users
can receive timely notification when the monitored value crosses the defined condition.
From an implementation perspective, consultants should confirm that the required alerting capability is
enabled, that users can access the metric, and that the organization's Slack and email notification
configuration is available. The analytical rule remains defined against the governed metric, while the
selected channel determines how the resulting notification reaches the user.
References/Topics: Agentic Experiences - > Proactive Data Alerts - > Slack and Email Delivery.
2.Universal Containers wants to allow sales reps to ask natural language questions about their pipeline
directly from Salesforce mobile.
Which configuration is required?
A. Enable Agentforce for Analytics.
B. Create custom Lightning components.
C. Deploy Tableau dashboards to mobile.
Answer: A
Explanation:
The correct requirement is to enable the conversational analytics capability represented by Agentforce
for Analytics, now called Tableau Agent. Salesforce explicitly lists the Salesforce Mobile app as a
supported surface for Tableau Agent with the Data Analysis subagent. Users can ask natural-language
analytical questions within Salesforce and receive grounded answers and visualizations based on their
semantic models.
The terminology in option A is older but still maps directly to the current capability. Salesforce states that,
beginning in July 2026, Agentforce for Analytics in Tableau Next is called Tableau Agent, while
Concierge: Analytics Q & A became the conversational analytics capability enabled by Data Analysis.
No custom Lightning component is required merely to expose this supported conversational experience
on Salesforce mobile. Likewise, deploying traditional dashboards to mobile would enable dashboard
consumption but would not itself provide the requested natural-language Q & A experience.
References/Topics: Agentic Experiences - > Tableau Agent - > Data Analysis - > Salesforce Mobile - >
Conversational Analytics.
3 / 9
3.Universal Containers (UC) is developing a new profitability dashboard within its Tableau Next Personal
Org. To ensure the dashboard is accurate, UC needs to incorporate the primary Sales data model object
(DMO) which is governed and maintained in the production environment. The company's Tableau Next
Consultant needs to bring this specific asset into its Personal Org workspace.
Which action must the consultant take to use the production Sales DMO in UC's Personal Org?
A. Use the Add Data function and select the production org as the source location.
B. Clone the Sales DMO from the production workspace to the Personal Org.
C. Initiate a data kit deployment from the production org to UC's Personal Org.
Answer: A
Explanation:
Tableau Next Personal Org supports reusing governed production assets without requiring the analyst to
recreate or independently govern those assets. The documented procedure is to open or create the
Personal Org workspace, select Add - > Data, choose Production from the Org dropdown, identify the
production workspace and asset type, and then add the required asset to the workspace.
Therefore, A precisely matches the official workflow.
The reused production asset remains governed by production controls. Salesforce notes that assets
reused from production are effectively read-only references; if the source asset is removed or the user
loses access, the corresponding reused asset in the Personal Org stops functioning.
Cloning the DMO is unnecessary and would contradict the intended reuse model. A Data Kit is a
deployment mechanism used to move supported assets between managed environments; it is not the
Personal Org workflow for referencing an individual production DMO.
This design supports self-service analytics while maintaining centralized governance: analysts can
combine authoritative enterprise data with their own analytical work without creating unmanaged
duplicate definitions.
References/Topics: Managing Workspaces and Orgs - > Personal Org - > Reuse Production Org Assets
- > Add Data.
4.A new analyst at Coral Cloud Resorts is responsible for the complete setup of Tableau Next. This
includes configuring the platform, managing all users, and overseeing all workspaces and assets.
Which permission set must a Tableau Next Consultant assign to the analyst?
A. Tableau Unmetered Self Service Analyst
B. Tableau Unmetered Platform Analyst
C. Tableau Unmetered Admin
Answer: C
Explanation:
Tableau Unmetered Admin is the correct permission set because the user needs full Tableau Next
administrative capability rather than analytical authoring alone. Salesforce states that Tableau
Unmetered Admin permits access to Tableau Next Setup and edit capabilities across Tableau Next
features in the production environment. Administrative users can configure the product and provision
users with appropriate Tableau Next permission sets.
Salesforce specifically requires Tableau Unmetered Admin or Tableau Next Admin to access Tableau
Next Administration and enable Tableau Next. When Tableau Next is enabled, the administrator also
receives the associated Data Cloud Architect capabilities required for underlying Data 360 configuration.
The Platform Analyst role is intended primarily for creating, managing, and sharing governed Tableau
4 / 9
Next analytical assets. It does not represent the full administrative persona required to configure Tableau
Next and manage users. Self-Service Analyst focuses primarily on Personal Org and self-service
analytical workflows and is even further removed from the stated administration requirement.
This question follows least-privilege role design: administrative tasks require the Admin persona; content
creation alone generally requires an Analyst persona.
References/Topics: Basic Setup and Admin - > Tableau Next Permission Sets - > Tableau Unmetered
Admin - > User Management - > Tableau Next Setup.
5.A Tableau Next Consultant is looking to share a newly created workspace with a group of 50 end users
and wants to avoid having to add users individually.
Which feature should the consultant use to solve for this?
A. Custom Permission Sets
B. Shared Data Spaces
C. Analytics Groups
Answer: C
Explanation:
Analytics Groups provide the native Tableau Next mechanism for sharing analytical assets with multiple
users as a single administrative unit. Salesforce states that Analytics Groups are specifically designed to
simplify access management by allowing an administrator to create a group, add members, and then
share Tableau Next assets with the entire group rather than adding each user individually.
That makes C the direct solution for sharing a workspace with 50 users.
Custom permission sets govern functional capabilities—what users are allowed to do in Tableau Next—
but are not the asset-sharing construct for granting workspace access to a collection of users. Data
spaces control access to Data 360 data and governance boundaries; theyare not substitutes for Tableau
Next workspace sharing.
After the Analytics Group has been created and populated, the workspace owner can use the normal
Share interface, select the group, and grant Viewer or Editor access as appropriate. The role applied to a
workspace can then be inherited by supported assets contained in that workspace, subject to each
user's underlying licenses, permission sets, and data access.
References/Topics: Managing Workspaces and Orgs - > Analytics Groups - > Workspace Sharing - >
Group-Based Access Management.
6.A Tableau Next Consultant is configuring a Salesforce action in a Tableau Next table visualization that
displays Contact records. The goal is to give sales reps the ability to trigger a screen flow that adds
selected Contacts to a Campaign.
What is a required configuration step for the action to work correctly?
A. Enable the "Multi row Selection" toggle on the table visualization before adding the Salesforce action.
B. Create a custom permission set that grants users access to trigger Salesforce actions from Tableau
Next visualizations.
C. Map the Contact ID field in the visualization to the Salesforce action.
Answer: C
Explanation:
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
5 / 9
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.
7.Cloud Kicks stores historical customer transaction data inside Snowflake. The marketing team wants to
track campaign performance in Tableau Next. However, IT compliance strictly prohibits creating duplicate
copies of this dataset due to storage costs and security synchronization risks.
Which architectural feature should a Tableau Next Consultant implement to meet these requirements?
A. Establish a Zero Copy Data Federation to map the Snowflake tables as Data Stream Objects (DSOs).
B. Create a Mulesoft integration flow that streams the dataset into standard Salesforce custom objects
through the REST API.
C. Configure a High-Volume Batch Data Transform scheduled to execute a full hourly refresh using an
encrypted JDBC connector.
Answer: A
Explanation:
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.
8.The client wants AI-generated insights about Gross Margin % in Tableau Next.
Where is the best place to define this context for the agent?
A. As a calculated field in the semantic model
6 / 9
B. As a scoped dashboard calculated field
C. As a Business Preference
Answer: C
Explanation:
For agent-specific business context about how Gross Margin % should be understood or interpreted,
Business Preferences are the best choice. Salesforce uses Business Preferences to add organization-
specific knowledge and instructions to a semantic model so Tableau Agent can interpret users' analytical
questions according to the organization's terminology and business logic.
A calculated field is appropriate when Gross Margin % itself must be mathematically derived—for
example, (Revenue - Cost) /Revenue. However, the question does not ask where to implement the
mathematical calculation; it asks where to define context for AI-generated insights. Contextual
instructions, such as what “healthy gross margin” means or which business interpretation to apply,
belong in Business Preferences.
A dashboard-scoped calculated field is even less suitable because it confines logic to a specific
downstream analytical artifact instead of enriching the governed semantic context used by Tableau Agent
across conversational experiences.
Salesforce's broader semantic architecture reinforces this separation: semantic models provide
standardized business logic and definitions, while Business Preferences augment those models with
business-specific interpretive knowledge for conversational analytics.
References/Topics: Agentic Experiences - > Business Preferences - > Tableau Agent Context - >
Semantic Model Enrichment.
9.A Tableau Next Consultant has enabled Acceleration for a connected data source, which is configured
to refresh data as frequently as every 15 minutes. However, records that have been deleted from the
source system are still appearing in Tableau Next 30 minutes later.
What is the most likely reason for this behavior?
A. Caching introduces latency, causing deleted records to take additional time before they are removed
from Tableau Next.
B. The Cache Refresh Method is set to Incremental, which does not process or reflect deleted records
from the source.
C. Acceleration for Data Connections uses caching, which does not propagate deleted records from the
source system.
Answer: B
Explanation:
When Acceleration for Data Connections is enabled, Tableau Next temporarily caches external-source
data in Data 360 to reduce runtime latency and improve query performance. Two refresh approaches are
available: Full Refresh and Incremental Refresh. Salesforce explicitly states that an incremental refresh
processes records that have been added or changed since the previous refresh but does not update
deleted data. Therefore, records removed from the source can remain present in the accelerated cache
even after several incremental refresh cycles.
This explains why the 15-minute frequency does not solve the issue. Frequency controls how often
incremental processing occurs; it does not change what the incremental algorithm processes.
Option A incorrectly attributes the behavior to ordinary cache latency.
Option C is also too broad because acceleration itself supports deletion synchronization when a Full
7 / 9
Refresh is used. A full refresh removes the existing cached dataset and replaces it with the current
source dataset.
References/Topics: Data Setup - >Data Connections - > Acceleration - > Full versus Incremental
Refresh - > Cache Refresh Method.
10.A Tableau Next Consultant is asked to configure proactive alerts for pipeline metrics.
Which license type is required to set alerts?
A. Creator.
B. Consumer.
C. Viewer.
Answer: A
Explanation:
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.
11.A Tableau Next Consultant interacts with a Tableau Next dashboard and identifies an issue with a
Tableau Next metric: It's using the wrong date field to trend the measure field. The consultant has
confirmed that the correct date field exists within the semantic model.
How should the consultant update the Tableau Next metric?
A. Update directly in the dashboard.
B. Update within Data 360 in the underlying data lake object (DLO) or data model object (DMO).
C. Update in the underlying semantic model.
Answer: C
Explanation:
The consultant should modify the metric definition in the underlying semantic model. Tableau Next
metrics are semantic-layer objects. Salesforce defines a metric as a business KPI derived from one or
more measures together with a date field, and metrics are built from semantic models.
Therefore, selecting which date dimension governs the metric's time trend is part of the metric's semantic
definition rather than dashboard presentation logic. The dashboard consumes the governed metric;
changing the dashboard would not correct the authoritative metric definition.
Option B is also inappropriate. Data Lake Objects and Data Model Objects define the underlying physical
8 / 9
/logical data available in Data 360. Because the correct date field already exists in the semantic model,
there is no requirement to modify the underlying DLO or DMO. The problem lies specifically in which
existing semantic field the metric uses for its temporal definition.
This reflects a central Tableau Next architectural principle: reusable analytical business logic—including
metrics, calculations, temporal semantics, and contextual definitions—should reside in Tableau
Semantics, while dashboards remain downstream consumption and presentation layers.
References/Topics: Data Setup - > Semantic Models - > Metrics - > Measure and Date Field
Configuration.
12.A Tableau Next Consultant is asked to configure batch data transforms.
Where is the output written?
A. Data Lake Object (DLO).
B. Data Stream Object (DSO).
C. Semantic Model (SDM).
Answer: A
Explanation:
Data Lake Object (DLO) is the correct answer among the available choices. A Data 360 Batch Data
Transform requires an Output node where the transformed results are persisted. Salesforce documents
that a Batch Data Transform can write its results to a new or existing target Data Lake Object, which can
subsequently serve as input to identity resolution, calculated insights, segmentation, semantic modeling,
or additional transforms.
A Data Stream Object is not the destination used to persist transformed output. Data streams provide
ingestion pipelines that bring source data into Data 360. A Semantic Data Model is also not the physical
output storage target; Tableau Semantics consumes governed Data 360 objects to provide measures,
dimensions, relationships, calculations, and business context.
References/Topics: Data Setup - > Data 360 - > Batch Data Transforms - > Output Nodes - > Data Lake
Objects.
13.A Tableau Next Consultant is shadowing a client's business analyst who is building a new profitability
dashboard in Tableau Next. The analyst knows exactly the business logic they need for a complex "Year-
over- Year Weighted Margin" metric, but they are new to the platform and keep getting syntax errors
when trying to write the formula.
How does generative AI in Tableau Next assist the analyst in this scenario?
A. By running a batch transform in the background to pre- calculate the metric
B. By allowing the user to describe the calculation in natural language to generate the formula
C. By creating a calculation field using the functions that matches and validates the criteria
Answer: B
Explanation:
Tableau Next provides generative AI capabilities that translate a user's natural-language description of a
calculation into a calculated-field formula. This directly addresses scenarios where an analyst
understands the required business logic but lacks familiarity with Tableau Next formula syntax.
With Draft with Einstein, the user describes the calculation they need in natural language. Einstein can
propose the field name, description, data type, aggregation type, and formula. The agentic calculated-
field experience also supports conversational refinement, allowing the user to explain requirements and
9 / 9
respond to clarification questions before reviewing the proposed field.
A batch transform, as described in A, is a data-preparation mechanism and is unrelated to helping an
analyst overcome formula-authoring syntax problems.
C is less accurate because the defining generative-AI capability being tested is the transformation of
natural-language analytical intent into a proposed formula.
The generated output remains subject to user review before creation, preserving human control over the
final semantic definition while substantially reducing formula-authoring friction.
References/Topics: Agentic Experiences - > Generative AI - > Draft with Einstein/Data Pro - > Natural-
Language Calculated Fields.
14.Sales managers at Universal Containers (UC) want to receive proactive data alerts for their Tableau
Next metrics directly within their Slack channels. UC has already enabled the Proactive Alert setting and
Agentforce for Analytics in the Salesforce org.
Which additional prerequisite must be met for users to receive these alerts in Slack?
A. Assign the 'Slack User' permission set to all sales managers.
B. Enable Collaboration with Slack and Tableau Next in Setup.
C. Create a new agent in Agentforce Builder specifically for Slack.
Answer: B
Explanation:
The additional requirement is to enable Slack for Tableau Next, represented by option B's Collaboration
with Slack and Tableau Next setting. Salesforce's current administrative workflow requires Salesforce
and Slack to be connected and the Collaborate with Slack and Tableau Next option enabled in Tableau
Next Administration.
For proactive alerts specifically, Salesforce states that an administrator must enable Slack for Tableau
Next and configure Agentforce in Slack. Once properly configured, Inspector Proactive Data Alerts can
deliver notifications into Tableau Next and Slack when a user-defined metric condition is satisfied.
Assigning a generic “Slack User” permission set is not the documented Tableau Next prerequisite in this
scenario. Users instead require an eligible Tableau Next permission set and access to the relevantasset.
Likewise, a separate analytics agent created specifically for Slack is not required merely to receive
Inspector alerts.
References/Topics: Embedding, Cross-Cloud, and Interoperability - > Slack Integration - > Inspector
Proactive Data Alerts - > Collaborate with Slack and Tableau Next.