Marketing-Cloud-Administrator Salesforce Certified Marketing Cloud Administrator (SP23) Questions and Answers

Journey Builder and Mobile Push are two products that would allow them to send push notifications to customers with their mobile app. Journey Builder is a product that allows marketers to create and execute cross-channel customer journeys based on events, activities, and goals. Journey Builder can be used to send push notifications to mobile app users as part of a journey. Mobile Push is a product that allows marketers to create, manage, and deliver push notifications to mobile app users. Mobile Push can be used to send push notifications as standalone messages or as part of a journey

Smart Capture is the feature that should be used to create a survey form. Smart Capture is a feature that allows marketers to create and insert forms within landing pages or emails, such as surveys, polls, or feedback requests. Smart Capture can be customized with different fields, labels, buttons, and actions. Smart Capture can capture subscriber responses and store them in a data extension or update existing records in Marketing Cloud.

There are overlapping contacts in each of the channel is why the total contact count would be less than the total number of contacts from all data sources. Contacts are unique individuals who can be reached through one or more channels in Marketing Cloud, such as email, mobile, or social. Contacts are counted based on their Contact Key, which is a unique identifier for each contact. If a contact has multiple channels associated with them, such as email and mobile, they are only counted once in the total contact count. Therefore, if there are overlapping contacts in each of the channel, the total contact count would be less than the sum of contacts from all data sources

 The Marketing Cloud admin should consider that building desirable sending history and data will be variable based on list size and engagement when sending from the new IP address. A new IP address has no reputation with ISPs and needs to be warmed up gradually by sending emails to engaged and active subscribers. The send volume and frequency should be adjusted according to the list size and engagement level of NTO’s subscribers to avoid being marked as spam or blocked by ISPs. The other options are incorrect because:

• The IP address is on reserve, is already in use, and has an email sending history. This describes an existing IP address, not a new one. An existing IP address already has a reputation with ISPs and does not need to be warmed up.
• Sending in large volumes will alert ISPs the new IP Address is now in use. This is not a consideration, but rather a mistake. Sending in large volumes from a new IP address will raise red flags with ISPs and may result in poor deliverability or blacklisting.
• Migration of larger marketing campaigns is necessary prior to bringing on smaller, triggered campaigns. This is not a consideration, but rather the opposite of what should be done. Migration of smaller, triggered campaigns should be done first before bringing on larger marketing campaigns, as this will help build trust and reputation with ISPs.

Create child business units for each brand and nest another level of child business units for GEOs is how the rest of the business units should be organized. Business units are organizational units that allow marketers to segment their Marketing Cloud account based on different brands, regions, products, or channels. By creating child business units for each brand and nesting another level of child business units for GEOs, NTO can manage their marketing activities and assets for each subsidiary brand and location separately

Creating a one-to-many relationship between Orders and Order_Details is the correct action, as each order can have multiple order details, but each order detail belongs to only one order. Creating a one-to-one relationship between Order_Details and Products is the correct action, as each order detail corresponds to only one product, and each product can be in only one order detail. Creating a one-to-one relationship between the contact record and Order Details is not correct, as each contact can have multiple order details, and each order detail can belong to different contacts. Creating a one-to-one relationship between Orders and Order_Details is not correct, as each order can have multiple order details.

Email Form Content Block is the feature that could be used to solicit website feedback without navigating away from the email. Email Form Content Block is a type of content block that allows marketers to create and insert forms within emails, such as surveys, polls, or feedback requests. Email Form Content Block can be customized with different fields, labels, buttons, and actions. Email Form Content Block can capture subscriber responses within the email without requiring them to visit a landing page or a website

From Address Management is where a Marketing Cloud admin can view all verified email addresses. This feature allows you to manage sender authentication for your email sends by verifying your from addresses and domains.

 Send classifications require defining a sender profile and a delivery profile. A sender profile defines the From Name, From Email, and Reply Email for an email send. A delivery profile defines the IP address, domain, and header and footer information for an email send. Defining a subscriber-specific From Name and custom Reply Mail Management are not necessary for creating send classifications.

