Salesforce Marketing-Cloud-Administrator Salesforce Certified Marketing Cloud Administrator (SP23) Exam Practice Test

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.

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

 When a Contact Delete request is processed, the contact data in sendable data extensions and the contact-specific data at the job level are deleted. However, the contact data in non-sendable data extensions and the general tracking data at the job level are retained

 The two fields that would need minimal consideration for size/scalability related reasons when creating a data extension to house the data are:

• Number. This is a field type that stores numeric values in a data extension. A number field can store up to 18 digits before the decimal point and up to 2 digits after the decimal point5. A number field has a fixed size of 8 bytes regardless of the number of digits stored in it. Therefore, a number field would need minimal consideration for size/scalability related reasons when creating a data extension.
• Boolean. This is a field type that stores logical values in a data extension. A boolean field can store only two possible values: true or false5. A boolean field has a fixed size of 1 byte regardless of the value stored in it. Therefore, a boolean field would need minimal consideration for size/scalability related reasons when creating a data extension. The other options are incorrect because:
• Text. This is a field type that stores alphanumeric values in a data extension. A text field can store up to 4000 characters per value5. A text field has a variable size depending on the number of characters stored in it; each character takes up 1 byte of space. Therefore, a text field would need considerable consideration for size/scalability related reasons when creating a data extension.
• Decimal. This is a field type that stores numeric values with decimal precision in a data extension. A decimal field can store up to 28 digits before the decimal point and up to 10 digits after the decimal point5. A decimal field has a variable size depending on the number of digits stored in it; each digit takes up 0.5 bytes of space. Therefore, a decimal field would need considerable consideration for size/scalability related reasons when creating a data extension.

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

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.

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.

 To create an audience based on complex criteria such as engagement and location, NTO should use SQL Queries5. SQL Queries allow NTO to write custom queries that can join data from different data extensions and filter based on various conditions5. Measures are used to define engagement metrics such as opens and clicks, but they cannot be used to filter by location or combine with other criteria5. Data Filters are used to filter data based on simple criteria such as attributes or measures, but they cannot be used to join data from different sources or filter by location5. Journey is used to create personalized customer journeys based on triggers and activities, but it is not a tool for creating audiences5.

 To link the new data extensions to the existing contact records, the subscriber ID value should be used. Subscriber ID is a unique identifier for each contact in Marketing Cloud and is automatically generated when a contact is created. It can be used to relate data extensions in Data Designer.

 To ensure Journey Builder directs the subscribers correctly, contact data should be used for the decision split. Contact data is the data that is stored in the contact model and is available for all journeys. Journey data is the data that is captured at the point of entry and is specific to each journey.

Parameter Manager is the solution that the admin should suggest. Parameter Manager is a feature that enables marketers to automatically append tracking parameters to links in emails, such as UTM variables. Parameter Manager can be configured at the account, email, or link level

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

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.

 Lifetime Purchase Value, Conversion Rate, and Last Purchase Date are three criteria that the customer should use to create an audience for this campaign. These criteria help to identify the highest-value outdoor sports customers who are most likely to respond to the product discount

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

The correct answer is B because SQL can be used to cross-reference the records in each registration data extension with corresponding invitation email sends, and to send a follow-up email to customers who click on the registration link but do not complete registration. A is incorrect because AMPscript cannot be used to cross-reference records or send follow-up emails. C is incorrect because HTML cannot be used to cross-reference records or send follow-up emails. D is incorrect because CSS cannot be used to cross-reference records or send follow-up emails.

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 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.

 Administrator and Marketing Cloud Administrator are two standard roles that should be selected for the new user. Administrator is a standard role that grants full access to all features and functions in Marketing Cloud, such as creating and managing users, roles, permissions, business units, and security settings. Marketing Cloud Administrator is a standard role that grants access to all features and functions in Marketing Cloud except for user management. By selecting both roles, the new user will have full administrator permissions in Marketing Cloud

The three statements that should be considered before using Goals in Journey Builder are:

• Goals are created to evaluate journey performance. This statement is true, as goals are used to measure how well a journey is achieving its desired outcome or objective. Goals can also help NTO to optimize their journey by identifying which activities or paths are more effective in reaching the goal1.
• Goals can act as exit criteria. This statement is true, as goals can be configured to exit contacts from a journey when they meet the goal criteria. This can help NTO to save resources and avoid sending irrelevant messages to contacts who have already achieved the desired outcome or objective1.
• Contacts are evaluated against the goal after a wait activity. This statement is true, as contacts are only evaluated against the goal when they reach a wait activity in the journey. Wait activities are used to pause the journey for a specified amount of time or until a specific date or event occurs. After the wait period ends, contacts are evaluated against the goal and either exit the journey or continue to the next activity

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 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 Email Send Report in Analytics Builder is the best place to view the total number of emails sent across all business units in the last calendar year. This report provides a summary of email performance metrics such as sends, opens, clicks, bounces, and unsubscribes for a specified time period.

