What should a data architect recommend to guarantee that records are not being updated at the same time?

Universal Containers (UC) owns a complex Salesforce org with many Apex classes, triggers, and automated processes that will modify records if available. UC has identified that, in its current development state, UC runs change of encountering race condition on the same record.

What should a data architect recommend to guarantee that records are not being updated at the same time?
A . Embed the keywords FOR UPDATE after SOQL statements.
B. Disable classes or triggers that have the potential to obtain the same record.
C. Migrate programmatic logic to processes and flows.
D. Refactor or optimize classes and trigger for maximum CPU performance.

Answer: A