Free Salesforce MCE-Con-201 Practice Exam with Questions & Answers | Set: 3

Two distinct root causes commonly prevent click tracking from correctly writing back to Salesforce Contact records. First, using Email Address as the Subscriber Key (A) can cause identity-resolution mismatches between how Marketing Cloud identifies a subscriber for a given click event and how Marketing Cloud Connect attempts to match that event back to the corresponding Salesforce record ID — if these two identity schemes don ' t align cleanly, the tracking data has no reliable path back to the correct Contact record. Second, Individual Level Tracking must be explicitly enabled in the Marketing Cloud Connect configuration for click (and open) events to be captured and associated at the individual subscriber level and written back to Salesforce at all (C) — without this setting selected, engagement data is not tracked with the granularity required for record-level write-back, regardless of Subscriber Key configuration. Option B, using ContactID as Subscriber Key, is actually a recommended best practice for reliable Salesforce record matching and would generally support, not hinder, correct click write-back — making it an incorrect cause. Option D, a 15-minute sync interval for Synchronized Data Sources, describes normal, expected latency for data synchronization and is not a cause of clicks failing to appear at all. Reference: Marketing Cloud Connect Individual Level Tracking, Subscriber Key Best Practices.

SMS/MMS sends in Journey Builder require a fully normalized phone number — country code plus the local number with no additional formatting characters — present directly in the entry-source data extension at the point the SMS activity executes; Marketing Cloud does not automatically infer or append a missing country code on the platform ' s own initiative. Because the root cause described is that the Salesforce-sourced mobile number field lacks the country code altogether, the fix must occur at the data source: formatting the phone field value in Salesforce to explicitly include the country code prefix (+1 for United States numbers) before or as it syncs into the journey ' s entry data extension, ensuring the normalized format Journey Builder requires is present from the start. There is no native ' Normalize Phone Number ' toggle in Journey Builder settings (option A) that automatically fixes missing country codes — this is a fabricated distractor. Configuring a Salesforce field ' s locale setting (option B) affects display/input formatting conventions within Salesforce itself, not the actual stored digit string synced to Marketing Cloud. There is likewise no ' sending country ' selector within the SMS activity configuration (option C) that retroactively corrects malformed source data. Reference: SMS/MMS Activity Phone Number Requirements, Journey Builder Salesforce Entry Sources.

Reply Mail Management supports a set of documented personalization strings specifically designed for use within its auto-forward email template configuration, including a string that renders the actual captured body content of the inbound reply directly inline within the forwarded message sent to an internal team such as Customer Success — this is the native, purpose-built mechanism for exactly this requirement, requiring only template configuration rather than custom development or data querying. RMM ' dynamic content blocks ' (B) is not a real, documented RMM feature; dynamic content blocks are a general Content Builder personalization concept unrelated to RMM ' s specific reply-forwarding template mechanism. There is no ' Include Replies as Attachments ' checkbox (C) in RMM settings — attaching the reply as a separate file is not how RMM ' s native forwarding feature renders reply content; it uses inline personalization strings instead. Option D, querying an ' RMM data view ' and referencing it from a separate data extension, describes an unnecessarily indirect, custom-built workaround for a need RMM ' s own native forwarding template configuration already directly solves through its documented personalization strings. Reference: Reply Mail Management, RMM Personalization Strings.

Flagging a naming discrepancy: the Ad Campaign and Ad Audience activities available on the Journey Builder canvas are enabled and licensed through Advertising Studio, Salesforce ' s official product name for Facebook/Google advertising integration within Marketing Cloud — the option set here labels this ' MC Advertising, ' which is not the documented Salesforce product name, but functions as the closest available option representing that capability among the four choices given. Advertising Studio provisions the connection to ad platforms (starting with Facebook), builds advertising audiences from Marketing Cloud data, and surfaces the Ad Audience and Ad Campaign activities directly on the journey canvas once enabled. Audience Studio (A) is Salesforce ' s separate data management platform (DMP) product for broader audience segmentation and activation across paid media generally, not the specific licensing gate for the Journey Builder Ad Campaign activity. Personalization (C) governs 1:1 web and app experience personalization (formerly Interaction Studio), unrelated to advertising activation. Social Studio (D) was Salesforce ' s social media publishing and listening tool, since retired, and never governed Journey Builder ' s advertising activities. Consultants should recognize any Facebook/advertising activity on the journey canvas as gated by Advertising Studio. Reference: Advertising Studio, Journey Builder Advertising Activities.

Because the data extension is continually appended to via API over time — rather than being a static, one-time-loaded population — the journey ' s Contact Evaluation setting must be configured to ' Evaluate new records only, ' which ensures Journey Builder only evaluates and processes rows that are newly added to the data extension since the last evaluation cycle, correctly picking up each day ' s newly-added payment-reminder subscribers without repeatedly re-processing or re-sending to records that were already added and evaluated on prior days. Setting this to ' Evaluate all records ' (option C) would cause the journey to re-evaluate the entire historical dataset on every cycle, risking duplicate sends to subscribers who were already processed and potentially already received their reminder, which directly undermines correct, one-time-per-cycle processing of a continually-growing data extension. Journey Settings around ' re-entry ' (option D) govern whether the same contact can enter the journey again after completing or exiting a previous run — a related but distinct concern from which specific rows in a growing data extension get evaluated in the first place. Option B ' s ' Use email attribute from Contacts ' setting concerns how the recipient ' s email address is resolved, not which records are evaluated for entry. Reference: Journey Builder Contact Evaluation Settings, Data Extension Entry Sources.