To avoid storing sensitive data in the cloud, the admin should use Tokenized Sending. This feature allows Marketing Cloud to send emails without storing sensitive data such as credit card numbers or social security numbers. Instead, Marketing Cloud uses tokens that are replaced with actual data at send time by an external system.

To ensure users have access to Query Studio for Marketing Cloud, the admin should license all appropriate users within the installed package. Query Studio is an app that allows users to write and run SQL queries on data extensions within Marketing Cloud. To use Query Studio, users need to be licensed by the admin within the installed package settings. The admin can select which users or roles can access Query Studio and assign them a license. The other options are incorrect because:

• Choose Public App Integration during the installation. This option will not ensure users have access to Query Studio for Marketing Cloud, as it only affects how Query Studio connects to Marketing Cloud via API. Choosing Public App Integration means that Query Studio will use a single API user for all requests, while choosing Private App Integration means that Query Studio will use each user’s own API credentials for requests. However, this does not affect whether users can access Query Studio or not; they still need to be licensed by the admin within the installed package settings.
• Install App-appropriate business units for expanded access. This option will not ensure users have access to Query Studio for Marketing Cloud, as it only affects which business units can use Query Studio. Installing App-appropriate business units means that Query Studio will be available in all business units within an account, while installing App-specific business units means that Query Studio will be available only in selected business units. However, this does not affect whether users can access Query Studio or not; they still need to be licensed by the admin within the installed package settings.
• Configure the API Integration to allow all users access. This option will not ensure users have access to Query Studio for Marketing Cloud, as it only affects how Query Studio connects to Marketing Cloud via API. Configuring the API Integration means that the admin can set up the API user credentials and permissions for Query Studio. However, this does not affect whether users can access Query Studio or not; they still need to be licensed by the admin within the installed package settings.

 Marketing Cloud authenticates if the user has login hours enabled on their profile when they log in through the user interface3. Login hours are a security feature that allows the admin to specify the time range when users can access Marketing Cloud. If a user tries to log in outside of their login hours, they will be denied access3. The other options are incorrect because:

• If the user is assigned a role in the parent business unit. This is not a factor for authentication, but rather for authorization. A role determines what permissions and access levels a user has within Marketing Cloud, but it does not affect their ability to log in through the user interface4.
• If the user is logging in from a whitelisted IP address. This is not a factor for authentication, but rather for verification. An IP address whitelist is a list of trusted IP addresses that can access Marketing Cloud without additional verification. If a user logs in from an IP address that is not on the whitelist, they will be asked to verify their identity via email or SMS5.
• If the user is an API User on their record. This is not a factor for authentication, but rather for integration. An API User is a user who can access Marketing Cloud via API calls from external applications or systems. This does not affect their ability to log in through the user interface.

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

For long term success of their Send Log data extension, NTO should consider the following three aspects:

• Apply an appropriately-scoped Data Retention period. A Data Retention period is a setting that determines how long records are kept in a data extension before they are deleted or archived. Applying an appropriate Data Retention period can help NTO manage their storage space and performance by removing old or unnecessary data from their Send Log data extension.
• Add custom fields not included in the Send Log Template. The Send Log Template is a predefined data extension template that contains a set of standard fields for logging send data. However, NTO can add custom fields to their Send Log data extension to capture additional information that is relevant to their business needs or reporting requirements.
• Log attribute data necessary for auditing communications. Attribute data is any data that is associated with a subscriber or a message, such as name, address, email type, or campaign name. Logging attribute data can help NTO audit their communications and track their performance by various criteria. The other option is incorrect because:
• Log all variable data captured in emails at send time. Variable data is any data that can change or vary depending on different factors, such as personalization strings, dynamic content, or AMPscript variables. Logging all variable data can result in excessive storage consumption and performance degradation for NTO’s Send Log data extension. NTO should only log the variable data that is essential for their reporting or analysis needs.

 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.

 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

Publication lists are used to allow subscribers to opt-down/out of specific types of communications instead of unsubscribing from all. This helps to retain subscribers and maintain their preferences1

To address the issue of employees not receiving emails because the messages are being blocked by spam filters, the Marketing Cloud admin should provide the IT team a list of relevant IP addresses to whitelist in their spam filter. Whitelisting is a process that allows NTO to specify which IP addresses are trusted and can bypass the spam filter. By providing the IT team a list of relevant IP addresses, such as the ones used by Marketing Cloud to send emails, the admin can ensure that the emails from NTO will not be blocked or marked as spam by the employees’ email servers. The other options are incorrect because:

