A good app builder does not chase the most familiar label. The best answer is A. Streams; D. Out of Office.
The decision turns on Chatter collaboration. Chatter supports record-centered collaboration. Feed tracking surfaces selected field changes, while groups, streams, and post actions organize discussions and follow-up work.
This is how the same requirement would be handled in a well-governed Salesforce org: identify the controlling object, relationship, field, page, automation, or environment first, and then configure the native capability for that control point. The selected answer satisfies the requirement without requiring users to perform extra interpretation or administrators to maintain an unnecessary custom workaround.
The distractors are not equal substitutes. B (Topics) is less defensible because it is not the most maintainable declarative control for this design. C (Polls) should be rejected because it works at the wrong scope for the object, field, page, automation, or deployment condition in the stem. That is the kind of solution a Salesforce admin can document, migrate, and troubleshoot without creating hidden technical debt.
For collaboration, the builder should decide whether the need is record feed visibility, group conversation, field-change tracking, or a quick action in the publisher.
For collaboration, the builder should decide whether the need is record feed visibility, group conversation, field-change tracking, or a quick action in the publisher.
---