Salesforce MCE-Dev-201 Salesforce Certified Marketing Cloud Engagement Developer Exam Practice Test

The newly created data model in Contact Builder can be used for segmentation in the following applications:

Email Studio (A) - Email Studio can use data extensions and attribute groups from Contact Builder for segmentation.

Journey Builder (C) - Journey Builder can leverage the data model created in Contact Builder for creating targeted journeys and audience segments.

AMPscript is evaluated in the following order before an email is sent:

Subject Line: Evaluates AMPscript in the subject line first.

HTML Body: Evaluates AMPscript within the HTML body of the email.

Text Body: Evaluates AMPscript within the text body of the email.

This order ensures that any dynamic content or personalization logic is correctly applied in all parts of the email.

Salesforce AMPscript Evaluation Order

To ensure that an installed package can access data from a child business unit, verify that the package has been granted access to the specific child business unit. This is configured during the package setup and permissions assignment.

Salesforce Installed Packages and Business Unit Access

When importing an encrypted file from the Enhanced FTP server, you need to move the file to the Safehouse first, and then decrypt it within the Safehouse.

Move to Safehouse: Use a File Transfer activity to move the encrypted file from the Enhanced FTP server to the Safehouse.

Decrypt in Safehouse: Use another File Transfer activity to decrypt the file within the Safehouse.

Salesforce File Transfer Activities

To retrieve subscribers who were sent emails with names starting with "TEST," we need to join the _Job and _Sent system data views on the JobID field and filter by the EmailName field using a LIKE condition.

Join Condition: The correct join condition between _Job and _Sent is ON J.JobID = S.JobID. This ensures that we are linking the job and sent data correctly.

EmailName Filter: We use J.EmailName LIKE 'TEST%' to filter for emails whose names start with "TEST".

SELECT * FROM _Job J INNER JOIN _Sent S ON J.JobID = S.JobID WHERE J.EmailName LIKE 'TEST%'

Salesforce Marketing Cloud System Data Views

A 401 Unauthorized HTTP status message indicates that the request was not authenticated properly. This error commonly occurs when the access token is missing, invalid, or expired.

Access Token Issues: The most common cause of a 401 error in REST API requests is related to the access token. The request must include a valid access token in the authorization header.

Example Authorization Header: Authorization: Bearer YOUR_ACCESS_TOKEN

Salesforce API Access Tokens

In the provided AMPscript, the IF statement checks the length of the @point variable and sets @value accordingly. Since x = 'Tacos' has a length of 5, it meets the first condition Length(@point) > 1, which sets @value to 1. Subsequent conditions are not evaluated because the first condition is already true.

AMPscript IF-ELSEIF Example:

%%[ SET @point = RequestParameter('x') SET @value = 5 IF Length(@point) > 1 THEN SET @value = 1 ELSEIF Length(@point) > 2 THEN SET @value = 2 ELSEIF Length(@point) > 3 THEN SET @value = 3 ELSEIF Length(@point) > 4 THEN SET @value = 4 ENDIF ]%%

Salesforce AMPscript Documentation

The Event Notification Service (ENS) in Salesforce Marketing Cloud provides real-time event notifications, such as email opens and clicks. Using ENS, Northern Trail Outfitters can trigger follow-up messages based on real-time engagement data.

Salesforce Event Notification Service

The JobID parameter is required for the LogUnsubEvent request to be tied to the appropriate send. The JobID uniquely identifies the email job that was sent, allowing the system to accurately log the unsubscribe event for that specific send.

JobID: This parameter ensures that the unsubscribe event is correctly associated with the email send job.

Salesforce LogUnsubEvent Documentation

When the subjectLine variable is declared in multiple locations throughout the email, the value used at the time of deployment will be the last value assigned to the variable. In the provided declarations, the last assignment is:

%%[ SET @subjectLine = 'Enjoy 20% off today' ]%% was declared within the Subject Line

Therefore, the subject line used at the time of deployment will be "Enjoy 20% off today" (C).

A developer would use the LookupRows function instead of the Lookup AMPscript function to return a complete rowset from the data extension (A). The LookupRows function retrieves all rows that match a specified criterion, returning a rowset that can be further processed or iterated over in AMPscript. In contrast, the Lookup function retrieves only a single field value from the first row that matches the specified criteria.

