Salesforce Certified Marketing Cloud Consultant Exam Questions

The reason why the Journey does not inject customers when their order status is updated is that orders are not being updated from not meeting criteria to meeting criteria. A Salesforce Data Entry Source only injects records into a journey when they change from not meeting the entry criteria to meeting the entry criteria. For example, if the entry criteria is order status equals New, then only orders that change from a different status to New will be injected into the journey. Orders that are created with a status of New or change from New to another status will not be injected into the journey. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_jb_salesforce_data_event.htm&type=5

To make sure the decision splits reflect the correct tent for each customer, Northern Trail Outfitters should use Entry Data as the type of data in the decision splits. Entry Data is the data that is captured at the time of entry into a journey and remains static throughout the journey. Entry Data can include data from data extensions, Salesforce objects, or API events. Using Entry Data will ensure that the decision splits are based on the tent that each customer bought at the time of entry, and not affected by any subsequent purchases or data changes. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_data.htm&type=5

Two options that would prevent the customer from duplicating records when implementing a Sales Cloud instance are:

Get existing records updated with new Keys sourced from Sales Cloud instance. This option will allow the customer to update their existing records in Marketing Cloud with new keys that match their Sales Cloud records, such as Contact ID or Lead ID. This will ensure data consistency and avoid duplication across both systems.

Continue as normal, as Marketing Cloud Contact Models will dedupe keys by Email Address. This option will allow the customer to continue using Email Address as their primary key in Marketing Cloud, and rely on Marketing Cloud Contact Models to dedupe keys by Email Address when syncing data from Sales Cloud. This will ensure data accuracy and avoid duplication within Marketing Cloud.

Uploading CSV with Migrated Subscriber Keys to All Subscribers will not prevent duplication, as it will create new records in Marketing Cloud with different keys than the existing records. Purging the current records and carrying on with new keys sourced from Sales Cloud will result in data loss and potential compliance issues. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_key.htm&type=5

To unify the messaging and branding of communications while still allowing personalization and timing of campaigns, Northern Trail Outfitters and its subsidiaries should use Distributed Marketing. Distributed Marketing is a tool that allows marketers to create consistent and compliant messages in Marketing Cloud and distribute them to Sales Cloud or Service Cloud users for sending. Distributed Marketing allows Sales Cloud or Service Cloud users to personalize and schedule messages based on their customer interactions and preferences. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_dm_distributed_marketing.htm&type=5

Three questions that are relevant to determining a solution for automating a process of importing data from a data warehouse into Marketing Cloud are:

Is the data file a delta or a historical file? This question will help determine how to handle existing records and avoid duplication or overwrite. A delta file contains only new or updated records, while a historical file contains all records regardless of changes.

Will the data file be placed on the SFTP at the same time daily? This question will help determine how to schedule an automation or trigger an event based on file drop. If the data file is placed on the SFTP at different times, then a File Drop Automation may be more suitable than a Scheduled Automation.

Does someone need to be notified if an error happens on import? This question will help determine how to handle errors and exceptions during import. If someone needs to be notified, then an email notification activity or a verification activity may be added to the automation.

Whether the data extension has a data relationship or not is not relevant to determining a solution for importing data, as it is only used for creating relationships between data extensions in Email Studio. Whether the file has more than 5,000 rows or not is not relevant to determining a solution for importing data, as it does not affect how data is imported or processed. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_as_file_drop_automation_studio_triggers.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_import_file_activity.htm&type=5