Marketing-Cloud-Consultant Salesforce Certified Marketing Cloud Consultant Exam (SP23) Questions and Answers

To enable data extensions for sending SMS messages from MobileConnect, Northern Trail Outfitters should add two fields to their data extensions: a field of Locale type containing the country code and a field of Phone type containing the mobile number. These fields are required for MobileConnect to identify and send messages to mobile subscribers. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_create_a_data_extension_for_mobileconnect.htm &type=5

To automate a weekly SMS message to contacts who have a birthday that week, the Refresh Mobile Filtered List activity can be used to update the filtered list based on the birth date criteria. The Outbound Send activity can then be used to send the SMS message to the contacts in the filtered list. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_refresh_mobile_filtered_list.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_outbound_send.htm &type=5

To send an email confirming opt-in when someone signs up for their emails via a form on their website, a triggered send data extension can be used to capture the form data and deploy the email. The triggered send data extension can be linked to a triggered send definition that contains the email creative and settings. The developer can use the SOAP or REST API to trigger the email from the website form, and the marketing team can change the email creative without involving the developer. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_triggered_sends.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_create_triggered_send_data_extension.htm &type=5

To pull data from the SendLog for troubleshooting based on email address without coding experience, Northern Trail Outfitters should filter data using a Filter Activity on SendLog Data Extension. A Filter Activity is an activity that allows marketers to create filtered data extensions based on criteria and conditions without coding. A SendLog Data Extension is a custom data extension that captures send-time values for each subscriber in an email send. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_filter_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_create_a_sendlog_data_extension.htm &type=5

To know the number of contacts in their account and email it to their Chief Marketing Officer on a weekly basis, Northern Trail Outfitters should schedule the Contacts Counts Standard Report. This report shows how many contacts are in Marketing Cloud across different channels and platforms. The report can be scheduled to run at a recurring interval and emailed to one or more recipients. References: https://help.salesforce.com/s/articleView?id=sf.mc_rn_contacts_count_report.htm &type=5

Supporting inbound messages in each country would require additional long code implementation for MobileConnect. A long code is a standard phone number that can send and receive SMS messages. Each country has its own regulations and requirements for long codes, so a single long code cannot be used for all markets. The other functionalities do not tie to additional long code implementation. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_long_codes.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. References: https://help.salesforce.com/s/articleView?id=sf.mc_dm_distributed_marketing.htm &type=5

To troubleshoot the connection between Sales Cloud and Marketing Cloud, a consultant should start by validating Marketing Cloud and Sales Cloud permissions for the connecting users. The connecting users are the users who authenticated Marketing Cloud Connect in both systems. They need to have certain permissions and roles in both systems to enable full functionality of Marketing Cloud Connect. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.htm &type=5

To capture customer feedback via email and create a new case in Service Cloud if a customer indicates they are unhappy with the service they have received, Northern Trail Outfitters should use an Engagement Split to capture positive or negative responses, and a Case Activity to create a new case in Service Cloud. An Engagement Split is an activity that allows marketers to route contacts based on their engagement with email messages, such as opens or clicks. A Case Activity is an activity that allows marketers to create cases in Service Cloud based on contact attributes or journey data. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_case_activity.htm &type=5

This personalization string is used to direct a subscriber to a web version of the email, allowing them to view the email online even if their email client does not support HTML. For more information on personalization strings, please see the documentation here: https://help.salesforce.com/articleView?id=mc_es_personalization_strings.htm &type=5.

The %%view_email_url%% personalization string is a system-generated link that allows subscribers to view a web page version of an email. It can be included as the href attribute in a ‘view online’ link in an email template to enable users to view the email in a browser if they have trouble viewing it in their email client. The %%view_as_webpage%% personalization string is deprecated and should not be used. The %%vawp%% personalization string is an alias for %%view_as_webpage%% and should not be used either. The %%view_online%% personalization string does not exist. References: https://help.salesforce.com/articleView?id=sf.mc_es_view_email_url_personalization_string.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_view_as_web_page_personalization_string.htm &type=5

 To integrate Marketing Cloud with their existing point-of-sale system in order to email purchase receipts to their customers, Northern Trail Outfitters should use MuleSoft Anypoint Platform. MuleSoft Anypoint Platform is a tool that allows marketers to connect and integrate different systems and applications using APIs and connectors. MuleSoft Anypoint Platform can help transform and map data between different formats and protocols, such as JSON and SOAP. References: https://www.mulesoft.com/platform/anypoint-platform