The reason why the customer continues to receive NTO’s daily digest at their old address is because the email address in All Subscribers is prioritized. All Subscribers is the master list of subscribers in Marketing Cloud that stores their email address and subscription status. When NTO sends an email to a data extension, Marketing Cloud checks if the subscriber exists in All Subscribers and uses their email address and status from there. Therefore, deleting the customer from the data extension does not affect their subscription status or email address in All Subscribers. NTO’s Marketing Cloud Admin should update or delete the customer from All Subscribers instead. The other options are incorrect because:

• Data retention settings were incorrect in the data extension. Data retention settings determine how long records are kept in a data extension before they are deleted or archived. However, this does not affect the subscription status or email address of subscribers in All Subscribers.
• Contact Builder was not configured properly. Contact Builder is a tool that allows NTO to manage their contacts and their attributes across different data sources. However, this does not affect the subscription status or email address of subscribers in All Subscribers.
• The data extension was not configured as sendable. A sendable data extension is one that has an email address field and a subscriber key field that can be used for sending emails. However, this does not affect the subscription status or email address of subscribers in All Subscribers.

The correct answer is A and D because Data Designer can be used to link data from different sources to the contact record, and Synchronized Data Sources can be used to bring data from Sales Cloud into Marketing Cloud. B is incorrect because Import Activity cannot import data from a Salesforce Report. C is incorrect because list attributes are not related to Sales Cloud data.

Publication lists are the feature that should be utilized to make this happen. Publication lists are used to manage subscribers’ preferences for different types of communications, such as newsletters, promotions, or alerts. The built-in subscription center allows subscribers to opt-in or opt-out of publication lists, as well as the master list

Data Extension, Audience Studio, API Event, Date Based Event are entry source types for Journey Builder. Entry source types are types of events or data sources that can trigger contacts to enter a journey in Journey Builder. Data Extension is an entry source type that allows contacts from a data extension to enter a journey based on a schedule or an automation. Audience Studio is an entry source type that allows contacts from Audience Studio segments to enter a journey based on a schedule or an automation. API Event is an entry source type that allows contacts to enter a journey based on an API call from an external system or application. Date Based Event is an entry source type that allows contacts from a data extension to enter a journey based on a date field in the data extension, such as birthday or anniversary.

When creating a data extension, the fields that would need minimal consideration for size/scalability reasons are text and Boolean. Text fields can store up to 4000 characters and boolean fields can store only true or false values. Number and decimal fields can store larger values and may require more storage space.

Change Character Encoding to UTF-8 and Select Unicode Output are two settings that could solve this issue. Character Encoding is a setting that determines how characters are encoded and decoded when importing or exporting data in Marketing Cloud. UTF-8 is a type of character encoding that supports all characters in the Unicode standard, including accented characters. Unicode Output is a setting that enables the output file to be encoded in UTF-8 format when exporting data from Marketing Cloud. By changing Character Encoding to UTF-8 and selecting Unicode Output, the admin can ensure that accented characters are displayed correctly in the extracted file.

 To resolve the issue of not being able to see the audience file in the data extension when scheduling the send, the admin should confirm that the data extension is marked as Sendable. A sendable data extension is one that has an email address field and a subscriber key field that can be used for sending emails. If the data extension is not marked as sendable, it will not appear as an option when selecting an audience for an email send. The other options are incorrect because:

• The data extension contains a Salesforce ID. This is not a requirement for sending emails from a data extension. A Salesforce ID is only needed if NTO wants to use Marketing Cloud Connect to sync data between Marketing Cloud and Salesforce CRM.
• The Data extension is marked as Sendable and Testable. This is not a valid option for marking a data extension. A data extension can only be marked as sendable or non-sendable; there is no testable option.
• The data extension is linked using the Contact Key. This is not a requirement for sending emails from a data extension. The Contact Key is only needed if NTO wants to use Contact Builder to link data across different sources and channels.

