Because tracking data is not synchronized to Sales Cloud, the consultant must build the non-opener logic natively inside Marketing Cloud using the Email data views. A Scheduled Automation runs a SQL Query Activity against the Sent and Open data views to isolate contacts whose last five sends show no corresponding open record, writing the result into a working Data Extension via a Data Extension Entry step. From there, a Task Activity in Automation Studio pushes that qualified segment into Salesforce as Task records against the associated Contact or Lead. This sequence works entirely on the Marketing Cloud side and does not depend on Sales Cloud tracking, satisfying the stated constraint. Option B ' s API Event Entry is a Journey Builder concept, not an Automation Studio activity chain, and doesn ' t fit a scheduled, recurring evaluation. Option C references a non-existent ' Contact Activity ' and a generic Filter Activity that cannot evaluate a five-in-a-row open pattern as precisely as SQL. Option D ' s ' Salesforce Data Entry ' is not a standard automation activity. The Task Activity specifically requires the Salesforce integration to be configured, but does not require Marketing Cloud Connect tracking to be enabled. Reference: Automation Studio Activities, Salesforce Data Views, Marketing Cloud Connect Task Activity.