This is a governance decision before it is a configuration click. The proper configuration is A. Field History tacking. The requirement in the stem is: Universal Containers uses a custom picklist called `Account_Region ` or the Account object. The vice president of sales has asked that the value of this field is visible on Opportunities. How should an app builder. The selected option addresses that requirement at the point where Salesforce actually evaluates the behavior.
The underlying concept is platform configuration. The Platform App Builder role is to choose the standard Salesforce capability that owns the behavior: data structure, access, automation, user experience, reporting, or deployment. That is why this answer is more defensible than a workaround. It can be reviewed in Setup, included in the correct deployment path, and tested by impersonating or logging in as a representative user where appropriate.
The rejected choices solve different problems. B (Cross-object formula) should be rejected because A formula is calculated display logic and cannot always store static values or perform record updates. C (Linking field) would be fragile here because it could produce an inconsistent result once different users, records, or apps are tested. D (Field-level security) does not fit cleanly; Permission controls are essential for access, but they do not perform calculations or process automation. The configuration remains understandable for future admins because the decision is visible in metadata rather than buried in a workaround.
---