Universal Containers has a requirement that an opportunity should have a field showing the value of its associated account's billing state. This…

A record-triggered flow is the most suitable declarative tool for this requirement. The flow can be configured to trigger when an Opportunity record is created. It can then get the Billing State value from the related parent Account record and update a custom text field on the new Opportunity. This process copies the value at the moment of creation, ensuring it remains static and does not change later if the Account's Billing State is updated. This approach adheres to the "clicks not code" principle.

A. Roll-up summary field: This is incorrect because roll-up summary fields aggregate data from child records onto a parent record, not copy data from a parent to a child.

B. Formula field: This is incorrect because a formula field is dynamic. It would always display the current Billing State of the Account, violating the requirement for the value to be static.

D. Apex: While Apex could solve this, it is a programmatic solution. A declarative tool like Flow is sufficient and preferred for this type of automation, aligning with Salesforce best practices.

---

1. Flow: Salesforce Help, "Record-Triggered Flows". This document explains that a flow can be triggered to run "When a record is created" and can be used to "Update any record". The flow would use the $Record.AccountId to access the parent Account's fields and populate the new Opportunity.

2. Formula Fields: Salesforce Help, "Formula Field Considerations". This documentation states, "A formula field is calculated at runtime when a record is accessed." This confirms its dynamic nature, which contradicts the "static" requirement.

3. Roll-Up Summary Fields: Salesforce Help, "Roll-Up Summary Field". This source defines a roll-up summary field as one that "calculates values from related records, such as those in a related list." This confirms it operates from child to parent (e.g., Opportunities to Account), which is the opposite of the required data flow.

4. Automation Tool Choice: Salesforce Architects, "Record-Triggered Automation Decision Guide". This guide recommends using Flow for "all declarative record-triggered automation" and positions it as the primary tool before considering programmatic solutions like Apex triggers. This supports choosing Flow over Apex for this scenario.