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

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.

Overwrite is the import type that should be used when the data extension contains all current product information and the product catalog is never the same. This import type will delete all existing records in the data extension and replace them with the new records from the CSV file

 To drive their mobile adoption strategy, NTO could use the following two report types from the Discover Reporting Tool:

• Email Performance by Device1. This report shows the number and percentage of email opens and clicks by device type, such as desktop, mobile, or tablet. This report can help NTO understand how their subscribers are engaging with their emails on different devices and optimize their email design and content accordingly.
• Time Between Send and Engagement2. This report shows the time elapsed between when an email was sent and when a subscriber opened or clicked it. This report can help NTO identify the best time to send emails to their subscribers based on their device preferences and behavior patterns.

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.

The best way to prevent the prefix [PREVIEW] from deploying in live sends is to wrap the subject line with AMP script that checks if the send is a test send or a live send. For example:

%%[

IF _IsTestSend == true THEN

SET @subject = "[PREVIEW] " + @subject

ENDIF

]%%

Using Proof instead of [PREVIEW] does not solve the problem, as it still shows up in live sends. Adding [PREVIEW] to the subject line validation list does not prevent it from deploying, but rather prevents any email with [PREVIEW] in the subject line from being saved. Requiring several campaign approvals does not guarantee that the prefix will be removed before sending.

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.

Importing a file of logged-in customers into NTO’s existing Abandoned Cart journey in Journey Builder is the best action to take. This way, NTO can leverage the existing journey logic and content to send personalized emails to the customers who had their shopping sessions disrupted. The emails can include the items they left in their cart and a link to resume their shopping. Creating a user-initiated message or an apology email are not as effective as using Journey Builder, which allows creating more engaging and relevant customer experiences. Doing nothing is not a good option, as it may result in losing potential sales and customer loyalty.

 Minimum password length is 12 characters and Once created, the user will need to be activated in order to use the SFTP are two considerations that should be taken when configuring an SFTP User. SFTP User is a type of user that allows marketers to securely transfer files between Marketing Cloud and an external location using Secure File Transfer Protocol (SFTP). SFTP User can be configured with different settings, such as username, password, folder access, and activation status. The password for an SFTP User must be at least 12 characters long and must meet certain complexity requirements. The user must also be activated before they can use the SFTP service.

 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

The part of deliverability that is tied to hitting spam traps during a send is list hygiene. List hygiene is the process of maintaining clean and accurate subscriber lists by removing invalid, inactive, or unengaged subscribers

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.

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.

To use Einstein to recommend similar items to customers during the checkout process, NTO needs to add two types of code to their website: Collect Code and Conversion/Cart Code2. Collect Code tracks customer behavior and preferences on the website, while Conversion/Cart Code tracks purchases and cart additions2. Recommendation Code is used to display product recommendations on the website, not during the checkout process2. Email Conversion Code is used to track conversions from email campaigns, not from website visits2.

To import data into a non-sendable data extension without a primary key, the admin could use the Overwrite import type3. This import type will delete all existing records in the data extension and replace them with the new records from the import file. This import type does not require a primary key because it does not need to match or update any existing records. The other options are incorrect because:

• Add Only. This import type will add new records to the data extension without affecting existing records. However, this import type requires a primary key to prevent duplicate records from being added3.
• Add and Update. This import type will add new records and update existing records in the data extension based on the primary key. However, this import type requires a primary key to match and update the existing records3.
• Update Only. This import type will update existing records in the data extension based on the primary key. However, this import type requires a primary key to match and update the existing records3.

To correct the issue of not being designated as an integrated Marketing Cloud user, the admin should apply the administrator and Marketing Cloud Administrator permission sets to the user5. The administrator permission set grants the user access to all standard objects and settings in Sales Cloud, while the Marketing Cloud Administrator permission set grants the user access to Marketing Cloud Connect features and settings in Sales Cloud. These permission sets are required for completing the integration between Sales Cloud and Marketing Cloud. The other options are incorrect because:

• Apply the Marketing Cloud for AppExchange User option as well. This option will not correct the issue, as it only grants the user access to Marketing Cloud Connect features in Marketing Cloud, not in Sales Cloud. The user also needs access to Marketing Cloud Connect features in Sales Cloud to complete the integration5.
• Reset all passwords to force new tokens. This option will not correct the issue, as it only affects the authentication tokens for API users, not for integrated users. The user needs to be designated as an integrated user before they can use their credentials to log in to Marketing Cloud from Sales Cloud5.
• Apply the appropriate user mappings in the CRM configuration. This option will not correct the issue, as it only affects how users are mapped between Sales Cloud and Marketing Cloud based on their email addresses or usernames. The user needs to be designated as an integrated user before they can be mapped between the two systems5.

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.

 Re-entry at any time, no re-entry, and re-entry only after exiting are the options that determine when a contact could enter a journey. These options are available in the journey settings and control how often a contact can enter the same journey based on their previous entry or exit status. Re-entry by attribute and re-entry by date are not valid options for journey re-entry.

