Marketing-Cloud-Administrator Sample Questions Answers

 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

The Setup Assistant guides the Marketing Cloud admin through creating users and assigning roles, classifying sends and defining parameters, and building the data structure for storing audience information. These are essential tasks for setting up Marketing Cloud. The Setup Assistant does not cover creating a SMS message or importing data using the Data Loader.

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

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

 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.

 Microsite with Smart Capture to store entrants on a data extension is the correct component for capturing the contact information of the booth visitors. Smart Capture allows creating a form that can validate the entries and prevent duplicates. Data Extension with double opt-in status defined is the correct component for storing the entrants and their opt-in status. Double opt-in is a best practice for email marketing and ensures that the entrants have given their consent to receive the monthly newsletter.

 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

Data extensions allow storing multiple values for an attribute for each subscriber. Profile attributes only store one value per attribute per subscriber.

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.

 Burst sending is the functionality that would get messages out the door faster. Burst sending allows you to send large volumes of email in a short period of time by bypassing some of the standard send processes. Burst sending is ideal for time-sensitive or urgent messages that need to reach a large audience quickly

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.

AMPscript conditional against the Gender field is the best method to ensure content is displayed properly within the email. It allows creating dynamic content based on the value of the Gender field in the sendable data extension. Dynamic Content Wizard is not suitable for this scenario because it requires creating content areas for each variation of content, which can be cumbersome for a customer with limited technical resources. AMPscript lookupRows functions and A/B Test content type are not relevant for this scenario.

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

To assign users to the business units, the admin should search for the individual user, select their name, and click Manage Business Units. This will allow the admin to select which business units the user can access and what role they have in each business unit. The Edit Business Units option is not available for users

Parameter Manager is the functionality that would allow this. 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

Multi-Org accounts do not support the standard profile and preference centers for the business units4. Instead, each business unit must create custom profile and preference centers using CloudPages or Microsites4. The other options are incorrect because branding is not inherited from the default business unit setup4, profile/preference centers are not automatically created for each business unit4, and profile/preference centers are not configured in the Salesforce CRM settings4.

 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.

Segment by domain to limit number of sends to each email provider is the option for segmentation that aligns with the IP Warming process. IP Warming is the process of gradually increasing email volume from a new or unused IP address to build trust and credibility with Internet Service Providers (ISPs). Segmenting by domain means dividing the email list into smaller groups based on the email domain, such as gmail.com or yahoo.com. By segmenting by domain, marketers can limit the number of sends to each email provider and avoid being flagged as spam or blocked by the ISPs.

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

 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.

Automation Studio Tracking Extract is what the admin should use to get granular bounce data in bulk in a pre-defined format. Tracking Extract is a type of data extract activity that allows marketers to export tracking data from Marketing Cloud, such as bounces, clicks, opens, unsubscribes, and more. Tracking Extract can be configured to include specific fields and filters, such as date range, send type, or job ID. Tracking Extract can be run manually or scheduled via Automation Studio. The output file is in a CSV format that can be downloaded or transferred to an external location

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.

To ensure Individual Email Results are pushed back into Sales Cloud for a particular send, the admin should confirm that the data extension is located in the Salesforce Data Extensions folder. The Salesforce Data Extensions folder is a special folder that contains data extensions that are integrated with Salesforce CRM via Marketing Cloud Connect. Only data extensions in this folder can be used for sending emails with Individual Email Results tracking enabled. The other options are incorrect because:

• The send relationship links Subscriber Key to Subscribers on Email Address. This is a setting that defines how subscribers are identified and matched between a sendable data extension and All Subscribers. However, this setting does not affect whether Individual Email Results are pushed back into Sales Cloud; it only affects how email addresses and subscription statuses are updated in Marketing Cloud.
• The data extension is located in the Synchronized Data Extensions folder. The Synchronized Data Extensions folder is a special folder that contains data extensions that are synchronized from Salesforce CRM via Marketing Cloud Connect. However, these data extensions cannot be used for sending emails directly; they can only be used as sources for filtered or query-based data extensions.
• The triggered Send Data Extension data extension template was used. This is a predefined data extension template that contains a set of standard fields for logging triggered send data. However, this template does not affect whether Individual Email Results are pushed back into Sales Cloud; it only affects what information is stored in Marketing Cloud.

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.

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 search for a Salesforce contact in All Subscribers, the admin should use the 18-digit contact ID as the subscriber key. This is because Marketing Cloud Connect uses the 18-digit contact ID as the subscriber key for contacts synchronized from Salesforce. The email address is not a reliable identifier as it can change or be duplicated

Update the Import definition to include a notification email address is how the admin could receive a file of the bad data rows to confirm this theory. Import definition is a type of activity that allows marketers to import data from a file into a data extension or a list in Marketing Cloud. Import definition can be configured to include a notification email address that will receive an email with a link to download a file of the bad data rows after the import is completed. The file will contain the rows that failed to import and the reason for the failure

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.

 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

 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

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.

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

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.

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.

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.

 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

Subscriber Key is the component that should be discussed with the customer to allow for this use case. Subscriber Key is a unique identifier for each subscriber in Marketing Cloud that can be different from the email address. Subscriber Key allows for multiple records to share the same email address but have different subscriber attributes and preferences

 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

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.

To ensure sensitive information needed for email sends is not imported and stored in Marketing Cloud, NTO should implement Tokenized Sending4. Tokenized Sending is a feature that allows NTO to send emails using encrypted tokens instead of actual email addresses. The tokens are generated by an external system and stored in a secure database outside of Marketing Cloud. When NTO sends an email, Marketing Cloud sends the token to the external system, which decrypts it and returns the actual email address. This way, NTO can avoid importing and storing sensitive information in Marketing Cloud. The other options are incorrect because:

• Transparent Data Encryption. This is a feature that encrypts data at rest in Marketing Cloud using encryption keys managed by Salesforce. However, this feature does not prevent NTO from importing and storing sensitive information in Marketing Cloud; it only protects it from unauthorized access5.
• Key Management. This is a feature that allows NTO to manage their own encryption keys for data at rest in Marketing Cloud using an external key management system. However, this feature does not prevent NTO from importing and storing sensitive information in Marketing Cloud; it only gives them more control over their encryption keys.
• 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 importing and storing sensitive information in Marketing Cloud; it only encrypts it within data extensions.