• Import employee email addresses into All Subscribers with an “Active” status. This option will not address the issue, as it only affects the subscription status of the employees in Marketing Cloud, not in their email servers. Importing employee email addresses into All Subscribers with an “Active” status means that NTO can send emails to those employees from Marketing Cloud, but it does not guarantee that the emails will be delivered or received by the employees’ email servers.
• Ensure employees have opted in to the test email list or data extension. This option will not address the issue, as it only affects the consent of the employees to receive emails from NTO, not their email servers. Ensuring employees have opted in to the test email list or data extension means that NTO has permission to send emails to those employees, but it does not guarantee that the emails will be delivered or received by the employees’ email servers.
• Ask employees to use personal email addresses instead of corporate email addresses. This option will not address the issue, as it only shifts the problem from one email server to another, not solving it. Asking employees to use personal email addresses instead of corporate email addresses means that NTO will send emails to different email servers, but it does not guarantee that those email servers will not block or mark the emails as spam.

The admin should create separate business units for each of NTO’s brands when brand-specific private domains need to be leveraged when wrapping images and links in email campaigns. A private domain is a domain name that NTO owns and uses for their email sends, such as email.nto.com. A private domain can be used to wrap images and links in emails to improve deliverability and branding. However, a private domain can only be associated with one business unit in Marketing Cloud, so NTO needs to create separate business units for each brand that requires a different private domain2. The other options are incorrect because:

• NTO requires SSL certificate configurations for Content Builder and Portfolio images. This is not a reason to create separate business units for each brand, as SSL certificate configurations can be applied at the account level or the business unit level. SSL certificates are used to secure the connection between NTO’s web server and their subscribers’ browsers, and can be applied to Content Builder or Portfolio images to ensure they are delivered over HTTPS3.
• Multiple brand logos must be accommodated in an email header. This is not a reason to create separate business units for each brand, as multiple brand logos can be accommodated in an email header using dynamic content or AMPscript. Dynamic content or AMPscript are features that allow NTO to display different content in their emails based on subscriber attributes or data extension fields4.
• A new sender profile needs to be leveraged for sending transactional emails. This is not a reason to create separate business units for each brand, as a new sender profile can be created and leveraged within the same business unit. A sender profile is a configuration that defines the sender information for an email, such as the from name, from address, reply address, and sender classification5.

Separating regions into business units and applying subscriber filters is the best way to ensure distinct data integrity across the regions. Subscriber filters allow you to control which subscribers are visible in each business unit based on criteria such as location, language, or preference.

When “Send as Multipart MIME” is selected during the send process, an auto-generated text version will be sent with the HTML email and open and click activity will be tracked in either version. This option helps to ensure that subscribers can view the email regardless of their email client or device preferences

 Impression Tracking for Triggered Sends is the report that should be used. Impression Tracking for Triggered Sends is a feature that allows marketers to track how subscribers interact with content areas within triggered emails. Impression Tracking for Triggered Sends can be enabled for any content area that uses AMPscript or dynamic content blocks. The report shows metrics such as impressions, unique impressions, clicks, and click rate for each content area

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

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.

 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.

Three Filter Activities and three Send Activities to the filtered audiences are the steps that should be included in the customer’s automation. Filter Activities are used to segment a data extension based on specific criteria, such as the member’s renewal date. Send Activities are used to send an email to a data extension or a filtered audience.

To view the test emails that have been sent from Email Studio, the Marketing Cloud admin can go to My Tracking > Test Send Emails3. This page shows the details of each test email, such as the subject line, sender name, recipient email, and status3. The other options are not relevant for viewing test emails.

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

 To update their Marketing Cloud SFTP password, the admin should go to Company Settings in Setup. There, they can find the FTP Accounts section and click Edit on their SFTP account. They can then enter a new password and save it

To send a promotional email to one million subscribers, NTO should use a data extension as their data structure. A data extension is a table that stores subscriber data in Marketing Cloud. A data extension can store up to 30 million records per data extension and up to 100 million records per account2. A data extension can also support advanced segmentation, personalization, and reporting features for email sends

The Content Builder Settings under Setup allow the admin to create a default Header and Footer for emails. These settings apply to emails created in Content Builder only. The other settings do not have an option to create a default Header and Footer for emails.

Marketing Cloud Email Marketing Manager and Marketing Cloud Regional or Local Administrator are two roles, custom or standard, that could be assigned to this user to meet the requirement. Marketing Cloud Email Marketing Manager is a standard role that grants access to Email Studio and its features, such as creating and sending emails, managing subscribers, and tracking email performance. Marketing Cloud Regional or Local Administrator is a custom role that grants access to all business units within a specific region or location, such as North America

SQL Query Activities can reference Send Logs in combination with system data views and a business unit can support up to three Send Logs. These statements are correct about Send Logging, which is a feature that allows marketers to capture additional information about email sends that are not available in standard reports or data view

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.