certified-marketing-cloud-administrator Sample Questions & Answers

This is the standard, most efficient method. By creating a suppression list in the parent (Enterprise) BU and sharing it with all child BUs, it becomes a centralized list. Then, by associating this shared suppression list with the commercial Send Classifications used across the enterprise, every commercial send will automatically check against this single, authoritative list, ensuring global suppression.

This is the most robust and scalable solution. The Smart Capture form on the CloudPage captures the signup and writes it to a designated data extension. A Journey Builder journey configured with that data extension as the entry source can then immediately inject the new subscriber. The journey can send the initial welcome email instantly and use Wait activities to perfectly time the subsequent emails in the educational series, all within a single, manageable workflow.

SPF is a DNS record that specifies which mail servers are authorized to send email on behalf of a domain. It's a fundamental authentication method required by all major inbox providers to verify sender identity.

DKIM adds a digital signature to emails, allowing the receiving server to verify that the message was sent from an authorized server and that its content hasn't been altered in transit. It is a core authentication requirement.

The Audit Trail is the primary tool for investigating changes within a Marketing Cloud Engagement account. Since the user's direct permissions were not changed, the administrator should check the Audit Trail to see if a Role's permissions were modified, a Business Unit's settings were altered, or if another system-level change occurred that would affect this user's access. It provides a chronological log of actions taken in the account.

In MobileConnect, the STOP keyword is a universal, system-level keyword that automatically handles opt-out requests. When a subscriber replies with 'STOP', MobileConnect processes it, unsubscribes the contact from the short/long code, and sends a confirmation message. This is a critical feature for SMS compliance.

The Contact Key (often referred to as Subscriber Key in Email Studio) is the unique identifier for a contact in Marketing Cloud Engagement. Using a consistent Contact Key, such as a CRM ID or a customer number, across all channels ensures that all interactions are tied to a single contact record, providing a unified view of the customer.

This is the correct and most scalable method. The '_Sent' Data View contains a record of every email sent from the account. A SQL Query Activity can perform a LEFT JOIN from the primary audience DE to the '_Sent' Data View, filtering for sends within the last 3 days. By selecting only those records that do not have a match (WHERE s.SubscriberKey IS NULL), the query effectively creates a new, clean sendable data extension that meets the exclusion criteria.

This is true. To enable Send Logging, an administrator must create a data extension from the SendLog template, which includes these required fields. Once created and enabled in the account, this data extension will automatically be populated with a row for each recipient of every send (excluding test sends) within that Business Unit, providing a valuable record for auditing and analysis.

This is the correct process. Synchronized Data Sources can sync standard and custom objects. The administrator must first add the custom object to the sync. Including the lookup field to the Contact object is crucial as it provides the key for joining the two datasets. Finally, a SQL Query Activity is required in Automation Studio to join the data from the two resulting synchronized data extensions to create a final, sendable segment.

Test Mode is the specific Journey Builder feature designed for this purpose. It allows the user to select a contact (or multiple contacts) and simulate their path through the journey. The interface will visually trace the path the contact would take through each activity and decision split based on their data, allowing for thorough validation of the journey logic before activation.