Marketing-Cloud-Consultant Exam Dumps - Salesforce Marketing Cloud Consultant Questions and Answers

To report on ‘Not Sent’ contacts in Journey Builder, Northern Trail Outfitters should use the standard report ‘Subscribers Not Sent to’. This report shows how many contacts were not sent an email due to various reasons, such as unsubscribes, bounces, duplicates, or errors. References: https://help.salesforce.com/s/articleView?id=sf.mc_rn_subscribers_not_sent_to_report.htm &type=5

To inject customers into journey B based on email engagement in journey A, Northern Trail Outfitters should use an engagement split followed by a contact activity in journey A. The engagement split can evaluate if customers opened or clicked the email in journey A. The contact activity can update a boolean field on an engagement data extension that indicates if customers are eligible for journey B. Then, an automation can run a query activity to select the customers who have the boolean field set to true and inject them into journey B. 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_contact_activity.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

To send emails to loyalty members based on recent activity, a contact data entry source can be used to segment the data based on attributes and filters configured in Contact Builder. This allows for more flexibility and scalability than using a data extension entry source with an applied filter. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_attribute_groups.htm &type=5

A journey that allows re-entry after exiting can be used to have a periodic, dynamic newsletter send to a set data extension that changes from day-to-day. A journey with this setting can admit contacts into the journey multiple times as long as they meet the entry criteria. The View As Web Page link will not be broken when the audience is refreshed daily because the link is based on the Job ID and Subscriber ID, which are unique for each send. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_settings.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_view_as_a_web_page_link.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

To integrate a new dataset with pre-existing contacts, Northern Trail Outfitters should create a new data extension and link it to the other data extension. A data extension is a table that stores data in Marketing Cloud, such as contact information or purchase history. Data extensions can be linked by common fields or attributes using Contact Builder or SQL queries. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_data_extensions.htm &type=5

One of the considerations for upgrading Marketing Cloud Connect to Multi-Org is that once an account is upgraded to Multi-Org, it cannot be turned off. This means that the account will permanently have separate integrations for each business unit and Salesforce org, and some features may not work as expected in Multi-Org mode. References: https://help.salesforce.com/articleView?id=sf.mc_co_multi_org_account_considerations.htm &type=5

The LookupRows AMPscript function returns a rowset from a data extension that matches the specified criteria. It can be used to retrieve multiple rows of data from a data extension based on one or more column values. For example, NTO can use the LookupRows function to retrieve all rows from the second data extension that have the same session ID as the subscriber in the sendable data extension, and then loop through the rowset to display the product data for each abandoned cart item in the email. References: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic- content.meta/mc-programmatic-content/lookuprows.htm

The API user created in Marketing Cloud for Marketing Cloud Connect should have the API User checkbox selected and the Administrator & Marketing Cloud Administrator roles applied. This ensures that the user has access to all features and functions in Marketing Cloud and can perform API calls between Marketing Cloud and Sales Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_create_a_marketing_cloud_api_user.htm &type=5