Northern Trail Outfitters needs to update an individual's consent in near real time when a...

An Automation Event-Triggered Flow with the supported consent action is the correct architecture for processing consent immediately after a Marketing Cloud Next form submission. Salesforce specifically states that Create Consent can be used in event-triggered flows to automate consent updates based on events such as a form submission .

Current Salesforce documentation commonly labels the Flow element Create Consent , while some recent support guidance still refers to the underlying operation as Consent Request . The functional purpose is the same in this question: update the contact point's OPT_IN or OPT_OUT state for the appropriate channel and communication subscription through the supported Marketing Cloud Next consent service.

Options B and C are incorrect because directly mapping ingestion or transformation results into the Communication Subscription Consent DMO isn't the supported consent-writing path. Salesforce's August 17, 2026 guidance specifically states that landing-page form consent should be paired with an Automation Event-Triggered Flow and Consent Request action.

The uploaded master correctly keys A.

Study Guide Reference: Consent → Automating Consent → Form Submission, Automation Event-Triggered Flow, and Create Consent/Consent Request.

===============