Summary 📝
When the Contact Delete process in Marketing Cloud Engagement is completed, it executes a system-wide permanent removal of the contact's data. This removal targets all data associated with the Contact Key across the core contact model. Specifically, the process deletes the contact's records from all associated Sendable Data Extensions (as these are linked to the contact model via Attribute Groups) and all Mobile Lists (which are part of the core MobileConnect/MobilePush channel data). This comprehensive deletion ensures the contact is no longer billable and adheres to the "right to be forgotten."

Data Removal Locations ✅

C. Sendable Data Extensions
Any Data Extension that is related to the central All Contacts table via a relationship in Contact Builder (i.e., any Sendable Data Extension used in a Journey, Triggered Send, or standard Send) will have the contact's record removed. This ensures data privacy and reduces the billable contact count.

D. Mobile Lists
The Contact Delete process includes the deletion of all associated mobile records. This means the contact is removed from the MobileConnect All Contacts list, Mobile Lists, and any related MobilePush records, ensuring the contact cannot be messaged via SMS or Push Notifications.

Data Not Removed/Incorrect Options ❌

A. Non-Sendable Data Extensions
Non-sendable Data Extensions are typically used as staging, reference, or lookup tables and do not need to be related to the core Contact Key in Contact Builder. Therefore, the Contact Delete process usually does not automatically delete records from these independent tables.

B. Import Files on the Enhanced SFTP
The Enhanced SFTP stores files external to the Marketing Cloud database (i.e., flat files like CSVs). The Contact Delete process runs within the database and does not interact with or delete files stored on the SFTP server. Files on the SFTP must be managed and deleted manually or via a separate File Transfer Activity.

