Certified Marketing Cloud Developer

UNION ALL combines results of two queries without removing duplicates, unlike UNION DISTINCT. JOIN merges based on relationships, not for stacking rows.

Mobile Connect uses the REST API to send and manage SMS messages in Marketing Cloud. The Classic Content tool is outdated, and Automation Studio does not rely primarily on REST, but instead on SOAP API and system activities.

Data Extract Activities are created and executed within Automation Studio, which allows extracting tracking data and delivering it to an FTP location. REST API and Journey Builder are not used for this type of extraction.

In SSJS, Variable.GetValue(“@variableName”) is used to retrieve the value of an AMPScript variable. Any other options are either syntax-incorrect or intended for assignment, not retrieval.

The correct data view for querying business unit-level unsubscriptions is _BusinessUnitUnsubscribes. The other views (_Subscribers, ENT._Subscribers) show overall status, not BU-specific status.

Marketing Cloud supports PGP or GPG-encrypted files during the import process. RSA and AES are not directly supported for this type of integration.

The Contact Builder data model is primarily used in Email Studio and Journey Builder to segment audiences. Automation Studio doesn’t segment audiences, and Mobile Studio uses specific lists or DEs.

The correct way to delete billable contacts in Marketing Cloud is to move them to a billable DE and run Contact Delete. Neither REST nor SOAP deletes from All Contacts directly.

SentEvent objects are read-only. They cannot be created or modified using the SOAP API, only queried.

The correct way to upload and get the URL of an asset is by using POST /asset/v1/content/assets and then reading the FileProperties property.

The correct option is B, because it performs a JOIN between _Job and _Sent and filters by EmailName LIKE ‘TEST%’. The others have syntax errors or incorrect conditions.

Marketing Cloud tiene un endpoint REST específico /address/v1/validateEmail para comprobar si una dirección de email es válida.

Contact Builder works best with normalized data, properly related (primary/foreign keys), and aligned with marketing objectives. Not all DEs need to have an email address or be sendable.

Credentials should be stored securely, using environment variables or a KMS. They should never be included in code or passed in URL parameters.

The ADD function in AMPscript only takes two parameters, so you have to nest it to add more than two values.

To dynamically concatenate the zip code to the link, Concat is used, and to ensure click tracking, RedirectTo.

OAuth 2.0 standards require sending the token in the header as Authorization: Bearer <token>.

To access a Shared DE from any BU, you must prefix it with Ent.. The correct condition is InStock = true.

Transparent Data Encryption (TDE) ensures that the database is encrypted at rest. Field-Level or Tokenized encryption protects data during use, not at the physical storage level.

When querying a Shared DE from a BU, the prefix ENT. must be used before the name.

The _Job data view contains the information for each shipment (JobID, date, etc.) required for this inventory.

The most efficient option is SELECT *, because it ensures that the new fields are included without having to modify the query each time.

When deleting large volumes of contacts, Salesforce Marketing Cloud enforces a limit of 1 million contacts per batch. Also, suppression status is only updated after the entire batch is processed, meaning you won’t see results contact by contact. This ensures system stability when processing millions of rows.

AttributeValue retrieves a value from profile or send context, Lookup retrieves a single field from a DE, and LookupRows returns rowsets from DEs. RowCount and Field are helper functions but not direct ways to reference data in this context.

When working with Journey Builder, the correct way to access entry source DE fields in emails is via Personalization Strings (e.g., %%FirstName%%). AMPscript can be used, but the standard method for journey entry data is personalization strings.

SAP involves authenticating the sending domain and setting up DKIM/SPF. Private domains and DKIM are required parts of SAP. Triggered Sends and Contact Delete are unrelated.

An INNER JOIN keyword is used to return only the rows from both tables where the join condition is true. In this case, the join condition is the matching ‘ContactKey’ column on both data extensions. The developer would use an INNER JOIN between the Customers data extension and the Orders data extension on the ‘ContactKey’ column to retrieve all subscribers who made a purchase in the last 30 days.

To further narrow down the result set to only include those subscribers who made a purchase in the last 30 days, the developer would use a WHERE clause to filter by the ‘PurchaseDate’ column on the Orders data extension.

The Decimal data type is used for storing decimal numbers with a specific number of digits to the left and right of the decimal point. The (9,2) in the Decimal(9,2) represents the precision and scale of the data type. The precision is the total number of digits that can be stored, including the digits to the left and right of the decimal point. The scale is the number of digits to the right of the decimal point.

In this case, the Purchase_Price values vary from ‘$.05’ to ‘$100’. To avoid data loss and ensure accuracy, the Decimal data type should be used with a precision of 9, which allows up to 9 digits to be stored, and a scale of 2, which allows for 2 digits to the right of the decimal point.

Using the Number data type could result in data loss as it only stores whole numbers, while using the Text data type could cause errors in calculations and sorting.

The Contact Key is a unique identifier that is used to link a subscriber’s information across multiple data sources in Marketing Cloud. It is typically represented as a text string, and its value should be unique for each subscriber.

Using the Text data type will allow for the storage of alphanumeric values, including numbers and letters, and the length of the text field can be set to 10 characters to accommodate the unique 10-digit integer Contact Key.