The recommended best practice for font usage in email is to use a web-safe font for text that closely matches the brand’s custom font. Web-safe fonts are fonts that are commonly available across different operating systems and email clients. Using a web-safe font ensures that the email text will be displayed consistently and legibly to the subscribers

Using %%FILENAME_FROM_TRIGGER%% in the Import File Activity allows the automation to import any file that matches the filename pattern, regardless of the date and time stamp. This is the recommended solution for File Drop Automations

To pass the email address of a subscriber to a landing page through a URL parameter from a promotional email securely, the admin should use the CloudPagesURL AMPscript function. This function encrypts the email address and other parameters and generates a unique URL for each subscriber. The landing page can then use the RequestParameter AMPscript function to decrypt the email address and other parameters

To copy journeys across business units, NTO should use Journey Templates1. Journey Templates are reusable journey structures that can be created and shared across business units. NTO can use Journey Templates to replicate journey structure so it can be easily recreated in another account. The other options are incorrect because:

• Deployment Manager. This is a tool that allows NTO to deploy assets and configurations across business units or accounts. However, this tool does not support journeys as an asset type, so it cannot be used to copy journeys across business units2.
• Journey Extracts. This is a feature that allows NTO to export journey data and metrics for reporting and analysis purposes. However, this feature does not allow NTO to copy or import journeys across business units; it only provides a snapshot of journey performance3.
• Copy activities. This is an option that allows NTO to copy individual activities within a journey and paste them in the same or another journey. However, this option does not allow NTO to copy the entire journey structure across business units; it only copies one activity at a time4.

To troubleshoot the issue with their sends, NTO can use the following links in Setup Home:

• Failed Sends3. This page shows the details of any sends that failed to complete due to errors or issues with the send definition or data extension3.
• System Status4. This page shows the current status and performance of Marketing Cloud and its features, such as Email Studio, Journey Builder, and Automation Studio4. The other options are not relevant for troubleshooting send issues because:
• Create Support Case5. This link allows NTO to create a case with Salesforce Support for any technical issues or questions they have with Marketing Cloud. However, this is not a direct way to troubleshoot their own send issues.
• Help and Training. This link allows NTO to access various resources and guides for learning and using Marketing Cloud. However, this is not a specific way to troubleshoot their own send issues.

 When setting up Distributed Marketing, the admin should consider the following:

• Default options can be set up for the greeting in the email2. This allows the admin to define how the email will address the recipient, such as by first name, last name, or salutation2.
• A journey can be connected to one or more Campaigns2. This allows the admin to associate a journey with a Salesforce object, such as an opportunity or a case, and trigger personalized messages based on the Campaign status2.
• Messages can be sent to Contacts, Leads, and Person Accounts2. These are the supported recipient types for Distributed Marketing messages2. The other options are incorrect because:
• Business users cannot select any email at the time of sending2. They can only select from the pre-approved emails that are configured by the admin in Marketing Cloud2.
• The DM administrator Profile is not required to access Distributed Marketing2. The admin can use any Profile that has the appropriate permissions and settings for Distributed Marketing

Advertising Studio supports lookalike audiences directly from Facebook only. For other networks, such as Google and Twitter, Advertising Studio can create audience segments based on Marketing Cloud data and export them to the network’s platform, where the lookalike audience can be created manually.

When using a filename pattern for a File Drop Automation trigger, the import File Activity should use %%FILENAME_FROM_TRIGGER%% as the file name. This ensures that the import activity will use the same file name as the trigger, regardless of the date stamp or other variations

The utm_campaign value should be configured at the email level. This level allows marketers to specify a campaign identifier for each email message that contains links with tracking parameters. The utm_campaign value can be used to group email messages by campaign in Google Analytics or other analytics tools

To resolve the issue of the encrypted file being decrypted after the File Transfer Activity completes, the decrypted data would be in the original SFTP folder. The File Transfer Activity can be configured to decrypt an encrypted file using a decryption key provided by NTO. The decrypted file will be placed in the same location as the encrypted file on the SFTP site. The other options are incorrect because:

• Selected SFTP folder. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not allow NTO to select a different SFTP folder for the decrypted file. The decrypted file will be placed in the same location as the encrypted file on the SFTP site.
• Target Data Extension. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not import data into a data extension. The File Transfer Activity only moves files from one location to another, such as from an FTP site to the Safehouse or from the Safehouse to a data extension. To import data into a data extension, NTO needs to use an Import File Activity.
• Safehouse. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not move files to the Safehouse when decrypting them. The File Transfer Activity only moves files to the Safehouse when encrypting them or when transferring them from an external FTP site to Marketing Cloud. The Safehouse is a temporary storage location within Marketing Cloud that can be used for staging files before importing them into a data extension.

 Account Send Summary Report is the email report that NTO’s Marketing Analyst should pull from Marketing Cloud to get this information. Account Send Summary Report provides a summary of email metrics for all business units in an account or for a specific business unit. The report includes the number of sends, delivery rate, overall bounce rate, block bounce rate, open rate, click rate, complaint rate, and unsubscribe rate for each email campaign

Run Once schedule type and Winner evaluation are two settings that should be selected before the admin can configure the Holdback percentage. Path Optimizer is a feature that allows marketers to test different paths in a journey and select a winner based on a specific metric. To use Path Optimizer, the admin needs to select a schedule type of Run Once, which means the journey will run only once for a single batch of contacts. The admin also needs to select a winner evaluation, which determines how long the test will run and how the winner will be chosen. After selecting these settings, the admin can configure the Holdback percentage, which is the percentage of contacts that will not enter any path until a winner is selected

 Einstein Email Recommendations is a product that enables a Marketing Cloud admin to observe customer behavior, build performance profiles and deliver the next best content. This product uses predictive intelligence to recommend products or content based on each customer’s preferences and actions. The other products do not have this capability.

A multiplier is applied to each SMS message based on the destination country, which could explain why NTO is already at 75% utilization for their annual Super Messages. For example, sending an SMS message to a subscriber in Germany consumes 1.5 Super Messages, while sending an SMS message to a subscriber in India consumes 3 Super Messages. The other options are not true or relevant.

Before updating and increasing their session timeout setting, the admin should review the following three considerations:

• Frustration of users upon timeouts. The admin should consider how users feel when their sessions expire and they have to log in again. Increasing the session timeout setting can reduce user frustration and improve user experience by allowing them to stay logged in longer.
• Security risk of unauthorized users for longer timeout settings. The admin should consider how longer timeout settings can increase the security risk of unauthorized users accessing Marketing Cloud. Increasing the session timeout setting can expose user accounts and data to potential threats if users leave their devices unattended or share them with others.
• Change impacts all users. The admin should consider how changing the session timeout setting will affect all users within their account or business unit. Increasing the session timeout setting will apply to all users who log in to Marketing Cloud after the change, regardless of their roles or permissions. The other option is incorrect because:
• Typical length of time users spend in Marketing Cloud. This is not a consideration for updating and increasing their session timeout setting, as it does not affect the security or user experience of Marketing Cloud. The typical length of time users spend in Marketing Cloud may vary depending on their tasks and needs, but it does not determine how long their sessions should last before expiring.

Removing Marketing Cloud Channel Manager is the best way to update the user to allow the analyst the appropriate access. Marketing Cloud Channel Manager is a permission set that grants access to create, edit, and delete content across all channels. This permission set is not necessary for importing contact lists and may pose a security risk.

The Time Between Send and Engagement report shows how long it takes for subscribers to open or click an email after it is sent, which can help optimize the send time for mobile users. The Email Performance by Device report shows how subscribers interact with emails on different devices, such as desktops, tablets, or phones, which can help design responsive emails for mobile users.

Synchronized Data Sources can use two types of filters: attribute filters and relationship filters. Attribute filters are based on the fields of the object being synced, such as email address or opt-out status. Relationship filters are based on the fields of a related object, such as account or campaign. Filtering by email open activity or subscriber status is not possible with Synchronized Data Sources.

