To avoid overwriting opportunity amount updates in NTO, what should a data architect recommend?

To ensure that opportunity amount updates in NTO are not overwritten, it's essential to control how different users and systems can access and modify this field. Making the opportunity amount field read-only for sales users via field level security effectively prevents them from making any changes to that field.

By restricting write access to the field for sales users, it allows the system, such as PPS (the integration system), to update the opportunity amount without the risk of being overridden by changes that sales users might make. This creates a clear governance structure around the data, ensuring that only one source of truth is maintained for the opportunity amount, fundamentally safeguarding data integrity.

In contrast, the other answer choices would either complicate the data architecture with additional custom fields (which may lead to confusion or inaccurate reporting) or allow for potential scenarios where different parties might make conflicting updates to the opportunity amount. Therefore, controlling the access to the field itself is a much more streamlined and effective solution.