Querying contacts from the Einstein Engagement Frequency data extension when creating the send can be used to limit the number of emails a subscriber receives to a maximum of one email every 14 days. The Einstein Engagement Frequency data extension contains information about how often each subscriber engages with emails and what is their optimal send frequency. By filtering the data extension based on the optimal send frequency, the send can exclude subscribers who have already received an email within the last 14 days. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_einstein_engagement_frequency.htm &type=5

To choose a subscriber key for Marketing Cloud, Northern Trail Outfitters should use a value that is unique, persistent, and channel-agnostic. A CRM ID or a loyalty program number are both good options, as they meet these criteria and can be used to identify and track subscribers across different channels and platforms. Email and mobile device ID are not good options, as they are not unique or persistent (subscribers can change their email or device) and they are specific to one channel (email or mobile). References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5

To ensure there’s a limit to the number of times a particular image asset can be chosen for a customer, Northern Trail Outfitters should set fatigue rules for the product asset classes. Fatigue rules are settings that allow marketers to control how often an asset can be selected for a customer within a specified time period. For example, a fatigue rule can prevent an asset from being selected more than once in 14 days. References: https://help.salesforce.com/s/articleView?id=sf.mc_ceb_einstein_content_selection_fatigue_rules.htm &type=5

To import the data, segment the data, and execute the daily sends as soon as the file is generated by the data lake instance, Northern Trail Outfitters should use a triggered automation that contains an import activity, a series of query activities, and a series of sends. A triggered automation can start when a file is dropped in a specified location, such as an FTP folder. An import activity can import the file into a data extension. A series of query activities can segment the data based on the criteria for different campaigns. A series of sends can send the emails to the segmented data extensions. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio_triggers.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_import_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_create_a_user_initiated_email_interaction.htm &type=5

To configure a sending domain in Marketing Cloud, the customer needs to delegate a subdomain to Marketing Cloud and modify their DNS entries to point to Marketing Cloud’s servers. These questions will help determine if the customer has the authority and ability to do so. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

How to determine engagement should be resolved prior to generating the audience for sending a special discount offer to engaged customers on their email list. Engagement is a measure of how subscribers interact with emails, such as opening, clicking, or converting. Different criteria can be used to define engagement, such as frequency, recency, duration, or channel preference. Determining engagement can help segment the audience and target the most relevant customers for the offer. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_engagement_metrics.htm &type=5

To process the correct subscribers who are added to a data extension via API for a monthly payment reminder journey, Northern Trail Outfitters should use Contact Evaluation > Evaluate new records only. Contact Evaluation is a setting that defines how contacts are evaluated for entry into a journey based on their entry source. Evaluate new records only is an option that allows only new records that are added to the entry source after the journey is activated to enter the journey. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_contact_evaluation.htm &type=5

To recommend a scalable business unit hierarchy for Northern Trail Outfitters and its three subsidiaries, the consultant should suggest one parent BU and three child BUs with their own Sender Authentication Packages. This will allow each subsidiary business to have their own branding, content, and subscribers, as well as access to aggregate reporting and shared subscribers from the parent BU. Each child BU should have its own Sender Authentication Package to authenticate its email sends with its own domain and branding. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_business_unit_setup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

To send an email to one million contacts in Sales Cloud using 10+ fields to segment contacts, Northern Trail Outfitters should send to a Salesforce Report from Marketing Cloud using Email Studio Send Flow. Sending to a Salesforce Report allows marketers to use existing reports in Sales Cloud as target audiences in Marketing Cloud without importing or syncing data. Using Email Studio Send Flow allows marketers to select an audience, an email message, and other options for sending an email campaign. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5

To send notifications to customers when their orders are ready for in-store pickup via SMS or email depending on their communications preference, Northern Trail Outfitters should use a Journey Builder multi-step journey with an API entry event and a decision split. A Journey Builder multi-step journey allows marketers to create personalized customer experiences across different channels and platforms. An API entry event allows marketers to inject contacts into a journey based on real-time events or data from external systems, such as order status updates. A decision split allows marketers to route contacts to different paths or activities based on their attributes or behaviors, such as communications preference. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_api_event.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_decision_split.htm &type=5

To send an email with 10 personalized fields from multiple data extensions to an audience of over one million subscribers, Northern Trail Outfitters should create and send to a sendable data extension containing those needed fields using a query activity. A query activity can join and filter data from multiple data extensions and populate a sendable data extension with the required fields for personalization. This will improve the email send performance and avoid timeouts or errors. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_send_email_using_a_data_extension.htm &type=5