Reference 🔗
Salesforce Help Documentation - Contact Delete
(Details the scope of the Contact Delete utility, confirming the removal of data across all channels, including sendable data extensions and mobile data.

Summary:
To retrieve individual send, open, click, and bounce tracking data tied to a specific JobID in Marketing Cloud, the data must come from the underlying tracking sent data views (_Sent, _Open, _Click, _Bounce). The only two Automation Studio activities that can extract or query this granular tracking data at the JobID level are the Tracking Extract and the SQL Query Activity (targeting a data extension).

Correct Option:

A. Tracking Extract Activity
The Tracking Extract can export Job-level tracking details (Sends, Opens, Clicks, Bounces, Unsubscribes, etc.) for one or more specific JobIDs. When configured with “Job” scope and the desired JobID(s), it generates a _Job.csv file plus the corresponding _Sent.csv, _Open.csv, _Click.csv, and _Bounce.csv files containing subscriber-level records.

D. SQL Query Activity
SQL Query Activities can directly query the tracking data views (_Sent, _Open, _Click, _Bounce) using a WHERE JobID = XXXXX condition. This is the most common and flexible method developers use to pull send, open, click, and bounce data for a specific JobID into a data extension for reporting or further processing.

Incorrect Option:

B. Server-Side JavaScript Activity
Server-Side JavaScript cannot directly access the tracking data views or perform a tracking extract. It can only call limited WSProxy or Core functions and is not designed for bulk tracking exports.

C. Campaign Data Extract
Campaign Data Extract is part of the legacy Automation Studio “Data Extract” activity and is limited to campaign-level summaries. It does not provide individual tracking events tied to a specific JobID.

Reference:
Salesforce Official Documentation: Data Encryption at Rest

Summary 🔒
Salesforce Marketing Cloud Engagement supports PGP (Pretty Good Privacy) and GPG (GNU Privacy Guard) as the standard encryption methods for securing file payloads transferred to and from the SFTP server. This is referred to as data encryption or data-at-rest encryption, which secures the sensitive information inside the file. The platform uses these asymmetric encryption methods in File Transfer Activities within Automation Studio to decrypt files incoming for import or encrypt files being exported, ensuring the data is protected beyond the transport layer security provided by SFTP.

Correct Options ✅

A. PGP (Pretty Good Privacy)
PGP is a widely accepted standard for securing data using asymmetric encryption.

Marketing Cloud utilizes the PGP public key provided by the data sender (or uploaded by the user to the Key Management section) to decrypt files that are uploaded to the SFTP for import. The corresponding private key is stored securely within the system to perform the decryption.

B. GPG (GNU Privacy Guard)
GPG is the free, open-source implementation of the PGP standard (OpenPGP).

Marketing Cloud treats GPG files virtually identically to PGP files. Users can upload GPG keys to the Key Management section to enable the decryption of incoming GPG-encrypted files as part of a File Transfer Activity prior to an import step in Automation Studio.

Incorrect Options ❌

C. AES (Advanced Encryption Standard)
AES is a symmetric encryption standard (using a single key for both encryption and decryption). While AES is used within Marketing Cloud for internal features like Field-Level Encryption and EncryptSymmetric AMPScript functions, it is not the supported encryption method for securing the entire file payload during the SFTP import/export process (where PGP/GPG is used).

D. SSH (Secure Shell)
SSH is a protocol used to establish a secure connection over an unsecured network. SFTP (SSH File Transfer Protocol) relies on SSH for this secure transport layer, but it is not an encryption method for the data within the file itself (the payload). While SFTP encrypts the transfer, PGP/GPG is still needed to encrypt the file contents separately.

Reference 🔗
Salesforce Help Documentation - Use a Created Key with File Transfer Activities

Summary 📝
A comment in any programming or scripting language is non-executable text used for documentation or temporarily disabling code. Within an AMPScript code block (defined by %%[ ... ]%%), the valid syntax for a single-line or multi-line comment is borrowed from the C-style language standard. This uses a forward slash followed by an asterisk to open the comment, and an asterisk followed by a forward slash to close it: /* comment */.

Correct Option ✅

D. / comment /
This is the correct C-style syntax for comments within an AMPScript code block (the portion between %%[ and ]%%).

This syntax can be used for single-line comments (e.g., /* Set the variable */) or for multi-line comments that span several lines of code within the block.

This comment syntax is completely ignored by the AMPScript processor during execution, serving only as documentation for the developer.

Incorrect Options ❌

A. --comment
This syntax (--) is the standard comment marker used in SQL (Structured Query Language) and is used in Marketing Cloud within Query Activities in Automation Studio, but it is not recognized as a valid comment marker within an AMPScript code block.

B. // comment
This syntax (//) is a common single-line comment marker in languages like JavaScript and C#, but it is not the valid or supported single-line comment syntax recognized by the AMPScript processor within a code block. Using this will result in an AMPScript error.

C. - comment -->
This syntax (- comment -->) is the closing syntax for HTML/XML comments (``) or a variation of it. It is entirely incorrect for use within an AMPScript code block and will cause a parsing error.

Reference 🔗
Salesforce Developers Documentation - AMPScript Syntax and Comments

Summary:
The Marketing Cloud SOAP API is built on the legacy SOAP protocol, which uses XML for both request and response payloads. It is primarily synchronous by nature, though some objects support an optional Asynchronous request header. The API enforces rate limits far below 2000 calls per minute (typically around 120–300 depending on the account tier).

Correct Option:

C. Uses XML in request and response body.
The SOAP API exclusively uses XML format for both the request envelope and the response. This is a fundamental characteristic of all SOAP-based web services in Marketing Cloud.

B. Most SOAP calls can be synchronous or asynchronous
Many SOAP API objects support both modes via the optional header inside the SOAP envelope. When omitted, calls are synchronous; when included, they are processed asynchronously and return a request ID immediately.

Incorrect Option:

A. More than 2000 SOAP calls can be performed per minute.
False. The standard SOAP API limit is much lower (typically 120–300 calls per hour for most accounts, or up to ~5 per second in high-tier accounts). 2000 calls per minute would far exceed documented limits.

D. Uses JSON in request and response body.
False. JSON is used by the Marketing Cloud REST API, not the SOAP API. The SOAP API always uses XML.

Reference:
Salesforce Help – SOAP API Technical Details