Free Salesforce Marketing Cloud Engagement Consultant Practice Test Questions

Explanation:

For an event-specific notification system (safety alerts, schedule changes, pop-up sessions), the most effective solution is SMS messaging via MobileConnect.

Attendees can opt-in by sending a keyword (e.g., "JOINCONF") to a short code. This automatically subscribes them to an SMS campaign.

Once opted in, NTO can send real-time notifications directly to attendees' phones — the fastest and most reliable channel for urgent updates.

Since attendee and lead data comes from Sales Cloud, Marketing Cloud Connect can synchronize records, but the SMS keyword opt-in ensures compliance and explicit consent for event messaging.

Why not the other options?

A. CloudPages opt-in to Event Journey: Useful for web-based signups, but not ideal for urgent, on-site opt-ins. SMS is faster and more accessible during a live event.

C. Existing Email Event Notification Subscription: Email is slower and less effective for real-time safety or schedule alerts.

D. Smart Capture and Triggered email messaging: Smart Capture is for form submissions, and triggered emails are not suitable for urgent, mobile-friendly notifications.

Reference:
Salesforce Help: MobileConnect Keywords
Trailhead: Marketing Cloud MobileConnect Basics

Explanation:

This scenario requires an email to be sent immediately after a specific customer event: the customer logs in from a new IP address. The email also needs to contain dynamic information about the login IP.

The Transactional Messaging API is designed for exactly this type of use case. Salesforce describes transactional messages as messages sent immediately and automatically in response to an activity, with examples including password resets and other security-sensitive notifications.

The login event can trigger an API request that passes the customer's information, including the new IP address, as part of the transactional message request. This avoids waiting for a Journey entry process or a scheduled/user-initiated send.

Why the other options are incorrect:

A. Inject the subscriber into a Journey — Incorrect:
Journey Builder can react to events, but it introduces a journey-based process that isn't the most appropriate choice when the requirement is to deliver a sensitive, immediate transactional notification.

B. Use a User Initiated Emails Interaction — Incorrect:
A User-Initiated Send is designed for marketer-initiated or scheduled batch sends. It isn't intended for immediate, event-driven security notifications.

C. Use the Transactional Messaging API — Correct:
The Transactional Messaging API sends messages immediately and automatically as a result of an event. It is well suited to security notifications such as a new-IP login alert.

It also supports passing recipient-specific information with the API request, making it appropriate for including the login IP address in the email. Salesforce's documentation notes that transactional messages use send definitions and can be sent through the API.

D. Execute a Triggered Emails Interaction — Incorrect:
A Triggered Email Interaction is also event-driven and can be triggered through an API, but the Transactional Messaging API is specifically designed for immediate transactional messaging and is the better fit for sensitive, time-critical notifications. Salesforce distinguishes transactional messaging from standard triggered sends.

Exam Tip:

For questions involving:

Security alert + real-time event + immediate delivery + dynamic event data

Think:

Event → Transactional Messaging API → Immediate personalized email

Answer: C. Use the Transactional Messaging API.