Using the Number or Decimal data types would not be appropriate for representing the Contact Key, as they are typically used for numeric values with decimal places, which is not the case for the Contact Key.

Sendable Data Extension is used to store data that is used for sending emails, SMS messages, or push notifications. It is used as a target for the email sends and is populated by importing data or automatically from other sources.

Salesforce Data Extension is used to synchronize data between Marketing Cloud and Salesforce, and is used to send targeted communications based on Salesforce data. It is used to store data from Salesforce objects such as leads, contacts, accounts, and opportunities.

Exclusion scripts are used to exclude subscribers from receiving an email based on certain criteria defined in the script. The exclusion script is a block of code that needs to be evaluated as true or false. If the script evaluates as true, the subscriber will be excluded from receiving the email. Subscriber attributes can be used in exclusion scripts.

Rowcount(LookupRows(‘Exclude’,’SubscriberKey’,_subscriberkey) > 0) This script checks the ‘Exclude’ data extension for a record with a subscriber key that matches the current subscriber being sent to. If a record is found, it will exclude the subscriber from receiving the email.

GetValue is used when you have an AMPScript variable that you want to pass to your SSJS.

To work, you need to set a value in an AMPScript variable before opening your script tags.

When writing a SELECT statement for a data extension, you must specify the fields you want to select by name. Using the wildcard (*) will not work as it is not a valid syntax in SQL to select all fields from a table.

Therefore, to select all fields in a data extension, you must list them individually, separated by commas, as shown in option B.

Option A is not entirely correct. Using the REST API to delete two million records at once may not be feasible as it can cause performance issues and timeout errors.

Option B, adding data retention policies to relevant data extensions, and option C, deleting unnecessary sendable data extensions, are valid ways to expedite the deletion process.

Option D, changing the suppression period to 0 days, will not accelerate the deletion process. The suppression period is the number of days a subscriber will remain suppressed from the “All Subscribers” list after being deleted. Changing it to 0 days will not affect the speed of the deletion process.

A-REST API should be used for sharing marketing content from CMS with Marketing Cloud Content Builder.

The ContentAreaByKey function in AMPscript can be used to retrieve dynamic content from a specific content area based on its unique key. This allows tracking the performance of each dynamic content block within an email.

When creating relationships for this data extension in Data Designer, it is required to include NTO. Since NTO uses a numeric identifier for the subscriber key, it is recommended to link the Contact ID to the subscriber key when creating the relationship. The Contact ID is the unique identifier that Marketing Cloud creates for each contact, which can be used as an external key to link data extensions. By linking the Contact ID with the subscriber key, NTO can ensure that all subscriber data is linked to the correct contact in Marketing Cloud.

To randomly select a percentage of records from a data extension that can be sent, you can use the SQL query language and the ORDER BY clause with the NEWID() function. The NEWID() function generates a unique value for each row in the data extent and ORDER BY sorts the results in a random order. The TOP 20 PERCENT clause limits the query results to the top 20% of the rows returned by the query.

Option A is not correct because the TOP function must be used with PERCENT, not with an absolute number.

Option C is not correct because there is no RANDOM function in SQL.

This is because in order for the contact deletion process to be effective, the contacts must be in a Sendable Data Extension. Otherwise, Marketing Cloud will not allow us to initiate it.

The error “MemberData is not a known data extension or system data view” indicates that the system couldn’t find the data extension named “MemberData” in the specified context. This could be due to several possible reasons:

The data extension doesn’t exist: Double-check that the data extension exists and is located in the correct folder.

The data extension is not in the correct context: If the automation is running in the context of a child BU, make sure that the data extension is in the correct child BU or in the shared folder.

The user of the automation doesn’t have access to the data extension: Verify the permissions of the user running the automation to ensure they have access to the data extension.

Regarding the options presented in the question, the correct answer is B – MemberData should have the prefix ENT. The prefix “ENT” should be added before the data extension name to specify that the data extension is part of the Enterprise level, rather than the Business Unit level.

The correct answer is A: Use the REST API to modify and add a retention policy.

To add a retention policy retrospectively to a Send Log Data Extension, you can use the REST API to update the Data Extension and add the retention policy. You can also use the SOAP API for this purpose.

Creating a new Send Log with a retention policy or editing the Send Log’s Data Extension in Contact Builder or Email Studio would not be effective in adding a retention policy retrospectively to an existing Send Log Data Extension.

The Tracking Extract activity can be used to extract tracking data, including sends, opens, clicks, bounces, and other tracking information for specific JobIDs.

The Campaign Data Extract activity can be used to extract data from Salesforce Marketing Cloud campaign objects, including email sends, opens, clicks, bounces, and other interaction metrics.

The Server-Side JavaScript activity can be used to perform custom server-side processing using JavaScript code, but it is not specifically designed for tracking data extraction.

The SQL Query activity can be used to extract data from data extensions or other data sources using SQL queries, but it may not be the most efficient option for tracking data extraction.

Server-to-Server (S2S) and Web Application (Server-Side) integrations use the OAuth 2.0 protocol for authentication and authorization.

