Universal Containers requires that when an opportunity is closed won, all other open opportunities on the same account must be rendered as Closed…

This requirement involves an automated process that triggers upon a specific record update (Opportunity Stage = 'Closed Won') and then performs actions on other related records (updating other open Opportunities on the same Account). Flow Builder is the designated Salesforce tool for creating such complex, record-triggered automations. An administrator can build a record-triggered flow that fires when an Opportunity is updated to 'Closed Won'. The flow would then get the Account ID, find all other related Opportunities that are not yet closed, and update their stage to 'Closed Lost'. This aligns perfectly with the capabilities of Flow Builder.

B. Outbound Message: This is used for sending data to an external system via a SOAP API call and cannot be used to update records within Salesforce.

C. Flow Orchestration: This is designed for coordinating complex, multi-step, multi-user processes and is overkill for this straightforward, background automation requirement.

D. Quick Action: This requires manual user initiation (e.g., clicking a button). The requirement is for a fully automated process that runs in the background upon saving a record.

1. Salesforce Help Documentation, "Record-Triggered Flows": "A record-triggered flow runs when a record is created or updated... Record-triggered flows can update any record in the database..." This source confirms that a flow can be triggered by a record update and can subsequently update other records, which is the core of the requirement. (Salesforce Help, "Flow Builder," Record-Triggered Flows section).

2. Salesforce Architects, "Architect's Guide to Record-Triggered Automation on Salesforce": This guide provides a decision framework for choosing automation tools. For a process that needs to execute after a record is saved and needs to access and update other records, the guide directs administrators to use a record-triggered flow. It explicitly states, "For all other 'after-save' use cases, we recommend Flow." (Salesforce Architects, "Record-Triggered Automation Decision Guide," After-Save Flow path).

3. Trailhead, "Flow Builder" Module, "Record-Triggered Flows" Unit: "Use record-triggered flows to automate your business processes when a record is created or updated... For example, when an opportunity's stage is updated to Closed Won, create a renewal opportunity." This example demonstrates a similar use case of triggering a process from an Opportunity stage change, validating the use of Flow Builder for the scenario. (Trailhead, "Flow Builder" Module).