MCE-Dev-201 Exam Dumps - Salesforce Developers Questions and Answers

To configure an Email Send Logging Data Extension for a new business unit, the recommended approach is to use the SendLog Data Extension Template. This ensures that all necessary fields and configurations are correctly set up to log email send data.

SendLog Data Extension Template: This template includes predefined fields and settings that are required for logging email sends. Using this template ensures that the data extension is set up correctly for tracking send logs.

Go to Email Studio -> Subscribers -> Data Extensions.

Click on "Create".

Choose "Create from Template" and select the "SendLog" template.

Follow the prompts to configure and save the new Send Log data extension.

Salesforce Email Send Logging

When configuring an API integration component in an Installed Package, it is best practice to select the minimum required scope for the integration. This approach ensures that the integration has only the necessary permissions, enhancing security by limiting access to only what is required.

Minimum Required Scope: Selecting only the scopes that are necessary for the integration helps maintain a secure and controlled environment.

Salesforce API Integration Best Practices

To identify all subscribers who are unsubscribed from a specific Business Unit, the correct Data View to query is ListSubscribers (A). This Data View contains information about the subscription status of subscribers at the list level, including unsubscribe status for specific Business Units.

To export send data to their SFTP, the following automations can be used:

Tracking Extract > File Transfer (B) - This automation extracts tracking data and then transfers the file to an SFTP location.

Query (Data Views) > Data Extension Extract > File Transfer (C) - This automation queries the data views to gather the necessary data, extracts the data from the data extension, and then transfers the file to an SFTP location.

Profile attributes like AGE in Profile Manager are not directly accessible via the _Subscribers data view or _EnterpriseAttribute data view. To retrieve subscribers over 30 years of age, creating a filtered Group based on the AGE attribute is the most effective method.

Salesforce Subscriber Filters and Groups

To exclude sending an email at send time to those with a record on the 'Exclude' Data Extension where the primary key is Subscriber Key, the developer should use the following Exclusion Script:

ampscript

Copy code

RowCount(LookupRows('Exclude', 'SubscriberKey', _SubscriberKey)) > 0

This script checks if there are any rows in the 'Exclude' Data Extension that match the Subscriber Key. If the count is greater than 0, the email is excluded from being sent.

For a data extension to be selected for journey entry in Journey Builder, it must be configured for sending. This configuration ensures that the data extension is recognized as a source for sending communications.

Configure for Sending: When creating or editing a data extension, ensure that it is set as "Sendable." This involves specifying the appropriate fields for sending, such as Subscriber Key and Email Address.

Salesforce Journey Builder Data Extension Configuration

To retrieve daily JSON data from a customer's API and write it to a data extension, the developer should use the following set of Server-Side JavaScript activities:

Platform.Function.HTTPGet(); - To make the HTTP GET request to the customer's API and retrieve the JSON data.

Platform.Function.ParseJSON(); - To parse the retrieved JSON data.

Platform.Function.UpsertData(); - To upsert the parsed data into a data extension.

Example code snippet:

var response = Platform.Function.HTTPGet("https://api.customer.com/data "); var jsonData = Platform.Function.ParseJSON(response); Platform.Function.UpsertData("DataExtensionName", ["PrimaryKeyField"], jsonData);

When a send is initiated directly to a Sendable Data Extension that includes records targeted for deletion, the following behaviors are expected:

Records still in the suppression phase will be excluded from sends (B) - These records are in the process of being deleted and will not be included in the send.

Records that have been deleted will be excluded from sends indefinitely (D) - Once records are deleted, they are permanently excluded from future sends.

The SQL statement in question does not return any records because it is joining on the EmailAddress field, which is not present in the _Bounce Data View. The correct approach is to join using the SubscriberKey (or SubscriberID). Here is the corrected SQL statement:

SELECT s.EmailAddress, s.SubscriberKey, b.JobID, b.EventDate, b.SMTPBounceReason FROM _Subscribers s JOIN _Bounce b ON s.SubscriberKey = b.SubscriberKey WHERE b.EventDate > DateAdd(DAY, -30, GETDATE())

This ensures that the join is based on the SubscriberKey, which is a common field in both data views.