To ensure a blank email will not be sent when creating a complex dynamic email with multiple sections and content blocks, the developer should confirm every version has default content (D). This practice ensures that if any dynamic content fails to load or meet the conditions, the default content will be displayed, preventing a blank email from being sent.

To optimize the performance when retrieving a large number of rows from a data extension via the API, the following solutions can be used:

Use the REST API instead of the SOAP API (A) - The REST API generally offers better performance for data retrieval operations compared to the SOAP API.

Use the ContinueRequest feature (C) - This feature allows for the pagination of results, enabling the retrieval of large datasets in manageable chunks.

Using the RaiseError AMPscript function allows a developer to handle errors when necessary data for building an email is missing. The possible outcomes of using this function include:

The send fails (A) - The entire email send can be stopped if a critical error is encountered.

The email is not sent to the particular subscriber (B) - The send can be aborted for specific subscribers who do not have the necessary data.

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

The tracking data views in Salesforce Marketing Cloud, such as _Sent, _Open, and _Click, store data for a limited period.

Data Retention Period: Salesforce Marketing Cloud retains tracking data for up to six months in the data views. This means that developers can query up to six months of tracking data using these views.

Salesforce Marketing Cloud Data Views

To build out a series of CloudPages that will interact with several REST APIs, the developer should use SSJS (Server-Side JavaScript) (C). SSJS is supported in Marketing Cloud and provides robust capabilities for interacting with external APIs, handling HTTP requests, and processing data.

A "401 Unauthorized" error typically indicates an issue with authentication or permissions. Since the Client ID and Client Secret have been successfully used in other REST calls, the most likely cause is insufficient permissions for sending emails.

Check Send Permissions: Ensure that the appropriate permissions for sending emails have been granted to the Client ID and Client Secret in the Installed Packages. Without these permissions, the API call will fail with a 401 error.

Salesforce Installed Packages and Permissions

To transform the date and time 'Data_Enrolled' from Daylight Savings time and fall back one hour, the developer should use the following AMPscript function:

%%=DateAdd(Data_Enrolled, -1, 'H')=%%

This function subtracts one hour from the 'Data_Enrolled' date and time.

To handle unexpected errors gracefully in a custom subscription center, wrapping the code in a Server-Side JavaScript (SSJS) Try/Catch block is recommended.

Try/Catch Block: Using a Try/Catch block in SSJS allows the developer to catch and handle exceptions, providing a mechanism to manage errors without disrupting the user experience.

SSJS Example:

