All Marketing-Cloud-Consultant Test Inside Salesforce Questions

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: &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: content.meta/mc-programmatic-content/lookuprows.htm

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:  &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: &type=5 &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: &type=5 &type=5