The main difference between them is that S2S integrations are designed for machine-to-machine communication, while Web Application integrations are intended for browser-based server-side integrations.

S2S integrations use the Client Credentials grant type and are issued a Client ID and Client Secret. They do not require user interaction and can access all resources available to the connected application.

Web Application integrations use the Authorization Code grant type and are designed for use in web applications. They require user interaction to obtain an authorization code, which is then exchanged for an access token. Web Application integrations receive a Client ID and Client Secret, and access is granted based on the permissions of the user who authorized the application.

Public Application integrations are designed for use in client-side applications such as mobile apps or JavaScript applications. They also use the Authorization Code grant type but do not have a Client Secret. Instead, they use a JSON Web Token (JWT) to authenticate requests. Public Application integrations make API requests in the context of the integrating user.

To include a comment within an AMPscript code block, developers can use the syntax: /* This is a comment */

If a subscriber record is deleted from the All Subscribers list or from the synchronized data source, it will be flagged for deletion in the sendable data extension during the next synchronization. Records that have been flagged for deletion are excluded from sends indefinitely, even if they are re-imported later.

Similarly, if a subscriber record is added to a suppression list or filtered out by a filter activity, it will be flagged for suppression in the sendable data extension during the next synchronization. Records that are still in the suppression phase at the time of sending will be excluded from sends, without the need for any manual intervention.

Grammatically speaking, the only valid option would be D, which is why it is the correct answer.

Since it is the only option that could be executed coherently, we will choose option 1.

The correct answers are A-Expires after 60 minutes and D-Can be requested with username and password.

A- An OAuth token for a legacy package expires after 60 minutes.

D- An OAuth token for the legacy package can be requested with a username and password.

B and C are incorrect because:

B- The endpoint to request an OAuth token for legacy packages is not POST/v1/requestToken. This endpoint is used for newer versions of the API.

C- OAuth tokens for legacy packages do not expire after 20 minutes. They expire after 60 minutes, as mentioned earlier.

It is done by process of elimination, as we know that contacts are not deleted from non-sendable Data Extensions.

A- Using the SOAP DataExtensionObject: This API option allows the developer to create and update records in a data extension using the SOAP API. The SOAP DataExtensionObject is used to represent data extension records. The developer can use the Create and Update methods of the SOAP API to create or update records in the data extension. This API option can be used to send real-time updates of the company’s product catalog to a data extension.

C- Using the SOAP Data Extension object: This API option allows the developer to create and update data extensions and data extension fields using the SOAP API. The SOAP DataExtension object is used to represent data extensions. The developer can use the Create and Update methods of the SOAP API to create or update data extensions and data extension fields. This API option can be used to create a new data extension or update an existing data extension to drive real-time updates of the company’s product catalog.

Option B: Using the REST path /hub/v1/dataevents is not a valid API option for sending real-time updates of the company’s product catalog to a data extension.

Option D: Uploading a file to Enhanced SFTP for import is not a real-time option, as the import process may take several minutes to complete.

When we talk about performing joins between data views, we can only reference them using SQL.

A- _Subscribers: This data view contains information about all subscribers in the account, including their email addresses and any associated profile attributes. Since language information is stored in a profile attribute, this data view can be used to join language information with click data from the _Click data view.

C- _Click: This data view contains information about all clicks in the account, including the subscriber’s email address, the clicked URL, and the date/time of the click. By joining this data view with the _Subscribers data view on the email address, the language information from the profile attribute can be included in the query to aggregate clicks by language.

The _AllSubscribers data view is not necessary for this query as it contains redundant data with the _Subscribers data view and does not include the necessary profile attribute information to join with the _Click data view.

Code validation A: This tool verifies the syntax of AMPscript code for errors and provides suggestions for corrections. It is useful for identifying and resolving issues with AMPscript code before sending the email.

Send preview C: This tool allows you to preview the email with the AMPscript code rendered as it will appear to the recipient. This is helpful for verifying that the AMPscript code functions as expected and that the email appears correctly.

Therefore, the correct options are Code validation A and Send preview C.

B – SpellCheck is a tool that checks the spelling of the email message content, and D – Markup Validation is a tool that checks HTML markup for errors. They are not directly related to AMPscript code validation.

The Marketing Cloud server-side function that should be used to convert a JSON-formatted string payload to a JavaScript object is ParseJSON.

The ParseJSON function is used to convert a string containing JSON data into a JavaScript object that can be manipulated with server-side JavaScript platform functions. This is useful when receiving JSON payloads from external systems, as the data can be easily converted into a format that can be used within a CloudPage.

The Request-Response integration pattern with Enhanced External Services invoking a REST API is the most suitable option for verifying preferences of an externally hosted RESTful service in real-time when a user clicks on Verify Preferences as part of a Lightning flow in Salesforce. Here’s why:

Request-Response integration pattern: This pattern is ideal when you need a real-time response from an external system. In this pattern, Salesforce sends a request to the external system and waits for a response before proceeding to the next step.

Enhanced External Services: This is a native feature of Salesforce that simplifies the integration process by allowing you to declaratively define external services in Salesforce. With External Services, you can create an Apex class that represents the RESTful service, and Salesforce can generate Apex code that you can use to invoke the REST API in the form of request and response.

