Marketing-Cloud-Administrator Questions and Answers

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

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.

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 monitor whether all records were added to the target data structure each day, NTO should use the Notification Settings within the Import File Activity. The Notification Settings allow NTO to specify an email address or a data extension to receive notifications about the status and results of the import. The notifications include information such as the number of records processed, added, updated, skipped, or failed. This way, NTO can track and verify the import process and identify any issues or errors. The other options are incorrect because:

• External Key within the Import File Activity. The External Key is a unique identifier for the Import File Activity that can be used for API calls or SQL queries. However, it does not provide any information about the status and results of the import.
• Run Completion within the File Drop Automation. The Run Completion is a summary of the execution of the File Drop Automation that shows the start time, end time, duration, and status. However, it does not provide any information about the status and results of the import.
• Runtime Error within the File Drop Automation. The Runtime Error is a message that indicates an error occurred during the execution of the File Drop Automation that prevented it from completing successfully. However, it does not provide any information about the status and results of the import.

To assist in reducing threats from malicious API attacks, NTO should enable IP Whitelisting3. IP Whitelisting is a security feature that allows NTO to specify a list of trusted IP addresses that can access Marketing Cloud via API. Any API requests from IP addresses that are not on the whitelist will be rejected. This way, NTO can prevent unauthorized or malicious API access to their Marketing Cloud account. The other options are incorrect because:

• Field Level Encryption. This is a security feature that encrypts specific fields in data extensions using encryption keys managed by NTO. However, this feature does not prevent malicious API attacks; it only protects data at rest in Marketing Cloud from unauthorized access.
• Advanced Audit Trail. This is a security feature that tracks and logs user activity and changes within Marketing Cloud. However, this feature does not prevent malicious API attacks; it only provides visibility and accountability for user actions in Marketing Cloud.
• Single Sign on Authentication. This is a security feature that allows users to log in to Marketing Cloud using their credentials from an external identity provider. However, this feature does not prevent malicious API attacks; it only simplifies and standardizes user authentication for Marketing Cloud.

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.

IP Allowlist is the feature that NTO should enable to assist in reducing threats from malicious API attacks. IP Allowlist is a feature that restricts API access to Marketing Cloud from a specific set of IP addresses. By creating an IP Allowlist, NTO can ensure that only authorized users or applications can access their Marketing Cloud account via API

Removing nonessential data for marketing purposes, identifying and assigning appropriate keys to tie records together, and normalizing data and fields to prevent redundancy are the data preparations that should be made to retain high data quality in the new model. These steps will help reduce data storage costs, improve data integrity, and enable cross-channel personalization

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.

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.

The two prerequisites for configuring Social Studio to manage NTO’s social media accounts are:

• Bitly URL Shortener. This is a service that allows NTO to shorten and customize the URLs that they share on their social media posts. Bitly URL Shortener can also provide analytics and insights on the performance of the URLs, such as clicks, impressions, and conversions2. NTO needs to have a Bitly account and connect it to Social Studio before they can use Bitly URL Shortener for their social media posts.
• Login details for each social media account. These are the credentials that NTO needs to access and manage their social media accounts, such as Facebook, Twitter, Instagram, or YouTube. NTO needs to have login details for each social media account and connect them to Social Studio before they can use Social Studio to create and publish social media posts. The other options are incorrect because:
• Facebook ad manager. This is a tool that allows NTO to create and manage advertising campaigns on Facebook and its partner platforms, such as Instagram or Messenger. Facebook ad manager can also provide analytics and insights on the performance of the campaigns, such as reach, impressions, and conversions3. However, this is not a prerequisite for configuring Social Studio to manage NTO’s social media accounts; it is an optional feature that NTO can use if they want to run paid ads on Facebook or its partner platforms.
• Google URL shortener. This is a service that allows NTO to shorten and customize the URLs that they share on their social media posts. Google URL shortener can also provide analytics and insights on the performance of the URLs, such as clicks, impressions, and conversions4. However, this is not a prerequisite for configuring Social Studio to manage NTO’s social media accounts; it is an alternative service that NTO can use instead of Bitly URL Shortener.

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

Purchasing a new private domain for use in CloudPages allows the admin to use a customized domain name for CloudPages, such as de-special.ntomarketing.com. This domain can be different from the SAP domain, which is used for email branding and deliverability. The other options are not feasible or correct.

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

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.

 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.

 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

Data Filter, Template-based emails, and Automation Studio are the components that the customer’s solution should include. Data Filter is used to segment a data extension based on specific criteria, such as the customer’s expiration date. Template-based emails are used to create emails with predefined layouts and content blocks that can be easily customized by a general marketing user. Automation Studio is used to automate the email sends based on a schedule or a trigger

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

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.

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

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.

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 achieve the setup of sharing the same SFTP directory across each of their Marketing Cloud accounts, NTO should copy the parent SFTP user into each child business unit. This will allow each business unit to access the same SFTP directory as the parent business unit and share files among them. The other options are incorrect because:

• Child business unit SFTP user should be created. This will create a separate SFTP user and directory for each child business unit, which will not allow them to share files with the parent business unit or other child business units.
• Each business unit should have multiple SFTP users. This will create unnecessary complexity and confusion for NTO, as they will have to manage multiple SFTP users and directories for each business unit. This will also not allow them to share files among different business units easily.
• All child business units should have an individual SFTP user. This is similar to the first option, as it will create a separate SFTP user and directory for each child business unit, which will not allow them to share files with the parent business unit or other child business units.

 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.

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.

 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.

 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.

The Sender Authentication Package (SAP) allows the image URLs to be wrapped with the appropriate brand URL, which enhances the branding and deliverability of the emails. The SAP does not affect the profile center branding, the click domain, or the IP warming.

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

Removing Marketing Cloud Viewer role from the user would allow the analyst to import contact lists. The Marketing Cloud Viewer role is a read-only role that prevents users from performing any actions on data or content. The Marketing Cloud Channel Manager role already grants the user permission to import contact lists. The other options would not solve the problem or are unnecessary.

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.

 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.

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.

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.

 Event registration and venue details are the two data sources that must be incorporated inside Contact Builder. Event registration contains the event ID, event name, event type, and venue ID, which are needed for the decision split and the dynamic content in the email. Venue details contain the venue ID, venue name, and venue address, which are needed for populating the venue details in the email with AMPscript. Customer data and payment details are not essential for this scenario and can be excluded from Contact Builder.

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

Data extensions are necessary for Contact Builder is the statement that differentiates the use of data extensions over lists. Data extensions are tables that store subscriber data and can be linked to other data extensions or data sources via Contact Builder. Contact Builder is a tool that allows marketers to create a unified view of their contacts and manage their relationships with other data entities. Lists are collections of subscribers that cannot be linked to other data sources via Contact Builder.

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.

 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

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.

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.