Marketing-Cloud-Consultant Practice Questions

An entry source filter is a filter that can be applied to an entry source in journey builder to limit which contacts are injected into a journey based on criteria such as field values or record types. A decision split is a journey builder activity that allows branching the journey based on attribute values or engagement behavior of each contact. By using an entry source filter on their order data extension, NTO can filter contacts whose status has changed to ‘shipped’ that day and inject them into their journey. By using a decision split within their journey, they can further segment contacts based on other criteria such as purchase amount or product category. References: https://help.salesforce.com/articleView?id=sf.mc_jb_entry_source_filter.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_decision_split.htm &type=5

Three considerations that should be made before implementing MobileConnect are:

• Long and Short Codes are not available for all countries. Long codes are local phone numbers that can be used for sending SMS messages in some countries, while short codes are special numbers that can be used for sending SMS messages in other countries. However, not all countries have long codes or short codes available or supported by MobileConnect.
• Inbound messaging only works with local Long or Short Codes. Inbound messaging is the ability to receive SMS messages from subscribers in response to outbound messages or keywords. This feature only works with local long codes or short codes that match the country of the subscriber’s mobile number.
• Not all countries are supported by MobileConnect. MobileConnect relies on mobile operators and aggregators to deliver SMS messages to different countries, but not all countries have these services available or supported by MobileConnect.

NTO would not be charged by mobile operators directly for messages, as they would pay for message credits or bundles through Marketing Cloud billing. Opting in for messages can be done via inbound message or other methods, such as web forms or APIs. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_mobileconnect_overview.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 I

  D.  

  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. References: 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