The correct mapping is Dynamic Widget Field with a Selection interaction because the flow input must depend specifically on a value that the user selects in another dashboard widget. Salesforce distinguishes two dynamic interaction types when mapping dashboard data to Salesforce Flow inputs: Selection and Result. A Selection interaction passes the value resulting from the user's selection in a widget, whereas a Result interaction passes a value derived from the widget query results.

A Static String would supply the same manually configured value every time and therefore cannot satisfy a requirement in which the flow input changes according to what the user clicks.

Operationally, the consultant configures the Salesforce Flow action, identifies the required flow input, selects Dynamic Widget Field, chooses the source widget and field, and sets the interaction type to Selection. This creates an actionable analytical experience where a user's interaction with dashboard data can directly feed contextual values into a Salesforce business process.

References/Topics: Visualizations and Dashboards - > Analyze and Share Data - > Add Single-Click Actions to Your Data - > Salesforce Flow Actions.

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

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.

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

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 relevant asset. 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.

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

A Data Stream Object (DSO) is the output associated with streaming data ingestion in this question. Streaming ingestion is designed to continuously accept incoming records from a connected source and represent that stream in Data 360 so downstream processing and analytics can work with newly arriving data with minimal delay.

A Data Lake Object is used as a persisted data-layer object for broader ingestion and storage scenarios, while a Semantic Model is a downstream analytical abstraction that defines business-friendly measures, dimensions, relationships, metrics, and other semantic logic. Neither option describes the streaming-ingestion output requested by this item.

The exam distinction is to keep the ingestion pipeline separate from the semantic layer. Streaming data first enters through the streaming/data-stream construct, where the Data Stream Object represents the incoming stream. That data can then participate in downstream mapping, modeling, and Tableau Next analytics. The semantic model does not serve as the raw ingestion target; it consumes prepared and governed data structures to provide analytical meaning.

References/Topics: Data Setup - > Streaming Data Ingestion - > Data Stream Objects.

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

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.

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