RESTful service with OpenAPI 2.0 JSON definitions: The RESTful service in this scenario has OpenAPI 2.0 JSON definitions, which External Services can use to generate Apex code for invoking the REST API.

Boolean and String data types: The preferences of the RESTful service are boolean and string values, which can be easily mapped to corresponding Salesforce data types in Apex code.

By using the Request-Response integration pattern with Enhanced External Services invoking a REST API, you can easily verify the preferences of the RESTful service in real-time when the user clicks on Verify Preferences as part of a Lightning flow in Salesforce.

SQL query activities in Marketing Cloud expire after 30 minutes.

According to the Marketing Cloud documentation, the default timeout value for SQL query activities is 30 minutes. If the query takes longer than 30 minutes to execute, it will automatically stop and be marked as failed. The Marketing Cloud user interface will display an error message indicating that the query timeout has been exceeded.

The timeout value can be customized for each SQL query activity in Marketing Cloud by modifying the “Timeout” parameter in the Query Activity Properties. However, it is recommended to keep the timeout value at the default of 30 minutes unless there is a specific reason to increase it.

We selected option two because within the Data Schema that we can create, it gives us the option to specify a Data Extension Name, apart from being the way in which Data Extensions are created through API calls

The OAuth token requested by NTO using the REST API should be included in subsequent API calls using the appropriate authorization header.

Before using the retrieved set of rows within a FOR loop, it is important to verify if the set of rows contains data. This can be done using the RowCount function to check the number of rows in the set of rows. If the set of rows does not contain any data, the FOR loop should not be executed.

AttributeValue() is a function used to retrieve a value from a sendable data extension. In this case, it will return the value of the IsCompetitor attribute, which can be used in the exclusion script.
%%IsCompetitor%% is a personalization string used to retrieve the value of the IsCompetitor attribute from the sendable data extension.
[IsCompetitor] is a shorthand notation for AttributeValue(“IsCompetitor”).
R: @isCompetitor is not a valid script for this scenario as it does not utilize the AttributeValue() function or personalization string syntax.

When importing data files into Marketing Cloud, the following two encryption options are supported:

PGP Encryption: Pretty Good Privacy (PGP) is a data encryption and decryption technique that provides cryptographic privacy and authentication for data communication. PGP encryption is widely used to secure emails, text messages, and data files. Marketing Cloud supports PGP encryption for data file imports.

GPG Encryption: Gnu Privacy Guard (GPG) is an open-source version of PGP encryption. It uses the same encryption algorithms as PGP and is compatible with PGP encryption software. Marketing Cloud also supports GPG encryption for data file imports.

The best practices related to Marketing Cloud API integrations are:

Provide only the necessary API scope permissions.
Securely store the client ID, client secret, and access token.
Therefore, the correct options are C and D.

Storing the client ID and client secret in JavaScript (Option A) is not a recommended practice as it can facilitate attackers in extracting confidential information. Updating the access token with every API call (Option B) can generate unnecessary overhead and increase the risk of token expiration.

A web application is an application that runs on a web server and makes API requests on behalf of the Marketing Cloud user. The user grants permission to the application to access their Marketing Cloud data through the OAuth 2.0 authentication protocol. Once authorized, the web application can make API requests using the access token obtained during the authorization process.

On the other hand, a public application is an application designed to run without requiring user authorization. It is typically used in scenarios where a third-party application needs to access Marketing Cloud data without requiring user intervention. Public applications do not make API requests in the context of a Marketing Cloud user and therefore do not require a user to authenticate the application. Instead, they rely on a client ID and client secret to authenticate and access Marketing Cloud data.

Both web applications and public applications can be used to make API requests to Marketing Cloud, but the key difference lies in the context of the API requests. Web applications make API requests in the context of a Marketing Cloud user, while public applications do not.

One is the minimum number of certificates required to secure a full-branded CloudPage with SSL protocol.

To secure a CloudPage using SSL protocol, the developer must have an SSL certificate installed on the domain where the CloudPage will be hosted. This SSL certificate will ensure that all communication between the website and the user’s browser is encrypted and secure. Only one SSL certificate is required to protect a CloudPage and its elements, including images hosted in Content Builder.

Therefore, the correct answer is C – One.

To send an email using the Transactional Messaging API, the developer needs to first obtain a token. This token is used to authenticate and authorize API requests to Marketing Cloud. The v2/authorize endpoint is used to obtain a token through OAuth 2.0 authentication.
Once the token is obtained, the developer can use it to send email messages using the Messaging API. The POST to /messaging/v1/email/messages/ with the customer ID is used to send the email message.

Client Id and Client Secret are sensitive credentials that should be protected against unauthorized access. Storing them as variables in the application or transmitting them as query parameters over HTTPS can expose them to potential security risks, such as unauthorized access or interception by malicious actors.

A more secure approach is to store these credentials in a Key Management System (KMS) or a secure storage solution, such as a password vault. A KMS can securely manage and store cryptographic keys and other sensitive data, ensuring they are protected by strong encryption and access controls.

