A developer is asked to prevent anyone other than a user with Sales Manager profile from changing the Opportunity Status to Closed Lost if the lost reason is blank. Which automation allows the…

A record trigger flow could achieve this by raising a custom error, but a validation rule is purpose-built for preventing invalid record saves and is generally more efficient for such direct validation requirements.

An Apex trigger could implement this logic programmatically, but it requires coding and maintenance, making it less efficient than a declarative validation rule for this straightforward requirement.

An approval process is designed for multi-step approval workflows and is not an efficient mechanism to simply prevent a record save based on immediate field conditions and user profiles.

An error condition formula on a validation rule on the Opportunity object is the most efficient declarative automation, as it can directly evaluate the Opportunity Status, check for a blank Lost Reason, and verify the user's profile to prevent the record from being saved if the conditions are met.