To avoid storing email addresses or phone numbers within Marketing Cloud, NTO should use Tokenized Sending2. Tokenized Sending is a feature that allows NTO to send emails or SMS messages using encrypted tokens instead of actual email addresses or phone numbers. The tokens are generated by an external system and stored in a secure database outside of Marketing Cloud. When NTO sends an email or SMS message, Marketing Cloud sends the token to the external system, which decrypts it and returns the actual email address or phone number. This way, NTO can avoid storing sensitive information in Marketing Cloud. The other options are incorrect because:

• Field Level Encryption. This is a feature that encrypts specific fields in data extensions using encryption keys managed by NTO. However, this feature does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only encrypts them within data extensions.
• Lookup reference to Contact Object. This is a method that allows NTO to use a lookup field in a data extension to reference a contact attribute from the Contact Object in Contact Builder. However, this method does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only reduces the duplication of data across data extensions.
• Master-detail relationship to Contacts. This is a type of relationship that allows NTO to link a data extension to the Contacts data model in Contact Builder. However, this type of relationship does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only enables them to use contact attributes for personalization and segmentation.

The File Transfer Activity can be used to decrypt a file on the SFTP server using a PGP key. This activity prepares the file for importing into Marketing Cloud. The other activities do not have the option to decrypt a file.

This is the same question as Question No: 124. The answer is still A.

 To give the marketing analyst access to all tracking data but no send activities, the admin should apply the Analyst and Marketing Cloud Viewer default user roles. The Analyst role allows the user to view tracking data, reports, and dashboards for all channels. The Marketing Cloud Viewer role allows the user to view content, subscribers, and data extensions, but not modify or send them

 Installed Packages is where their Marketing Cloud admin should set up permissions to allow REST authentication. Installed Packages are containers that hold API integrations, components, and permissions in Marketing Cloud. To use the REST API for an external application, the admin needs to create an installed package and configure the API integration settings, such as authentication method, scope, and redirect URI. The admin also needs to assign permissions to the installed package to grant access to specific Marketing Cloud features and data

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

To ensure only specific Contacts are synced from Sales Cloud, the admin should filter records on a Boolean field1. This allows the admin to select only the Contacts that have a true value for a checkbox field, such as “Sync to Marketing Cloud” or "Email Opt-in"1. Filtering records on a formula field, a date field, or existing records in All Subscribers are not supported options for synchronizing Contacts

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.

List Detective is the error code that the file would contain for this record. List Detective is a feature that filters out invalid, malformed, or problematic email addresses from being imported or sent to in Marketing Cloud. List Detective uses a set of rules and filters to check email addresses for syntax errors, spam traps, role accounts, or blocked domains. If an email address fails the List Detective validation, it will not be imported or sent to and the file will contain an error code of List Detective

Configure the business unit data retention setting to 12 months is the policy that the Marketing Cloud admin could configure in Setup. Business unit data retention setting is a setting that allows marketers to specify how long records in data extensions should be retained at the business unit level. By configuring the business unit data retention setting to 12 months, any inactive data that is older than 12 months will be automatically deleted from the data extensions in that business unit2

 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.

 Business unit unsubscribe setting causes an Enterprise level unsubscribe is what could explain this behavior. Business unit unsubscribe setting is a setting that determines how unsubscribes are handled across different business units in an account. If this setting is enabled, when a subscriber unsubscribes from an email sent from one business unit, they will also be unsubscribed from all other business units in the account. This is also known as an Enterprise level unsubscribe

The aspects that would confirm that SAP has been set up on NTO’s account are:

• Upon receiving an email, all tracked links start with click.email.nto.com. This indicates that NTO has configured their SAP with their own domain name (email.nto.com) and subdomain name (click) for link tracking.
• Cloudpages personalized URLs are served from cloud.email.nto.com. This indicates that NTO has configured their SAP with their own domain name (email.nto.com) and subdomain name (cloud) for Cloudpages. The other options are incorrect because:
• The login page for Marketing Cloud Users is login.email.nto.com and is branded with NTO colors. This does not indicate that SAP has been set up, but rather that NTO has configured their own private domain for Marketing Cloud login. This is a separate feature from SAP and does not require SAP to be enabled.
• Users receive Marketing Cloud password reset emails from help@email nto.com. This does not indicate that SAP has been set up, but rather that NTO has configured their own sender address for Marketing Cloud system emails. This is a separate feature from SAP and does not require SAP to be enabled.

 The Collect Tracking code is a JavaScript code that is added to a website to capture and send user behavior data to Marketing Cloud. This data is stored in data extensions and can be used for Einstein Recommendations1