By storing the Client Id and Client Secret in a KMS, the application can securely access them when needed without exposing them to unauthorized access or interception. The developer should ensure that appropriate access controls and security policies are in place to protect these credentials and minimize the risk of unauthorized access or data breaches

This occurs when the subscriber’s sending data extension information has been deleted. When attempting to render the email again and not finding the data, it collapses or fails to render.

When updating records in a data extension using the ‘contacts/’ path of the REST API, it is important to ensure that the contact key matches the subscriber key in the underlying data extensions. This is because the contact key is used to identify the record in the All Contacts list, while the subscriber key is used to identify the record in the All Subscribers list. By ensuring that the contact key and subscriber key are the same, the API call will be able to correctly link and update the records in the data extension.

In SSJS, the CtrlVar object is used to reference fields from data extensions. The CtrlVar object allows you to access attributes within subscriber, system, and send data extensions. The attribute name should be enclosed in quotation marks after the “”name=”” part of the code. For example, if you want to reference the attribute “”Name,”” you would use the following code:

<ctrl:var name=””Name”” />

This will insert the value of the “”Name”” attribute for the current subscriber in the email.

The RedirectTo AMPscript function is used to track links in an email send. When a link is wrapped in this function, it ensures that the href values of the link containing HTML markers or anchors are recorded in the tracking data. This allows the email marketer to track which links were clicked in the email and how many times they were clicked.

Option A – Create an Exclusion Script with the Rainbow Run domain for use in the Email Send activity and Option B – Create a Suppression List with all possible email addresses from Rainbow Run are the two recommended best practices to use when setting up the Email Send activity in the welcome journey to ensure no emails are sent from the journey to the competitor at Rainbow Run.

Creating an exclusion script to check the recipient’s email domain before sending the email is one approach. If the domain is Rainbow Run, the email will not be sent. This will prevent emails from being sent to Rainbow Run.

Creating a suppression list that includes all possible email addresses from Rainbow Run ensures that any email address associated with Rainbow Run is excluded from receiving the email.

Creating a filter activity in the journey to remove the Rainbow Run domain and creating a data extension with the Rainbow Run domain to use with a Domain Exclusion are not the best practices for this situation because they do not provide a comprehensive solution to prevent emails from being sent to Rainbow Run.

We selected option C because TR is what is used to assign a new row to a table.

The Subscriber Key is a unique identifier for a subscriber in Marketing Cloud. It is used to link subscriber data across different channels and systems in Marketing Cloud, such as Email Studio, MobileConnect, and Journey Builder.

The Contact Key is a unique identifier for a contact in Marketing Cloud, which can be used to link contact data across different channels and systems in Marketing Cloud.

Please note that the Contact ID and Subscriber ID are not used to identify subscribers across different channels and systems in Marketing Cloud. The Contact ID is a unique identifier for a contact in the Marketing Cloud contact model, which is not directly linked to subscribers in Email Studio or other channels. The Subscriber ID is a system-generated ID for a subscriber in Email Studio, but it is not used as a cross-channel identifier in Contact Builder.

We selected options A and D since they are the only ones that perform a comparison correctly.

This SQL query will replace all line breaks in the “Description” field with spaces. It does so using the REPLACE function twice: once to replace occurrences of a carriage return (CHAR(13)) with an empty string (“”), and again to replace occurrences of a line feed (CHAR(10)) with a space (” “).

We selected options A and D because they are the ones that have direct access to Contact Builder.

The NTILE function is used to divide a result set into a specific number of groups or “tiles” based on a given order. This function is useful for creating samples of uniform size from a larger dataset.

It is a key part of the lifecycle of a record. It describes how long a company needs to retain a piece of information (record), where it is stored, and how to dispose of the record when the time comes. This helps prevent unnecessary records from accumulating within the send log.

The Shared Items root folder is a special folder that allows sharing items across business units. If a data extension is located in the Shared Items root folder, secondary business units can access it as long as it is marked as “shareable” and appropriate permissions have been set.

We selected options A, C, and D, based on the fact that in options A and C, we find the customers who receive sends. And in option D, we find the customers who are part of a journey.

Marketing developers, service providers, and external developers can create and manipulate marketing content using the Content Builder REST API.

The CloudPagesURL function returns the URL of the landing page along with an encrypted query string containing subscriber data.

Both are ways to display AMPscript in HTML. Option B is based on a variable that is derived from a calculation or definition in the code. Option D is used to retrieve the value from the Sending Data Extension.

We choose option A because we know that we cannot make requests of more than one million.

SSJS (Server-Side JavaScript) has advantages over AmpScript in terms of loops and arrays.

B- Loops: SSJS provides more advanced looping capabilities compared to AmpScript. With SSJS, developers can use different types of loops such as for loops, while loops, and do-while loops. This allows for more flexible and complex logic when iterating over data or performing repetitive tasks.

D- Arrays: SSJS supports arrays, which are ordered collections of values. Arrays are useful for storing and manipulating multiple values within a single variable. Developers can easily access, manipulate, and iterate over array elements using SSJS, providing more flexibility in handling data.

A- Advanced exception handling and C- Shorter learning curve for new developers are not advantages of SSJS over AmpScript. AmpScript also provides exception handling capabilities and can have a shorter learning curve for developers already familiar with HTML and basic scripting languages.

