When an administrator needs to perform a "cleanup" of existing data in bulk, a Schedule-triggered flow is the most efficient choice. This type of flow can be configured to run once (or on a recurring schedule) and process all Lead records that meet the "inconsistent" criteria (e.g., Lead Source equals 'Website' or 'Online')46. The flow can then automatically update those records to the standard "Web" value. A Record-triggered flow (Option B) only works on records as they are being created or updated, so it would not fix historical data unless every record was manually touched Screen flows (Option D) require manual user interaction for each record. 53Segment-triggered flows (Option A) are used in Data Cloud marketing conte54xts rather than standard core record cleanup.

Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add "Schedule Site Visit" and "Send Contract" to the Task Subject list and "Site Visit" and "Ride Along" to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.

Best practices for Agentforce Action Instructions emphasize clarity, intent, and specific usage scenarios to help the LLM (Large Language Model) understand exactly when and why to trigger an action13. Option B is the best choice because it explicitly defines the Action (create a Case), the Goal (document a customer's issue), and the User Intent (formal record of a problem or question)14. High-quality instructions act as a guide for the agent's reasoning process15. Vague instructions, like those in Option A or C, may lead to the agent triggering the action at inappropriate times, such as during a simple inquiry that doesn't require a formal case. Instructions that focus on "code snippets" (Option D) are less effective because the LLM needs to understand the functional business context rather than the technical implementation details to interact naturally with the user17.

To create a "guided" experience combined with "routing and authorizations," a Platform Administrator should leverage the power of Flow Builder and the Approval Process engine. Flow Builder is used to create the user-facing interface (Screen Flow) that guides the employee through the expense report submission, ensuring all necessary data is collected in a structured way. This replaces a static page layout with a dynamic, step-by-step wizard. Once the data is captured and the record is created, the Flow can automatically submit the record into an Approval Process. The Approval Process then handles the "routing and authorizations" by sending the report to the appropriate manager or director for sign-off. While Quick Actions (Option B) can launch flows, they are a entry point rather than the logic engine itself. Validation Rules (Option A) only prevent errors but do not guide users or route records. Together, Flow and Approvals provide a seamless end-to-end automation for complex business requirements like expense management.

To change the display name of a standard field (like "Account Type") globally across the entire organization, the correct tool is Rename Tabs and Labels in the Setup menu. This tool allows an administrator to modify the singular and plural labels for standard objects and the field labels for their standard fields. By renaming "Type" to "Tier," the change will be reflected on page layouts, in report column headers, and in list views. This is the preferred method because it preserves the underlying data and logic associated with the standard field. Option A is incorrect because standard field names cannot be edited in the "Fields and Relationships" menu. Option C is a destructive and complex process that would require data migration and could break existing reports or integrations. Option D does not address the label of the field itself.