Validate will check if words or phrases used may trigger spam filters, if correct syntax is used on any AMPScript in the email’s code, and if personalization strings map to attributes or data extension fields. A is incorrect because Validate will not check if each content area specified in a dynamic content rule exists. C is incorrect because Validate will not check grammar and spelling in the email text.

 Join is the activity that would allow NTO to build the journey with the fewest activities possible. Join allows you to combine multiple paths into one path based on a common attribute or event. This way, NTO can send five different versions of an initial welcome email using five different paths, and then join them into one path for the follow-up email

 To ensure a notification is received when the query fails, the admin should add their email address in the automation “Runtime Error or Skipped Run Notification Settings”. This setting allows the admin to specify an email address or a data extension to receive notifications when an automation encounters a runtime error or a skipped run. A runtime error occurs when an activity within an automation fails to execute, such as a query that has invalid syntax or references a non-existent data extension. A skipped run occurs when an automation is scheduled to run but does not run because the previous run is still in progress. The other options are incorrect because:

• Install the Marketing Cloud App on phone to receive Push Messages. This option will not ensure a notification is received when the query fails, as the Marketing Cloud App does not support push notifications for automation errors or skipped runs. The Marketing Cloud App only supports push notifications for Journey Builder entry events and email sends.
• Add their Email Address in the Query Activity Notifications Field. This option will not ensure a notification is received when the query fails, as the Query Activity Notifications Field only sends notifications when the query completes successfully. The notifications include information such as the number of records processed, added, updated, skipped, or failed.
• Configure the “Event Notification Service” in Setup with their Email Address. This option will not ensure a notification is received when the query fails, as the Event Notification Service is a feature that allows external systems to subscribe to events that occur in Marketing Cloud, such as email sends, opens, clicks, bounces, and unsubscribes. The Event Notification Service does not support events related to automation errors or skipped runs.

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 append an Urchin Tracking Module (UTM) variable string to links in emails, NTO should use Web Analytics Connector. Web Analytics Connector is a feature that allows NTO to append UTM variables or other custom parameters to the links in their emails. Web Analytics Connector can be configured at the account, business unit, or send level, and can support up to four parameters per link. The other options are incorrect because:

• Advertising Studio. This is a product that allows NTO to create and manage advertising campaigns across various channels, such as Facebook, Google, or Twitter. However, this product does not allow NTO to append UTM variables to links in emails; it only allows NTO to use their Marketing Cloud data for audience segmentation and targeting.
• Personalization Builder. This is a product that allows NTO to create and deliver personalized content and recommendations to their subscribers based on their behavior and preferences. However, this product does not allow NTO to append UTM variables to links in emails; it only allows NTO to use predictive intelligence and machine learning to optimize their content and offers.
• Web and Mobile Analytics. This is a product that allows NTO to collect and analyze web and mobile data from their subscribers, such as page views, visits, conversions, and revenue. However, this product does not allow NTO to append UTM variables to links in emails; it only allows NTO to use web tracking code and mobile SDKs to capture and report on their web and mobile activity.

After a Contact Delete request has been processed for subscribers who have been sent an email previously, the following data would still exist in the account:

• Contact-specific data at the job level. This includes data such as open rate, click rate, bounce rate, and unsubscribe rate for each individual contact who received an email. This data is not deleted because it is used for reporting and analytics purposes.
• General tracking data at the job level. This includes data such as total number of sends, opens, clicks, bounces, and unsubscribes for each email job. This data is not deleted because it is used for reporting and analytics purposes. The other options are incorrect because:
• Contact data in non-sendable data extensions. This includes data such as name, address, phone number, and other attributes for each contact. This data is deleted because it is not used for sending emails and it is considered personal information.
• Contact data in sendable data extensions. This includes data such as email address and subscriber key for each contact. This data is deleted because it is used for sending emails and it is considered personal information.

Custom roles are available on their Marketing Cloud account is what should be taken into consideration to accomplish this. Custom roles are roles that can be created and modified by Marketing Cloud administrators to grant specific permissions to users based on their business needs. Custom roles can be applied to users across all business units in an account or within a specific business unit

 Setup Assistant is a prioritized account configuration checklist that guides you through the essential steps to set up your Marketing Cloud account. It provides links to relevant documentation and resources to help you complete each task

To record send log data, the send logging feature must be enabled for the send. This can be done by selecting the send log data extension in the Delivery Options tab of the email send wizard.

 Setup Assistant covers the following two topics:

• Setting up the Data Structure. This topic provides information and resources for configuring the data structure in Marketing Cloud, such as creating data extensions, importing data, setting up data retention policies, and managing subscriber status.
• Enabling Mobile Connect. This topic provides information and resources for enabling Mobile Connect in Marketing Cloud, such as creating keywords, setting up short codes or long codes, creating text messages, and sending text messages. The other options are incorrect because:
• Configuring Journey Builder. This is not a topic that Setup Assistant covers, as Journey Builder is a product that allows NTO to create and manage customer journeys across various channels, such as email, mobile, social, or advertising. However, Setup Assistant does not provide information or resources for configuring Journey Builder; it only provides information or resources for configuring Marketing Cloud products that are included in the core subscription.
• Managing the Enhanced SFTP. This is not a topic that Setup Assistant covers, as Enhanced SFTP is a feature that allows NTO to securely transfer files between Marketing Cloud and external systems using SFTP protocol. However, Setup Assistant does not provide information or resources for managing the Enhanced SFTP; it only provides information or resources for managing Marketing Cloud products that are included in the core subscription.

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

 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.

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