Salesforce Certified Marketing Cloud Consultant Exam

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

The key questions to ask in this scenario are about the necessity of importing such a vast amount of historical data and whether the customer's license includes the Large Data Extensions feature. Understanding the customer's need for 10 years of historical data helps assess the relevance and potential performance implications for the Marketing Cloud environment. Additionally, knowing if the customer has the Large Data Extensions feature is crucial as it affects the capability to handle the significant volume of records efficiently. Reference: Salesforce Marketing Cloud Data Management documentation, Large Data Extensions feature specifications

To capture open-ended feedback via SMS and write it to a data extension, using a text-response message template with embedded AMPscript is the most suitable approach. This method allows for the dynamic handling and processing of the incoming SMS responses. The AMPscript can be programmed to parse the response and write the collected data to a specified data extension, making it an effective way to capture and store open-ended feedback. Reference: Salesforce MobileConnect documentation, AMPscript in MobileConnect

How many API calls are expected to be made at peak hourly rate? This question will help determine if they have enough API limits and bandwidth for importing large volumes of data via REST API into Marketing Cloud. The REST API has limits on how many requests can be made per hour per account based on license type and edition.

Why do they require 10 years' historical data in Marketing Cloud? This question will help determine if they have a valid business case and use case for importing large volumes of historical data into Marketing Cloud. Depending on their marketing objectives and strategies, they may not need 10 years' historical data in Marketing Cloud, which could reduce their storage needs and costs.

What time of day are the API calls made is not relevant to determining a solution for importing large volumes of data via REST API into Marketing Cloud, as it does not affect how data is imported or processed. Whether someone needs to be notified if an error happens on import is not relevant to determining a solution for importing large volumes of data via REST API into Marketing Cloud, as it does not affect how data is imported or processed. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_overview_large_data_extensions.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/using_the_rest_api.htm

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. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_ceb_dynamic_content_rules.htm&type=5