A Salesforce Report is the correct recommendation because it is the tool Sales Cloud users themselves can build and manage manually, directly within their familiar Salesforce interface, without needing any Marketing Cloud access or technical skill — critically, Salesforce Reports natively support combining both Lead and Contact records (through report types built for that combination), and once built, such a report can be directly selected as the target audience within Email Studio ' s Send Flow via Marketing Cloud Connect, which specifically supports sending to Salesforce Reports as an audience source. This directly satisfies the requirement that Sales Cloud users — not Marketing Cloud specialists — are the ones manually creating the segment. Automation Studio (A) and Salesforce Data Extensions or Synchronized Data Extensions (D, B) all require Marketing Cloud-side configuration, SQL knowledge, or Contact Builder access to build and maintain — none of which are accessible or manageable directly by Sales Cloud users working purely within their own CRM interface, working against the explicit ' Sales Cloud users to manually create ' requirement. The Salesforce Report send-flow integration is specifically designed for exactly this kind of CRM-user-driven, cross-object (Lead and Contact) audience creation. Reference: Marketing Cloud Connect Send Flow, Salesforce Report Audiences.

Because the Marketing Cloud Connect app-level connection itself reports as successful, but Sales Cloud objects still fail to appear or synchronize within Contact Builder, the most direct and efficient troubleshooting step is to verify that the specific users involved in the integration — both on the Marketing Cloud side (the integration/API user) and the Sales Cloud side — hold the correct permission sets and role-based access required to expose and synchronize Salesforce objects into Contact Builder, since a successful app connection does not automatically guarantee sufficient object-level and field-level permissions for synchronization to function. This is a targeted, low-effort first diagnostic step consistent with standard troubleshooting methodology: verify permissions before escalating to more invasive fixes. Option A, sending a test email to validate tracking, addresses a different layer of the integration (send-tracking sync) rather than the object-visibility issue described in Contact Builder specifically. Option B, creating new users and reinstalling entirely, is a drastic, high-effort action that should only be considered after simpler causes like permissions have been ruled out. Option C, validating Sales Cloud users have BU access, is narrower and less complete than validating permissions across both platforms, which is the more thorough and correct first diagnostic. Reference: Marketing Cloud Connect Troubleshooting, Contact Builder Salesforce Data.

The requirement has two distinct needs: complex segmentation logic (six-month purchase lookback, likely joining transactional and contact data) and true omnichannel orchestration across email, SMS, and push in a single coordinated flow. A SQL Query Activity in Automation Studio is the right tool to build that segmentation, since it can join multiple data extensions and apply date-based filtering with precision. The output then feeds a Data Extension Entry Source into a journey, and Journey Builder ' s multi-channel activities (Email, SMS, Push) natively send the same coordinated message across whichever channels each contact is opted into, using the same journey path. Option A stops at Automation Studio activities, which lack native multi-channel send orchestration within a single flow. Option B ' s Decision Split without a preceding robust query risks segmentation being handled inside the journey rather than pre-filtered, and pairs oddly with an Import Activity rather than a query against existing data. Option C ' s Salesforce Entry Event is unnecessary complexity when the source data already lives in Marketing Cloud and doesn ' t require Salesforce-triggered entry. The ' Query Activity into a Data Extension Entry Source, then Journey activities ' pattern is the standard, exam-tested approach for segmented, cross-channel, one-message-many-channels campaigns. Reference: Journey Builder Entry Sources, Automation Studio Query Activity, Multi-Channel Messaging.

The Transactional Messaging API is Salesforce ' s purpose-built, API-driven mechanism for sending exactly this class of message — a one-off, highly time-sensitive, security-relevant notification (new-IP login alert) that must be dispatched with minimal latency directly from an external system ' s real-time event trigger, without waiting on any batch, scheduled, or journey-evaluation cycle. Because the request is initiated synchronously via a direct API call at the exact moment the security event (new IP login) occurs, and the response includes send-status confirmation, it delivers the fastest possible deployment path among the available options while also supporting the dynamic, per-message content (the specific login IP) that needs to be included. Injecting the subscriber into a Journey (A) introduces journey entry-evaluation timing and processing overhead that, while often fast, is not as directly immediate as a synchronous transactional API call purpose-built for exactly this kind of urgent, individual, security-triggered message. ' User Initiated Emails Interaction ' (B) and ' Triggered Emails Interaction ' (D) are not standard, precisely-named Marketing Cloud features matching this real-time, API-driven transactional use case as directly as the Transactional Messaging API. Reference: Transactional Messaging API, Security/Fraud Alert Messaging Patterns.