Option B is the currently verified Salesforce-supported approach. Marketing Cloud Next treats a prospect, Lead, or Contact without applicable consent as opted out by default. Therefore, before a new Contact can receive promotional marketing, a valid opt-in must exist for the relevant contact point, channel, and communication subscription .
Salesforce's current 2026 guidance states that consent changes originating from CRM record creation or updates should be handled with an Automation Event-Triggered Flow using the Prospect, Lead, Contact, or Related Record Change event, followed by the Consent Request/Create Consent action . That supported action writes the consent so that Marketing Cloud Next honors it at send time.
Option C is explicitly insufficient because HasOptedOutOfEmail isn't automatically synchronized with Marketing Cloud Next consent. Option A is misleading because directly manipulating a separate CRM consent record doesn't itself establish supported Marketing Cloud Next sending consent.
The uploaded document keys this question as A. However, Salesforce's updated July–August 2026 documentation supersedes that approach and explicitly directs implementations to Create Consent/Consent Request.
Study Guide Reference: Consent → Creating and Updating Consent → Create Consent / Consent Request Flow Action.
===============