We choose option one because it has to be a Send relationship, so the last two options are ruled out. It is not mandatory for it to be a primary key, so we discard option two.

Post requests are the only ones that support passing OAuth tokens.

To import an encrypted CSV file from Marketing Cloud Enhanced FTP servers, you will need to use a File Transfer Activity to move the import file from the Enhanced FTP server to the Safehouse. Safehouse is a secure location within Marketing Cloud where files can be stored and accessed. By transferring the encrypted file from the FTP server to the Safehouse, you can ensure its security and then proceed with the necessary steps to decrypt and process the file within Marketing Cloud.

Searching for a specific age is more efficient. With this option, we also ensure that there are no leading or trailing spaces.

As the response states, the EmailAddress is not found in this Data View.

We selected options B and C because they go hand in hand. Custom fields can be added to a send log, but they must be named the same as the field they reference in the input Data Extension to ensure that the information is reflected correctly during the send. We ruled out option A with the image on sheet 2.

Since it mentions combining data from data views and inserting it into a final Data Extension, we would use the SQL Query activity as it allows us to perform table joins.

Option A (Row) retrieves a specific row from a search. Option C (lookup) retrieves a single record, so for searching multiple orders, options B and D are more optimal.

Check the snapshot

To ensure that clicks are tracked for the variable, the developer should include the variable in a RedirectTo function within the “a” tag. The RedirectTo function is used in AMPscript to track link clicks. By wrapping the variable in this function, the developer ensures that when the link is clicked, proper tracking is performed for reporting purposes.

We ruled out option 3 as it wouldn’t make sense since they already mentioned having the unique identifier. And we ruled out option 4 because we would already have them registered with that identifier. Therefore, we selected options 1 and 2.

You can extract it using the Tracking Extract activity, where you can select the files you want to extract. Alternatively, you can use a Query activity and filter by a specific Job.

We selected option 1 since when the token expires, it returns this error, and the solution is simply to request a new one. Option 2 could be considered, but it is less secure. Option 3 would be useful for automating a process that refreshes the token in case it becomes invalid.

By process of elimination, we selected option 3. Option 1 is ruled out because it would throw an error when trying to ParseJSON into a JSON response, so we converted it to a string.

In deliveryRecords, we find the RecipientSendId, which is the value returned by the /messageDefinitionSends service. It is the unique identifier for a single email send.

The try/catch block in SSJS has a separate scope. It means that any variable declared within the block will be accessible from the outside, neither in other parts of SSJS nor by personalization strings.

In order to enable text messaging programmatically, you will need to have MobileConnect enabled in Mobile Studio of Marketing Cloud. You will also need to be able to create an installed package in your Marketing Cloud account to interact with the Salesforce Marketing Cloud APIs. If you have both in place, we can start by generating a new SMS message.

Option 3 is chosen by process of elimination. It is the most correct option among the four.

As stated in the Salesforce documentation, if the email send uses a Salesforce data extension, make sure that the subscriber key is an 18-digit Contact or Lead ID.

Based on best practices, we choose option 1 to prepare the necessary data for the marketing department in order to avoid unnecessary data. Normalizing data to eliminate redundant values and ensuring primary keys in the relationships between tables in the model.

We select option 2 because with the ‘group by’ clause, we can order by subscriber key, displaying all the purchases made by a customer from top to bottom.

Considering how the statement is presented, we ruled out the last option because it lacks a File Transfer to extract the file to SFTP. And we ruled out option 1 because you would need to be able to insert the data into a Data Extension in order to export it to SFTP.

We select option 1 because it converts a given JavaScript object into a JSON string value. This function only works with known JSON objects and types, such as strings and integer values.

We use the extract method to retrieve all the information dynamically and display it.

Of all the options, Begginimpressionregion is the only one that allows us to access some specific type of tracking.

After the suppression process, the contacts are removed from all Sendable Data Extensions and lists.

As we can see in the Salesforce documentation, it corresponds to REST calls.

We selected option two because within the Data Schema that we can create, it gives us the option to specify a Data Extension Name, apart from being the way in which Data Extensions are created through API calls.

As we can find it in the Salesforce documentation, we choose options 1 and 2.

Access tokens expire one hour after issuance. If you attempt to use an expired token, you will receive an HTTP 401 Unauthorized response.

GetValue is used when you have an AMPScript variable that you want to pass to your SSJS. To work, you must set a value in an AMPScript variable before opening your script tags.

We select options 1 and 2, as they are the two ways used to access data from the Sending Data Extension.

In order to perform more optimal data intersections and manage high record counts, you may want to use the initial long-term data extension as a temporary data extension and then move it to different locations, such as sales or remarketing data extensions. That’s why it is recommended to add Data Retention.

We ruled out option 2 by the process of elimination. The EmailAddress does not appear in the Bounce Data view.

Transparent Database Encryption (TDE) encrypts the entire database transparently using a SQL Server function. This function stores the entire database in an encrypted format at the file level, while at rest. This feature prevents anyone with physical access to the database or a backup copy of the database from mounting it on another SQL server instance and accessing the data. TDE has minimal performance implications and no loss of functionality. TDE uses AES-256 encryption to generate the key.