A contact is a person who interacts with a brand across one or more channels, such as email, mobile, web, etc. A contact is identified by a contact key, which is usually the same as the subscriber key in Marketing Cloud or the contact or lead ID in Sales Cloud. When users register with the mobile app, they will create new contacts in Marketing Cloud with their device IDs as contact keys. However, these contacts will not be associated with their contact keys in Sales Cloud until they are synchronized through Marketing Cloud Connect, which can take up to 24 hours. Therefore, newly registered users will create additional contacts in Marketing Cloud until they are matched with their existing contacts in Sales Cloud. References: https://help.salesforce.com/articleView?id=sf.mc_co_what_is_a_contact.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implementing_contacts_in_the_marketing_cloud.htm &type=5

To initiate sends when contacts for select accounts are created, Northern Trail Outfitters should use a Salesforce Data Entry Source on the Contact Object. A Salesforce Data Entry Source is a feature that allows marketers to inject contacts into a journey based on changes or events in Sales Cloud objects, such as contacts or accounts. Using a Salesforce Data Entry Source on the Contact Object will allow Northern Trail Outfitters to trigger sends when a contact record is created for a specific account. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_salesforce_data_event.htm &type=5

Datorama is a product that enables marketers to connect and unify their data sources, visualize and analyze their data, and optimize their marketing performance. Datorama can help NTO centralize their analytics data from Marketing Cloud, Sales Cloud, and other sources, and provide insights and recommendations to drive return on investment and growth via their marketing sends. References: https://www.salesforce.com/products/marketing-cloud/platform/datorama-marketing-intelligence/ https://help.salesforce.com/articleView?id=sf.mc_dtm_datorama.htm &type=5

 To simplify the sending process using Marketing Cloud with as little additional setup as possible, the customer should create a journey and use Salesforce Data and the Reports object as the entry source. This will allow them to use their existing complex reports in Sales Cloud as criteria for injecting contacts into the journey and sending them emails. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_salesforce_data_event.htm &type=5

SSH key authentication is a method of authenticating FTP users using SSH keys instead of passwords. SSH keys are more secure than passwords because they are encrypted and do not expire or need to be changed periodically. By requesting SSH key authentication to be enabled for their FTP user and creating an SSH key in key management, NTO can upload data files to Marketing Cloud using SFTP without having to update their file transfer script on the data warehouse each time a password changes and without compromising security. References: https://help.salesforce.com/articleView?id=sf.mc_overview_enable_ssh_key_authentication_for_ftp_users.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_overview_create_an_ssh_key_in_key_management.htm &type=5

A query activity is an automation studio activity that allows querying data from data extensions or data views using SQL statements. A data extension entry source is a journey builder entry source that allows injecting contacts into a journey based on a data extension. Journey activities are actions that occur within a journey, such as sending an email or updating a contact attribute. By using a query activity to filter contacts who have not made a purchase in the last six months from their order data extension, NTO can create a sendable data extension with those contacts and use it as a data extension entry source for their journey. Then, by using journey activities, they can communicate the same message across all channels to those contacts. References: https://help.salesforce.com/articleView?id=sf.mc_as_sql_query_activity.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_data_extension_entry_source.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_journey_activities.htm &type=5

Creating and enabling a BLOCKOUT window in MobileConnect can be used to prevent SMS messages from being sent during certain hours of the day. A BLOCKOUT window is a time period during which no messages are sent or received by MobileConnect, regardless of when they were scheduled or triggered. References: https://help.salesforce.com/articleView?id=sf.mc_moc_blockout_window.htm &type=5

This allows you to specify the exact name of the file when running the automation. The File Drop Starting Source is an automation activity that allows you to specify the source of the File Drop as either a Scheduled or Manual event. This allows you to control when the data is imported from the Enhanced FTP file.

To set up their automation to import the data from the file on a nightly basis, Northern Trail Outfitters should use two ways to start their automation:

• File Drop Starting Source. This is a trigger that starts an automation when a file is dropped in an Enhanced FTP folder or an external SFTP location.
• Scheduled Starting Source. This is a trigger that starts an automation at a specified date and time or at recurring intervals.

%%BASEFILENAME_FROM_TRIGGER%% and %%BASEFILENAME_FROM_FILEDROP%% are not starting sources, but variables that can be used in file transfer or import activities to reference file names. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio_triggers.htm &type=5

Using RMM personalization strings to render the email reply body can be used to include the body of marketing email replies captured by Reply Mail Management (RMM) within auto-forwarded messages to their Customer Success team. RMM personalization strings are variables that can be inserted into auto-forwarded messages to display information from the original reply message, such as subject line, sender address, or reply body. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_reply_mail_management_personalization_strings.htm &type=5

