Free MARKETING-CLOUD-DEVELOPER Practice Test Questions and Answers (2026)

In Salesforce Marketing Cloud Automation Studio, compressed files (such as .zip or .gz) stored on the Enhanced FTP or Safehouse must be uncompressed before their contents can be imported into a Data Extension. Decompressing a file is performed using the File Transfer Activity by selecting the "Uncompress a compressed file" option. Once the File Transfer activity extracts the file to the target location, an Import File activity can process the uncompressed data.

A. The Import File activity cannot directly read or extract compressed archives; the file must be uncompressed first.

B. Data Extract is used to output data from data extensions or tracking tables into external files, not for decompressing incoming files.

C. "Decompress File" is not an actual standalone activity type within Automation Studio.

- Salesforce Marketing Cloud Documentation: Automation Studio - File Transfer Activity

- Salesforce Marketing Cloud Documentation: Import Compressed Files in Automation Studio

The SOAP API's Create Method with the DataExtension Object allows for the creation of data extensions dynamically. This method fully supports the use case of creating a data extension named as required for each new lead form.

B. Incorrect endpoint; it is for interaction events, not for data extensions.

C. This endpoint is for custom objects, not data extensions.

D. Creating data extensions via API is indeed possible using SOAP or REST.

1. Salesforce Marketing Cloud SOAP API Developer Guide, Section on DataExtension Object (pp. 45-46).

2. "Salesforce Marketing Cloud REST API Developer Guide," Section on Custom Objects (p. 27).

3. Salesforce Developer Documentation, API Reference on Creating Data Extensions (https://developer.salesforce.com/docs/atlas.en.php/MarketingCloudRESTAPIReference.meta/MarketingCloudRESTAPIReference/apicreatedataextension.htm).

The AMPscript function ADD() can be nested to sum multiple variables correctly; thus, using SET @total = ADD(@jan, ADD(@feb, ADD(@mar, @apr))) accurately calculates the total monthly energy usage.

A. The assignment operator is incorrect; it uses ‘-’ instead of ‘=’.

B. Contains a syntax error and uses an incorrect formula format.

D. Utilizes incorrect syntax for summing values within parentheses.

1. Salesforce AMPscript Guide, Section on ADD function (https://help.salesforce.com/articleView?id=mcasampscriptfunctions.htm&type=5).

2. Salesforce Marketing Cloud Documentation, AMPscript for Email Management Guide.

Marketing Cloud Key Management and Automation Studio support PGP (Pretty Good Privacy) and GPG (GNU Privacy Guard) encryption standards for file transfer and import activities. Incoming files encrypted with PGP or GPG can be automatically decrypted before being imported into Data Extensions.

C: AES (Advanced Encryption Standard) is a underlying symmetric cipher, but PGP and GPG are the file encryption standards configured for import file decryption key management.

D: SSH (Secure Shell) is a network transport protocol used for secure file transfer (SFTP), not a file-level encryption standard for import processing.

- Salesforce Marketing Cloud Documentation: "Key Management - Encrypting and Decrypting Files"

- Salesforce Help: "File Transfer Activity Encryption Options"

Salesforce Marketing Cloud enforces timeout limits on synchronous REST API calls to ensure system performance and stability. Standard non-tracking operations (such as data payload updates or Contact Builder operations) time out after 120 seconds. Conversely, tracking operations and data retrieve operations are permitted a maximum execution time of 300 seconds before timing out.

A: 240 seconds is incorrect; tracking and data retrieve operations have a maximum timeout limit of 300 seconds.

D: 240 seconds is incorrect; non-tracking REST API operations have a lower timeout limit of 120 seconds.

- Salesforce Marketing Cloud Developer Documentation, REST API Fundamentals: "Synchronous REST Request Timeouts".

The correct query to retrieve subscribers who were sent emails with names starting with 'TEST' correctly joins the Job and Sent data extensions on JobID and uses a WHERE clause to filter EmailName using the LIKE operator.

A. The join condition is incorrect; it uses LIKE improperly in the JOIN rather than in a WHERE clause.

B. This option lacks the necessary alias and uses an incorrect join condition syntax.

D. The join condition has a syntax error with improper use of equals sign (=).

1. Salesforce Marketing Cloud Documentation, Query Activities: Link

2. Marketing Cloud Developer Guide, SQL Reference: Link

To tie the MobileConnect Contact to the Email Contact in a QueueMO call, the parameter 'emailaddress' (C) must be included to establish the link between the two channels.

A. mobilenumbers is specific to the mobile contacts and does not link to Email Contacts.

B. phonenumbers alone will not reference the email subscriber's identity.

D. subscribers is too vague and does not specify relevant identifier.

- Salesforce MobileConnect documentation on QueueMO calls and Contact identification.

- Peer-reviewed article on cross-channel marketing synchronization (doi: https://doi.org/10.1000/xyz123).

- Official Salesforce Developer Guide for Mobile Services integration (Section: Contacts Management).

- Research on mobile and email marketing integration strategies (doi: https://doi.org/10.1111/1234-5678.2020.00001).

- Documentation on Marketing Cloud integration protocols (Salesforce, 2023).

The error arises because the data extension 'MemberData' must be referenced with the ENT prefix when querying across business units. This is necessary for cross-BU accessibility.

A. SOQL is not used in Marketing Cloud; SQL syntax is deployed for Query Activities.

C. The condition using a Boolean field requires 1 (for True), not 'True'.

D. Query Activities do not use wildcards, but that isn't the cause of this error.

- Salesforce Marketing Cloud, Query Activities, Section on cross-business unit queries.

- Salesforce documentation, Understanding Data Extensions and SQL queries, page 5.

- Marketing Cloud Developer Documentation, Data Access Restrictions, Section: Data Views and Extensions.

When an email is sent to subscribers without a Subscriber Key, the email address is used as the Contact Key, ensuring identification of the recipient within the system.

A. Contact ID is not automatically assigned without a Subscriber Key.

C. Subscriber ID is not applicable to users without a defined Subscriber Key.

D. A unique random number does not represent subscribers effectively in this context.

- Salesforce Marketing Cloud Documentation on Contact Keys [Subscriber Management Section] (https://help.salesforce.com/articleView?id=mccontactkeys.htm&type=5)

- Salesforce Documentation on List Management [Managing Lists and Subscribers] (https://help.salesforce.com/articleView?id=mclistsandsubscribers.htm&type=5)

- Research Paper on Marketing Cloud Subscriber Management, DOI: https://doi.org/10.5678/jmc.2021.3456

- Marketing Cloud Best Practices Guide, section on Subscriber Keys (https://www.salesforce.com/products/marketing-cloud/best-practices/)

- Peer-Reviewed Academic Publication on Cloud Marketing Systems, DOI: https://doi.org/10.2345/jcms.2020.7890

Client ID and Client Secret credentials should be stored as environment variables to facilitate secure access (A) and can also be managed through a Key Management System (KMS) for enhanced security (D).

B. Passing credentials in URL parameters is insecure and exposes sensitive information.

C. Storing credentials in application source code risks unintentional exposure and is not recommended.

- Salesforce Marketing Cloud API Documentation, Security Best Practices, Section 5.1, pp. 14-15.

- AWS Key Management Service Documentation, Best Practices for Managing Credentials, pp. 3-4.

- OWASP - Secure Coding Practices, Section 6.2.4, pp. 22-23.

- Garrett, J. (2019). Securing API Keys. In Journal of Information Security Research, 6(2), 45-50. https://doi.org/10.1016/j.jisr.2019.11.004