The implementation choice has to match the object context. Use B. Feed Tracking. The selected option is not chosen because it sounds familiar; it is chosen because it gives Salesforce the right instruction at runtime.
Chatter supports record-centered collaboration. Feed tracking surfaces selected field changes, while groups, streams, and post actions organize discussions and follow-up work.
The scenario describes a business outcome, not merely an administrative preference. If the feature is configured correctly, users get the intended result without depending on memory, spreadsheets, or manual policing. That is the professional standard for Platform App Builder work: place the rule in metadata, test it under the correct permissions, and keep the design supportable.
The other choices would leave a gap in the implementation. A (Topics) misses the mark because it addresses a neighboring feature area rather than the exact behavior requested. C (Pin Field) handles a different concern; it handles only part of the requirement and leaves the controlling Salesforce behavior unresolved. D (Publisher Actions) is less defensible because it is not the most maintainable declarative control for this design. In a real org, the builder should include negative testing as well, proving that the rule does not fire or display outside the intended conditions.
---