If the data extension is deleted or overwritten, it will affect the view as a web page when a subscriber tries to view the web links because the view as a web page works by gathering subscriber’s source data and performing searches to create the email as a web page view. If something breaks in the delivery between the subscriber and the email, it will display a broken view as a web page (VAWP).

Setting up a Data Extract to extract the data, and then use the file transfer to transfer the data with the assigned key.

Key Manager can be found in Settings > Administration > Data Management and allows you to store all key clients for various purposes. From configuring SSO, using the EncryptSymmetric / DecryptSymmetric methods of AMPscript, to encrypting files via PGP or GPG

We basically ruled this one out by process of elimination, as we know that library cannot be used in SMS or email

We basically deduce this option by process of elimination. We know that this library cannot be used for SMS or Email.

In the following question, we can discard options 2 and 3 as follows. Option 2 is discarded because, in Marketing Cloud, the decryption process is done in the safehouse, not in the import directory. Option 3 is discarded because the File Drop has to be in a specific directory path within the import directory.

When creating a Data Designer, it asks us to specify which primary key to use for decision making. Therefore, we need to link it based on the SubscriberKey of the input Data Extension.

Guided by the statement where it asks for the identifier of the send, we can deduce that it is the JobID, which is the unique identifier for each send.

As stated in its documentation, in this type of accounts, deletion processes are executed from the Business Unit where the contact was generated.

We select options 1 and 3 because they have the CASE function, which allows us to handle different variants of field values within a query.

We will select option 2 based on the fact that dividing a large query into multiple smaller queries will reduce processing times, avoiding timeouts. However, it will result in more activities being executed.

We chose option 3 as it is the only one that uses the ADD function correctly.

Given the requirements, with the exclusion script, we would have the competitor’s emails in the exclusion Data Extension, and at the same time, we would prevent them from receiving the specific email sends.

There are only 2 SSJS libraries, Core and Platform. Landing pages support both of them.

A contact is a person you reach out to through any channel. But a subscriber is a person who opted in on a specific channel. That’s why all subscribers are contacts.

Populations are ways of segmenting a population within large groups of contacts. It is suggested not to create more than 3 populations because if you need to create more, it might be worth reconsidering the use case and finding an alternative approach.

We select option 4 because it specifically selects the necessary fields. Option 3, for example, would bring us all the fields existing in the Data Extension, accessing information that we don’t need.

Since endpoints are unique to your account, only you have access to them, which makes them perform better.

AMPScript is rendered in the following order: HTML Body > Text Body > Subject Line. Therefore, option 2 is the correct one.

By process of elimination, we know that it is option 3 since it has the event tab.

The triggeredSendDefinition object is used to obtain the external key and contact in order to access the information of the subscriber to be contacted.

Guided by the statement of the question, it indicates that it is a text type, but then the comparison is made against a number, which causes it to fail. The correct operator would be the greater than operator.

Since it is the only option that could be executed coherently, we will choose option 1.

This type of error occurs when the token has expired and needs to be refreshed.

For a Data Extension to be eligible as an entry source for a journey, it must be sendable so that after the send, the contact can be created or updated based on the value in the send relationship.

We select the first option because with CHAR, we can assign a number or letter to a character, and then use the REPLACE function to remove line breaks.

We choose option 3 because it is the object to which the call is made in order to fetch the information.

We choose option 3 because it has the “invokeretrieve” function, which allows us to access the response JSON of the call. Then, we can convert the JSON to a string using the “stringify” function.

Since accessing Data Views requires SQL queries, we choose the option that involves querying and extracting data from a data extension, understanding that the obtained information will be stored in a data extension and will be exported later.

Based on the type of error returned, we choose option 1. It indicates that there are insufficient permissions to perform the send, but the authentication is properly done.

We chose option 2 because it is the only one that is grammatically correct. The difference between option 2 and option 3 is that option 3 treats the value ‘Customerkey’ as a literal text.

As stated in the documentation, Impression Tracking allows you to track the performance of emails that contain content created with AMPscript or dynamic content in Email Studio.

The most optimal way to identify the specific subscriber and send would be by using the subscriber key, which is the unique identifier of the subscriber, and the JobID, which is the unique identifier of the send.

Populations are used to categorize different subgroups of contacts. A population is like a subset of the main list of people who can enter a journey. Therefore, according to Salesforce documentation, if you need more than 3 of these to carry out the journey, you may consider creating different journeys.

Based on the fact that records cannot be created in Salesforce from SSJS, we need to choose the options that involve Ampscript in that function

We discard option 1 because the timeout for queries is 30 minutes, and we discard the second option because there is no error to return large amounts of data in an SQL query.

As stated in its documentation, all new Marketing Cloud technologies implement the REST API. REST calls are synchronous, with timeout values of 120 seconds for non-tracking operations and 300 seconds for tracking and data retrieval operations.

We select option two based on the statement referring to Contact data, which is within an Attribute Group.

We select option 4 because it is the only one that allows for unzipping a file.