Synchronized data extensions are data extensions that are automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. They can be configured with filters to limit the records that are imported based on criteria such as field values or record types. By using synchronized data extensions with a filter on the consent checkbox field, NTO can import their Sales Cloud data into Marketing Cloud and leverage it within Journey Builder. Synchronized data extensions can be refreshed as frequently as every 15 minutes, which meets the requirement of having no more than 30 minutes delay. References: https://help.salesforce.com/articleView?id=sf.mc_co_data_integration_synchronized_data_sources.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implement_synchronized_data_sources_best_practices.htm &type=5

Publication List and Auto-Suppression List can be used to control what content is available to certain users and business units based on their preferences and send volume. A Publication List allows subscribers to opt in or out of different types of communications, while an Auto-Suppression List automatically excludes subscribers from receiving certain messages based on criteria such as frequency or content category. References: https://help.salesforce.com/articleView?id=sf.mc_es_publication_lists.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_auto_suppression_lists.htm &type=5

To inject contacts into journey B based on email engagement in journey A, Northern Trail Outfitters should use an engagement split followed by an update contact activity to a Boolean field on an engagement data extension in journey A, and query the engagement data extension for journey B injection. An engagement split is an activity that allows marketers to route contacts based on their engagement with email messages, such as opens or clicks. An update contact activity is an activity that allows marketers to update contact attributes or data extension fields based on journey data. A query activity is an activity that allows marketers to retrieve data from data extensions using SQL queries. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_update_contact_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5

A consideration that should be made when building dynamic content rules is that rules should be built before uploading the respective content. Dynamic content rules are rules that define what content should be displayed based on subscriber attributes or behaviors. Dynamic content rules should be created before uploading content blocks or images into Content Builder, as they cannot be edited after content is uploaded. References: https://help.salesforce.com/s/articleView?id=sf.mc_ceb_dynamic_content_rules.htm &type=5

Using an import activity to import a file from the SFTP can be used to maintain an auto-suppression list. An import activity allows users to import data from a file on the Marketing Cloud FTP into a data extension or list. An auto-suppression list is a type of exclusion list that prevents subscribers from receiving certain types of messages based on criteria such as email address, subscriber key, or domain. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_import_file_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_auto_suppression_lists.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

Three tasks that a consultant would suggest for using Journey Builder instead of Automation Studio are:

• Building simple segmented campaigns without SQL queries. Journey Builder allows marketers to create simple segmented campaigns using filters and rules without writing SQL queries. Automation Studio requires SQL queries for creating complex segments using data extensions.
• Designing decision logic via an intuitive user interface. Journey Builder allows marketers to design decision logic using activities such as decision splits, engagement splits, or random splits via an intuitive user interface. Automation Studio requires scripting or coding for creating decision logic using activities such as script activities or verification activities.
• Setting behavior-based goals. Journey Builder allows marketers to set behavior-based goals using criteria such as email opens, clicks, conversions, or custom events. Automation Studio does not have a feature for setting behavior-based goals.

Processing zipped encrypted files containing subscriber data is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as file transfer activities or import file activities that can handle zipped encrypted files. Creating customer segments from multiple data extensions is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as query activities or filter activities that can create customer segments from multiple data extensions. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio.htm &type=5

To provide near real-time data in a 30-day welcome journey, Northern Trail Outfitters should use contact data using synchronized data sources. This will allow them to access the most up-to-date data from their CRM system in decision splits and other journey activities. Journey data is static and based on the entry source data extension, which may not reflect recent changes in CRM. Contact data mapped through profile attributes or imported from CRM reports may not be as timely or accurate as synchronized data sources. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_synchronized_data_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_decision_split.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. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_data.htm &type=5

A decision split activity is a journey builder activity that allows branching the journey based on attribute values or engagement behavior of each contact. Contact data refers to data that is stored outside the journey, such as in data extensions or data views. Journey data refers to data that is captured at the moment of entry into the journey, such as from a Salesforce entry event. By using both contact and journey data in a decision split activity, NTO can compare attribute values from different sources using an attribute-to-attribute comparison. For example, they can compare the promo code from the transaction data extension (contact data) with the promo code from the entry event (journey data) and divert contacts who have redeemed the promo code before reminder emails are sent. References: https://help.salesforce.com/articleView?id=sf.mc_jb_decision_split.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_attribute_to_attribute_comparison.htm &type=5

A filtered keyword list is a list of words or phrases that trigger an automated response when a subscriber replies with them to an email. For example, if “take me off your list” or “opt out” are added to a filtered keyword list with an unsubscribe action, any subscriber who replies with those phrases will be automatically unsubscribed from future emails. This can help NTO handle manual unsubscribe requests more efficiently and avoid sending unwanted emails to their customers. References: https://help.salesforce.com/articleView?id=sf.mc_es_reply_mail_management.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_create_a_filtered_keyword_list.htm &type=5