<script runat="server"> Platform.Load("Core", "1"); try { // Code that may throw an error } catch (e) { // Handle the error Write(Stringify(e)); } </script>

Salesforce Server-Side JavaScript (SSJS) Guide

To update Contact data stored in a Data Extension using the REST API, the Data Extension must be in an Attribute Group (A). This is necessary because the REST API interacts with Contact data through Attribute Groups, which organize Data Extensions and their relationships within Contact Builder.

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.

A Contact can be reintroduced into the system only after the deletion is fully complete. The Contact Delete process in Salesforce Marketing Cloud is designed to ensure that all references and data associated with the contact are thoroughly removed. Reintroducing the contact before the process is fully complete would disrupt this cleanup process and potentially lead to data integrity issues.

The Describe method in the SOAP API provides metadata about the objects available in the system, including Profile and Preference Attributes. This method can be used to dynamically retrieve and display these attributes in a custom profile center.

Describe Method: This method returns the schema of the objects, including fields and their properties, which can be used to dynamically generate forms and interfaces.

Salesforce SOAP API Describe Method

To create a JavaScript Web Token (JWT) using a key from Key Management in Salesforce Marketing Cloud, the GetJWTByKeyName function should be used. This function generates a JWT using the specified key from Key Management.

Salesforce JWT Documentation

To expedite the process of deleting roughly 10 million subscribers using Contact Delete, the developer should change the Suppression value to a larger value (A). Increasing the suppression period helps in reducing the time taken for the deletion process as it allows the system to handle more deletions at once, thus speeding up the overall process.

Transparent Data Encryption (TDE) is designed to protect data at rest by encrypting the underlying storage of the database. This method ensures that data is encrypted on disk to prevent physical data theft while allowing it to remain accessible to authorized users within the system.

Salesforce Transparent Data Encryption

To successfully create a TriggerSend object using AMPscript's API functions, the following objects are required:

TriggerSendDefinition (B) - Defines the parameters of the triggered send, including the email to be sent and the associated attributes.

Subscribers (D) - Represents the individual recipients who will receive the email.

These objects ensure that the correct email is sent to the specified subscribers when the TriggerSend is executed.

Before using the 'contacts/' route of the REST API to update records in a data extension, the developer should verify that the data extension should be linked in an AttributeGroup in Contact Builder (D). This ensures that the data extension is part of the contact model and can be accessed and updated using the REST API.

To retrieve a row of data from a data extension using the SOAP API, the developer should use the DataExtensionObject API Object. This object allows for operations such as retrieving, updating, and inserting rows within a data extension.

Automation Studio provides tools for extracting tracking data from the Marketing Cloud. This can be done using the Data Extract Activity, which allows you to extract various types of tracking data such as email send, open, and click information.

Salesforce Automation Studio Data Extract Activity

To collect a representative sample from a larger data set, the developer should use the NTILE (C) SQL function. The NTILE function is used to distribute rows into a specified number of approximately equal-sized buckets or tiles, which can be useful for sampling purposes.

Example usage:

SELECT * FROM ( SELECT *, NTILE(10) OVER (ORDER BY SomeField) AS TileNumber FROM LargeDataSet ) AS Sample WHERE TileNumber = 1

This query divides the dataset into 10 tiles and selects rows from the first tile, effectively providing a sample.

To reference subscriber, system, and sendable Data Extension attributes for content personalization using SSJS, the correct syntax is . This tag allows you to dynamically insert the value of an attribute into the email content.

Tag: This tag is used to insert the value of an attribute from a Data Extension or subscriber attribute into the content. The name attribute of the tag specifies which attribute's value should be used.

%%[ var @firstName set @firstName = AttributeValue("FirstName") ]%% Hello, !

Salesforce SSJS Guide

This syntax ensures that the correct personalization attributes are pulled into the email, enabling dynamic and personalized content based on subscriber data.

A Query Activity in an Automation can fail for several reasons, including:

The query takes more than 60 minutes to run (A) - Long-running queries are subject to timeouts, which can cause the query to fail.

The query results in duplicate rows not allowed by the primary key (C) - If the query attempts to insert duplicate rows into a data extension that has a primary key constraint, it will fail.

The query is inserting a value that is larger than the size of a field (E) - If the query attempts to insert data that exceeds the field size limits, it will result in an error.

When batch deleting large volumes of contacts, it is important to consider the following factors:

Batch Deletion Limits: Up to one million records can be deleted in each batch. This helps manage and control the deletion process without overwhelming the system.

Suppression Status Visibility: The suppression status does not show for individual contacts until the entire batch processes. This means that you will not see the status updates for individual contacts until the deletion batch is fully processed.

Salesforce Contact Deletion Process

To append the subscriber's zip code to a link and ensure that the clicks are tracked, you should use the Lookup function to retrieve the zip code from the data extension and the RedirectTo function to create the link with tracking enabled.

Lookup: Retrieves the zip code from the data extension.

RedirectTo: Ensures that the link with the appended zip code is tracked.

Example:

ampscript

Copy code

%%[ SET @zipcode = Lookup("DataExtensionName", "zipcode", "SubscriberKey", _subscriberkey) SET @link = Concat(" ", @zipcode) ]%%

Salesforce AMPscript Lookup Function

Salesforce AMPscript RedirectTo Function

To populate a data extension with the date of the most recent click for each subscriber, the developer should use the following SQL query:

SELECT c.SubscriberKey, MAX(c.eventDate) AS eventDate FROM _Click c GROUP BY c.SubscriberKey

This query selects the SubscriberKey and the maximum eventDate for each subscriber from the _Click Data View, ensuring that the most recent click date is retrieved.

In Marketing Cloud, the Contact Key should be represented as a Text data type, even if it is a numeric value. This is because using the Text data type avoids issues related to numeric value formatting and allows for greater flexibility in handling the values.

Salesforce Contact Builder Best Practices

To trigger an SMS message to a subscriber using a form published on CloudPages, the developer should use the requestToken and messageContact REST API objects (D). These objects can be used to authenticate and send the SMS message programmatically when the form is submitted.

To retrieve which subscribers were sent a particular email using the Marketing Cloud SOAP API, the developer should use the SentEvent (C) SOAP API object. This object records the event when an email is successfully sent to a subscriber.

To dynamically populate the physical address of a company's locations using the variable @address and ensure the fastest possible performance for millions of subscribers, the recommended AMPscript solution is:

%%[ SET @address = Lookup("Building_Locations", "Address", "Id", @Id) ]%%

This solution uses the Lookup function, which retrieves a specific field value from a data extension based on the given criteria. It is efficient and performs well for high-volume sends.

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.

The LookupRows function retrieves rows from a data extension where specified criteria are met. In an Enterprise 2.0 account, the data extension name in shared data extensions should be prefixed with 'Ent.' to indicate it is in the shared space.

Example:

SET @rows = LookupRows('Ent. Inventory', 'InStock', 'true')

Salesforce AMPscript LookupRows Function

The outdated subject line variable could be located in the HTML body which is processed after the subject line (D). This is because AMPscript variables declared in the HTML body can affect the overall email content, including the subject line, and if not updated, they can cause discrepancies in the displayed subject line.

To track the performance of dynamically created content via AMPscript in an email, the following steps should be performed:

Request the Impression Tracking feature be enabled on the account: This feature must be enabled to track impressions of dynamic content.

Include the functions BeginImpressionRegion and EndImpressionRegion: These functions are used within the AMPscript code to mark the beginning and end of the content region that needs to be tracked.

Example:

ampscript

Copy code

%%[BeginImpressionRegion('DynamicContent')]%%

%%=v(@DynamicContent)=%%

Salesforce AMPscript Functions for Tracking

To add records to a Data Extension using the SOAP API, the DataExtensionObject object is utilized. This object represents a row within a data extension.

DataExtensionObject: This object is specifically designed to interact with data extensions, allowing you to insert, update, and retrieve rows. Here is a basic example of how to use this object to add a record:

DataExtensionExternalKey SubscriberKey example@example.com FirstName John LastName Doe

Salesforce SOAP API Developer Guide

A File Drop Automation should be configured to handle files that arrive at varying times and have unique filenames. This type of automation triggers when a file is dropped into a specific folder on the Enhanced FTP site, allowing the system to handle imports as soon as the file arrives.

Salesforce File Drop Automations

Regarding Populations in Contact Builder:

Populations need to be added to an Attribute Group (B) - This is necessary to define the relationship between the population and the associated data extensions and attributes.

No more than three Populations should be created (C) - Creating more than three populations can lead to performance issues and complexity in managing contacts.

To avoid data loss and ensure reliable data transfer to Marketing Cloud data extensions, follow these best practices:

Handle 'Not Authorized' Errors: If a 'Not Authorized' error occurs, it is likely due to an expired or invalid access token. Request a new access token and retry the API call.

Retry on Server Errors: If a server error occurs, it might be a temporary issue. Ensure the server is available and retry the call.

Token Expiry Management: Store the expiry time of the access token and request a new one before the old token expires to prevent authorization issues.

Salesforce Marketing Cloud API Best Practices

To remove line breaks within the Comments field and replace them with a single space, you can use the REPLACE function in combination with the CHAR function. The CHAR(13) and CHAR(10) functions represent carriage return and line feed characters, respectively.

REPLACE Function: This function is used to replace occurrences of a specified string with another string.

CHAR Function: This function returns the character based on the ASCII code provided.

Example:

SELECT REPLACE(REPLACE(Comments, CHAR(13), ' '), CHAR(10), ' ') AS Comments FROM YourDataExtension

Salesforce SQL Reference

To create a lead capture form on a landing page and create a Lead record in Salesforce, you can use either AMPscript or SSJS. AMPscript can be used for interacting with Salesforce, and SSJS can handle form processing. Alternatively, SSJS can handle the entire process, including creating the Salesforce record.

AMPscript and SSJS Combination: You can use AMPscript to interact with Salesforce APIs to create records and SSJS for form handling.

SSJS for Full Functionality: SSJS can handle both the form submission and the interaction with Salesforce to create Lead records.

Salesforce AMPscript and SSJS Integration

The "View Email As Web Page" (VAWP) link relies on the original email content being available. If the email used at the time of send was deleted, updated, or moved, the link will not be able to retrieve and display the content, resulting in the error message.

Salesforce VAWP Documentation

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(" "); var jsonData = Platform.Function.ParseJSON(response); Platform.Function.UpsertData("DataExtensionName", ["PrimaryKeyField"], jsonData);