Free Practice Questions for Salesforce MCE-Admn-201 Exam

Synchronized Data Sources can use two types of filters: attribute filters and relationship filters. Attribute filters are based on the fields of the object being synced, such as email address or opt-out status. Relationship filters are based on the fields of a related object, such as account or campaign. Filtering by email open activity or subscriber status is not possible with Synchronized Data Sources.

Following a Contact Delete request in Salesforce Marketing Cloud, certain types of data remain within the account:

Contact data in sendable data extensions: This data is not automatically removed through a Contact Delete process unless specifically targeted. It requires separate processes to ensure data is cleansed.

General tracking data at the job level: This includes aggregate performance metrics from email campaigns, which do not store individual contact details but rather overall campaign performance stats.

When creating a data extension for subscriber data from a data warehouse, fields that typically require minimal consideration for size or scalability include:

Number: Fields designated as 'Number' generally consume less storage space and are straightforward in terms of scalability and processing within data extensions.

Boolean: Boolean fields, representing simple true/false values, are highly efficient in terms of storage and processing, making them less of a concern in terms of scalability.

The advantages of using data extensions over lists in Marketing Cloud, especially given the complex data needs outlined:

Add/Update Capability: Data extensions support add/update import activities, allowing for the nightly refresh of the customer data from the data warehouse without duplicating records.

Handling Large Data Volumes: Data extensions are more suitable for managing large volumes of data with numerous attributes, such as the scenario described with 5 million records and 40+ attributes.

Regarding Send Logging in Marketing Cloud:

B. AMPscript can be used to pull data from Send Logs for use within emails: AMPscript can retrieve and display data stored in Send Logs during email sends, allowing for dynamic content based on previous interactions.

C. SQL Query Activities can reference Send Logs in combination with system data views: SQL Query Activities enable more complex data retrieval and analysis, including combining Send Log data with other system data views for comprehensive reporting and segmentation.

These points underscore the functionality and utility of Send Logs in enabling dynamic content and deeper data analysis within Marketing Cloud.

The Content Builder Settings under Setup allow the admin to create a default Header and Footer for emails. These settings apply to emails created in Content Builder only. The other settings do not have an option to create a default Header and Footer for emails.

The behavior where customers unsubscribe via the Marketing Cloud default Profile Center and do not receive emails from any other business unit is explained by:

D. Business unit unsubscribe setting causes an Enterprise level unsubscribe. This setting means that when a subscriber opts out using the default Profile Center, they are unsubscribed at the enterprise level, impacting all business units within the organization.

 Einstein Email Recommendations is a product that enables a Marketing Cloud admin to observe customer behavior, build performance profiles and deliver the next best content. This product uses predictive intelligence to recommend products or content based on each customer’s preferences and actions. The other products do not have this capability.