Salesforce-Marketing-Cloud-Engagement-Developer Practice Test

Salesforce Spring 25 Release
196 Questions

A developer is creating a custom preference center and wants to log unsubscribe events from the CloudPage. Which set of parameters should be captured and provided to the LongUnsubEvent Execute Call to ensure accurate unsubscribe information?

A. SubscriberKey and JobID

B. SubscriberID and BatchID

C. EmailAddress and JobID

D. SubscriberKey and BatchID

A.   SubscriberKey and JobID

Explanation:

✅ SubscriberKey and JobID
This is the correct pair of parameters required for the LogUnsubEvent Execute Call in order to accurately log an unsubscribe event from a CloudPage. The SubscriberKey uniquely identifies the subscriber across the Marketing Cloud account, and JobID identifies the specific send job (email deployment) associated with the unsubscribe. Using both ensures that the unsubscribe is tied directly to the correct subscriber and specific email they are opting out from. Without this, unsubscribe behavior can be inaccurately tracked or not tracked at all.

❌ SubscriberID and BatchID
This pair may seem plausible but is incorrect. SubscriberID is an internal, system-generated identifier and is not typically used in scripting or API calls. BatchID refers to a grouping of subscribers within a send job but does not uniquely identify a subscriber or an email. These parameters are not sufficient or correct for the LogUnsubEvent API call, which expects a SubscriberKey and JobID to perform a properly scoped unsubscribe event logging.

❌ EmailAddress and JobID
Using EmailAddress instead of SubscriberKey is a common mistake. While EmailAddress might appear unique, in many Marketing Cloud accounts it is not (e.g., one email address can belong to multiple subscribers with different SubscriberKeys). Therefore, using only EmailAddress introduces risk of inaccurate targeting. Although JobID is correct, EmailAddress is not a reliable identifier for the LogUnsubEvent API call. SubscriberKey should always be used for identity management in modern Marketing Cloud practices.

❌ SubscriberKey and BatchID
While SubscriberKey is correct, BatchID is not a suitable replacement for JobID in the LogUnsubEvent Execute Call. BatchID is used for tracking segments within a larger job, but it doesn't provide a complete picture of the full send job. Without the JobID, the unsubscribe cannot be tied directly to a specific send, which is critical for accurate tracking and compliance. Thus, this option is partially correct but ultimately insufficient.

Salesforce-Marketing-Cloud-Engagement-Developer Practice-Test - Home Previous
Page 15 out of 196 Pages