Changing a field type is a significant configuration change that can have downstream impacts. When converting from Text to Picklist, a Platform Administrator must be aware of two critical consequences:
List View Deletion: Any list views that use that specific custom field as a filter will be automatically deleted or the filter will be removed. This happens because the filter logic for a text field (which uses operators like "contains") is fundamentally different from a picklist (which uses "equals").
Automation Impact: Assignment rules, escalation rules, and validation rules that reference the field may be disabled or function incorrectly. Because these automations rely on specific text strings, changing the field to a picklist requires the administrator to manually review and update the logic to ensure it aligns with the new picklist values.
Option A is incorrect because Salesforce does not automatically update code references. Option C is incorrect because data loss can still occur if existing text values do not exactly match the new picklist entries.

A Bucket Column in a Salesforce report allows a user to group multiple field values into larger, more meaningful categories (buckets) without needing to create a new custom field or modify the underlying data. For instance, if a "Industry" picklist has twenty different values like "Banking," "Insurance," and "Venture Capital," a sales rep can create a bucket called "Financial Services" and place all three values inside it. When the report is run, these records are displayed under the "Financial Services" header. This is the ideal solution for ad-hoc reporting needs where the user wants to see data summarized in a way that doesn't exactly match the existing picklist structure. Report Filters (Option C) would exclude data rather than categorizing it. Unique Count (Option B) simply tells you how many distinct values exist in a column. Charts (Option D) are for visualization. Bucketing is a powerful, self-service tool for users to reorganize data for analysis.

When building prompt templates within the Prompt Builder, the most direct way to inject specific record data into the AI's instructions is through Merge Fields. Much like an email template or a mail merge, merge fields allow the administrator to reference specific fields from the object in context-in this case, the Case object. For example, an administrator might use {!$Input:Case.Subject} or {!$Input:Case.Description} within the prompt template. When the agent runs, it replaces these placeholders with the actual data from the specific case record being viewed. This ensures that the AI has the "grounding" information it needs to generate an accurate and relevant summary. While Flows (Option A) can be used for more complex data retrieval, Merge Fields are the standard, low-code tool for simple record-to-prompt data population. Agent Instructions (Option C) provide the "how-to" logic for the AI but do not themselves represent the dynamic data points from the Salesforce database.

To provide reps with an "easy way" to perform a repetitive sequence of manual tasks, Macros are the ideal solution. A Macro allows a user to perform multiple steps-such as changing a Case Status, reassigning the Case Owner, and sending a pre-written email-with a single click. When combined with Quick Actions, Macros can navigate the user interface, populate fields, and submit changes automatically. This significantly reduces manual data entry and ensures that the company's required support process is followed consistently. Case Assignment Rules (Option A) and Autolaunched Flows (Option D) are fully automated and trigger on save, which might not be appropriate if the rep needs to decide when to trigger the support request. Quick Text (Option C) only assists with typing but does not automate field changes or ownership transfers.

Agentforce is built to be dynamic, meaning it doesn't just follow a static script but rather "reasons" through a problem using an agentic loop. The feature that directly allows an agent to adapt its behavior and take specific, real-time steps based on customer input is Custom Actions3. When a customer provides information-such as a specific order number or a request to change an address-the agent identifies the user's intent and selects the most relevant action to execute4. These actions can be powered by Flows, Apex, or Prompt Templates, giving the agent the ability to interact with Salesforce data in real-time. While Data Cloud (Option A) provides the data foundation for grounding, it is the actions themselves that define the agent's behavioral capabilities6. Screen flows (Option C) provide a guided UI for humans, but custom actions are what allow the agent to function autonomously7. Tableau (Option D) is an analytics tool and does not drive real-time agent behavior8.