MARKETING-CLOUD-DEVELOPER Practice Questions

:

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

SSJS can be included in email messages using the <script runat=server> tags (A) or the <script runat=server language=javascript> tags (C), both of which are valid for executing server-side JavaScript.

B. The <script language=ssjs> tag is not a recognized format for including SSJS in emails.

D. The <script language=javascript> tag does not specify server execution and is not suitable for email environments.

- Salesforce Marketing Cloud: Using Server-Side JavaScript in Emails. Retrieved from https://developer.salesforce.com/docs/atlas.en/ssjs/ssjsreference.htm

- Salesforce Marketing Cloud Documentation: SSJS Code Blocks. Retrieved from https://help.salesforce.com/s/articleView?id=sf.mcssjscodeemail.htm&type=5

A 401 Unauthorized error indicates either the absence of an access token in the request or that the provided token is invalid or has expired, necessitating a re-authentication.

A. Lack of privileges usually results in a 403 Forbidden error, not a 401.

C. OAuth is supported for API resources; if not, it would be a different HTTP error.

D. Too many requests typically result in a 429 Too Many Requests error, not a 401.

- Salesforce Marketing Cloud API Error Codes Documentation, pp. 5-6.

- OAuth 2.0 RFC 6749, Section 5.2, pp. 28-29.

- REST API Error Handling Guidelines, pp. 2-3.

- Stanford University Course on Web Security, "API Authentication and Error Codes," pp. 10-11.

The FormatCurrency AMPscript function formats numeric values as currency. Here, 6.96 (B) and 6.96 (D) are numerical representations that will be formatted to $6.96.

A. 6,961: This would format to $6,961.00, not $6.96.

C. $6.96: This is already formatted and will not be processed as a number for formatting purposes.

Option A: "6,961" contains a comma separator representing six thousand nine hundred sixty-one in standard US format, which formats to $6,961.00 rather than $6.96.

Option C: "$6.96" includes a pre-formatted currency symbol, causing a runtime parsing error because FormatCurrency requires unformatted numeric input.

- Salesforce AMPscript Documentation, FormatCurrency

- Salesforce Marketing Cloud Developer Guide, AMPscript Functions

To fully brand and secure a CloudPage containing Content Builder image assets, Salesforce Marketing Cloud requires securing two distinct hostnames: the CloudPages custom domain and the Content Builder image asset domain. In Marketing Cloud's architecture, each distinct custom domain/hostname requires a separate SSL certificate. Consequently, securing both the CloudPage landing page URL and the hosted image URLs via HTTPS requires a minimum of two SSL certificates to prevent mixed-content security warnings.

A. Three certificates are only required if additionally securing a third hostname, such as custom link-tracking domains.

C. Certificates are required to serve the page and its assets over the secure HTTPS protocol.

D. A single certificate cannot secure both distinct CloudPages and Content Builder hostnames in Marketing Cloud's standard SSL configuration.

- Salesforce Marketing Cloud Documentation: Secure Custom Domains (SSL) Implementation Guide

- Salesforce Marketing Cloud Documentation: CloudPages Security and SSL Certificates

To push real-time updates of data rows to a Data Extension using APIs, developers can use the SOAP API DataExtensionObject object (which inserts and updates data rows) or the REST API Data Events route (/hub/v1/dataevents). Both API mechanisms allow real-time transactional manipulation of Data Extension records.

C. The DataExtension SOAP object manages the structural schema definition of a Data Extension, not individual data rows.

D. Uploading files to the Enhanced SFTP executes asynchronous batch imports, which is not a real-time API option.

- Salesforce Marketing Cloud Developer Documentation, "SOAP API: DataExtensionObject".

- Salesforce Marketing Cloud Developer Documentation, "REST API: Data Events (/hub/v1/dataevents)".

In Salesforce Marketing Cloud's legacy v1 (Legacy Package / REST API using the requestToken endpoint), the returned access token is valid for 60 minutes (one hour). The expiresIn value in the authentication response is 3600 seconds. A developer should reuse the same token for all API calls within that window and only request a new token once the current one is about to expire—i.e., approximately once an hour. Requesting a token before every call is unnecessary, adds latency, and can trigger rate-limiting. The token remains valid regardless of which routes or objects are accessed, and the lifetime is one hour, not 15 minutes.

A. Token validity is time-based, not scope/route-based; a single token works across routes and objects.

B. Requesting a token per call is inefficient and unnecessary since tokens persist for the full hour.

D. The v1 token lifetime is 3600 seconds (60 minutes), not 15 minutes.

1. Salesforce Marketing Cloud Developer Documentation — "Access Tokens for API Integrations" / Legacy Package Authentication (/v1/requestToken), section on token response fields (accessToken, expiresIn: 3600). developer.salesforce.com/docs/marketing/marketing-cloud/guide/access-token-s2s.html

2. Salesforce Marketing Cloud REST API Documentation — "Your First API Call," Authentication token lifetime (60 minutes), paragraph on reusing tokens.

3. Salesforce Marketing Cloud Developer Guide — "Legacy REST Authentication," expiresIn field definition (3600 seconds).

Note: The specific v1 requestToken documentation has been largely superseded by the enhanced (v2) OAuth package in current Salesforce documentation; the one-hour (3600-second) token lifetime for v1 is the officially documented behavior.

For configuring an Email Send Logging Data Extension, the proper method is to create it using the SendLog Data Extension Template, which ensures compliance with required fields and structure for logging.

A. Naming alone does not create the necessary logging structure or functionality.

B. Salesforce Support creating the extension does not ensure correct configuration; it is up to the developer.

C. Copying an existing Send Log can lead to incorrect configurations and unique requirements for the business unit.

1. Salesforce Marketing Cloud Developer Documentation, "Creating Send Logging Data Extensions" (https://developer.salesforce.com/docs/atlas.en/marketingcloud/SendLoggingDE.htm)

2. Official Marketing Cloud Data Extension Best Practices, Salesforce Documentation

3. "Creating and Managing Data Extensions," Salesforce Marketing Cloud Documentation (Sections on Send Logs)

4. Salesforce Developer Community Best Practices on Email Logs (https://developer.salesforce.com/community/EmailLogs)

5. Marketing Cloud Email Marketing Essentials Course Material (on Logging Data Extensions)

The RaiseError function stops the send and allows the system to skip the subscriber without sending the email, thus failing the send.

C. The RaiseError function does not send messages to the From Address.

D. The send is not retried; the error stops the process from continuing.

- Salesforce Marketing Cloud Scripting Guide, AMPScript Error Handling.

- Salesforce Developer Documentation, RaiseError Function Use Cases (https://developer.salesforce.com/docs/atlas.en/AMPScriptReference.meta/AMPScriptReference/contentserrorhandling.htm).