We select option number 4 because, as stated in its documentation: Marketers use Journey Builder to create event-based responsive campaigns for distribution across any channel (online and offline), at any time, and with any frequency.

We select the “describe” option, which allows us to access the data of an object, and the “update” option to update them.

The answer to this question depends on the type of structure that SOAP calls have. They use XML in the request and response, and then the second correct answer would be that the major difference between SOAP and REST calls is that SOAP calls allow for asynchronous processing almost entirely.

In this question, we have two options for moving and decrypting the file. However, we choose option 3 because the decryption is performed in the safehouse, as its name implies, and then it is moved to Marketing Cloud for importing, as option 2 states.

We chose the overwrite option because it is the only one that has the ability to remove records from the destination of the Data Extension.

Both programming languages can be supported in email messages.

AMPscript can contain comments or non-executed notes that allow you, as the author, to document your code. You should open comments with the /* sequence and close comments with the */ sequence. Comments can span multiple lines.

In this question, we select option one because, as we understand from the prompt, the file will always start with the month and day. Then we select option 4 to always compare based on the start of the name.

We select option 2 because it is the only one that correctly applies the Add function. Option 3, for example, does not apply it correctly because it cannot sum more than 3 variables in the same function.

We select options 3 and 4 because they are the types of APIs that have the capabilities to send requests.

As stated in its documentation, the DataExtensionObject represents a row within a data extension.

We selected option 1 based on it being the correct flow for a contact deletion.

We choose this option based on best practices. We provide only the necessary permissions to prevent access to functionalities that we do not want to be accessed.

We choose option 3 because the rendering order is HTML Body > Text Body > Subject Line.

This is because in order for the contact deletion process to be effective, the contacts must be in a Sendable Data Extension. Otherwise, Marketing Cloud will not allow us to initiate it.

When the RaiseError function detects that there is missing information, it cancels the sending of the email. Therefore, we choose options 1 and 2.

This is basically a good practice for security reasons.

We choose option one because, in addition to being the only well-formed option, the DATEADD function allows you to add negative numbers to subtract time.

We choose options 1 and 3 based on the requirements of the question. We are asked to create a URL that the subscriber will click in the email, which will contain information from the sending Data Extension. The lookup function is used to retrieve the zipcode data, and the redirect function is used to direct us to the destination URL while passing the value of the zipcode in it.

In the following question, we can discard options 2 and 3 as follows. Option 2 is discarded because in Marketing Cloud, the decryption process is done in the safehouse, not in the import directory. And option 3 is discarded because the File Drop has to be in a specific directory path within the import directory.

In the following, we discard options 2 and 3 as they are less secure. Option 2, by passing them in the URL, could allow access to sensitive data such as the Client ID and Client Secret. Option 3, being in the application’s code, would be easily accessible.

As we can see in the prompt, to avoid having any sensitive information stored in our Salesforce system, I recommend using tokenized sending to transmit contact data that is too confidential to be stored in the Marketing Cloud account database. You can retrieve information from your own data systems and transmit it to Marketing Cloud only at the time of sending through an API call.

In this question, we will discard option 1 because a tracking extract alone does not transfer the file to the SFTP, and option 4 because in order to transfer a file to the SFTP that contains information from the Data Views, they must be saved in a Data Extension and extracted using a Data Extract, as mentioned in option 3.

Based on the prompt, we are asked which option to follow to display default content in case the client does not appear. We chose the first option because it is the only one that presents an IF statement.

We select option 3 because being primary keys, they are unique identifiers, making it easier to locate records. Then we select option 4 because using joins allows us to avoid using additional clauses in the WHERE statement when querying. Finally, we choose the last option because it allows us to avoid reinserting all the unchanged information since we already have it.

We select options 3 and 4 because the function allows you to choose the position where you want to place the decimal and whether you want to include the symbol of the local currency (in this case, the dollar) separately.

We discard option 1 because creating a regular Data Extension and naming it “Send Log” will not do anything. We discard option 2 because it is a functionality that accounts have, and Salesforce does not need to activate it. We discard option 3 because being a copy from another Business Unit, it has a different Org ID assigned to it, and the information will not be transferred.

When this error occurs, there are certain considerations to take into account:

– Check if you have added individual email results as a related list in the Lead/Contact object.

– If the email sent is from Marketing Cloud, verify if the subscriber key is Lead/Contact ID.

– In the Marketing Cloud Connect settings in Salesforce, enable the Tracking Frequency. Tracking data will be updated only according to the tracking frequency.

– If the email sent is from Marketing Cloud, make sure to check the box to send tracking data to Salesforce.

In this question, it is very important to read the prompt carefully. Data retention is a feature that can only be added when creating a Data Extension in Email Studio. However, in Contact Builder, it allows you to add it after creating the Data Extension. That’s why we choose option 3.

We select option 2 because it can be done using AMPscript from a Cloudpage, and we select option 3 because it is a function used in SOAP APIs that allows accessing Data Extensions and retrieving contacts.

We discard the first option because the route v1/interactions is used to retrieve a collection of all journeys. We discard v1/eventDefinitions because it only defines the event but doesn’t trigger it in the journey. And we discard v1/contactEvents because it is a route that doesn’t exist.