The Einstein STO activity allows the journey to send five different versions of an initial welcome email to new subscribers at the optimal time for each subscriber. This activity requires only one email and one activity, whereas the Join activity would require five emails and five activities.

To add a set of four tracking parameters automatically to all the links in an email sent via Email Studio, the admin should suggest using the Web Analytics Connector1. The Web Analytics Connector is a feature that allows NTO to append Urchin Tracking Module (UTM) variables or other custom parameters to the links in their emails. The Web Analytics Connector can be configured at the account, business unit, or send level, and can support up to four parameters per link1.

To correct the issue of insufficient user permissions, the admin should apply the Administrator and Marketing Cloud Administrator permission sets to the user. These permission sets grant access to the Marketing Cloud tab in Sales Cloud and allow the user to complete the integration. The Marketing Cloud for AppExchange Admin option is not enough to grant access to the Marketing Cloud tab

Adding a domain to the export email whitelist and enforcing export email whitelist are the steps that should be taken to implement this. This will restrict the email addresses that can receive tracking data via email to only those that match the specified domain

To create and schedule a weekly report with high-level metrics, the Marketing Cloud admin should use Analytics Builder. Analytics Builder allows users to create, view, and share reports and dashboards. The Account Send Summary report shows how many emails were sent in a given time period.

A block bounce is a type of bounce that occurs when an ISP rejects an email because of the sender’s reputation or content. This indicates that the ISP views the sender as a potential spammer or has received complaints from other recipients.

Linking the Customers data extension to the data model using Customer ID and linking the Orders data extension to the Customers data extension using a One-to-Many relationship are the best ways to configure Data Designer to allow this data to be used within a Journey. Customer ID is a unique identifier that can be used to link data extensions in Data Designer. A One-to-Many relationship means that one customer can have multiple orders, which reflects the data model scenario.

Product code, application ID, and subscriber ID are values that can be used as personalization strings in query string parameters without violating PII regulations. Email address and name are considered PII and should not be used in query string parameters.

 To clear inactive data stored in data extensions after 12 months, NTO should apply a row-based retention to each data extension as it is created, set to 12 months. This will delete any records that have not been modified in the last 12 months. Row-based retention can be applied to individual data extensions or data extension templates

To create a suppression list for hard-bounced email addresses, the Marketing Cloud admin should query the Bounce Data View. The Bounce Data View is a system data view that stores information about bounced emails, such as the subscriber key, email address, bounce category, bounce type, and bounce reason. The admin can use SQL queries to filter the records in the Bounce Data View based on the bounce category or type and create a suppression list from the results. The other options are incorrect because:

• Run a Bounce Email Report. This is a standard report that shows the number and percentage of bounced emails by category and type for a specific time period or email job. However, this report does not provide the details of the bounced email addresses, which are needed to create a suppression list.
• Query the Send Log. The Send Log is a custom data extension that stores information about sent emails, such as the subscriber key, email name, subject line, send date, and any additional attributes. However, this data extension does not store information about bounced emails, which are needed to create a suppression list.
• Run an Account Send Summary Report. This is a standard report that shows the summary of email sends across an account or a business unit for a specific time period. However, this report does not provide the details of the bounced email addresses, which are needed to create a suppression list.

Synchronized Data Sources is the feature that would allow this functionality. Synchronized Data Sources are data sources that allow marketers to import and synchronize data from Salesforce CRM objects into Marketing Cloud data extensions. Synchronized Data Sources can be configured with different settings, such as sync frequency, field mapping, and filter criteria. Synchronized Data Sources enable marketers to use Sales Cloud data in their queries and other Marketing Cloud activities.

 The correct answer is C because File Drop Automation can be used to trigger an automation when a file is dropped on the SFTP, and Import File Activity and SQL Query Activities can be used to import and separate the data into different data extensions. A is incorrect because Scheduled Automation cannot check if the file is present on time. B is incorrect because Scheduled Automation cannot trigger an alert if the file is not present. D is incorrect because Filter Activity cannot separate the data into different data extensions.