Salesforce Marketing-Cloud-Administrator Dumps

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

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

 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.

 Creating a single Attribute Group that links Customers to Contacts, Orders to Customers, and Products to Orders is the best way to facilitate this within Contact Builder. This way, NTO can create a single data model that connects all the relevant data extensions and allows accessing customer data across different attributes. Creating three distinct Attribute Groups that link each data extension directly to Contacts is not correct, as it does not establish the relationships between Customers, Orders, and Products. Creating three distinct Attribute Groups that link Customers to Contacts, Orders to Customers, and Products to Orders is not correct, as it creates unnecessary duplication of data models. Creating a single Attribute Group that links Contacts to Customers, Orders to Products, and Products to Customers is not correct, as it does not reflect the logical hierarchy of the data extensions.

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.

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.

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

 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.

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.

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.

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 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 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 best way to prevent duplicate records in Marketing Cloud is to strategically control the Contact Key values and tie records together across channels using this key. The Contact Key is a unique identifier for each contact in Marketing Cloud, and it can be set by the admin or automatically generated by Marketing Cloud. If the same Contact Key is used for a contact in both email and mobile push channels, then the contact will be unified and not duplicated.

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.

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

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.

The Content Split activity should be used for multivariate content testing within Journey Builder. This activity allows the journey to send different versions of email content to different audience segments and measure their performance based on open or click rates. The other activities are not suitable for multivariate content testing.

 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.

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

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

 Email attachments is the Marketing Cloud product that NTO should purchase as a solution. Email attachments allows you to attach files such as PDFs or CSVs to your email messages. The files are stored securely in Marketing Cloud and are not publicly accessible. Distributed sending is not a suitable solution because it allows franchisees to send their own emails using NTO’s content, not receive emails from NTO. Content syndication and Analytics Builder are not relevant for this scenario.

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.

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.

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.

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

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

Create separate folders and add permissions is how they should accomplish this. Folders are used to organize data extensions and other assets in Marketing Cloud. Permissions can be applied to folders to control which users can view or update the data extensions or assets within them. By creating separate folders for B2C and B2B campaigns and adding permissions accordingly, they can restrict access to data extensions based on user roles

QUESTIONNO: 95

Northern Trail Outfitters wants to know how customers are engaging with marketing communications they have sent over the last year. What action should be taken to populate the Einstein Engagement Scoring Dashboard?

A. Select one of the Predictive Algorithms then click Deploy

B. Click Deploy and results are available immediately

C. Select the channels (Emails, Push, SMS) to report on then click Activate

D. Click Activate and wait for an email notification

Answer: D

Click Activate and wait for an email notification is the action that should be taken to populate the Einstein Engagement Scoring Dashboard. Einstein Engagement Scoring is a feature that uses artificial intelligence to score subscribers based on their likelihood to open, click, or unsubscribe from emails. To activate this feature, users need to click the Activate button in the dashboard and wait for an email notification that confirms the activation and provides a link to view the scores.

Data Management is where in Setup they could accomplish this task. Data Management is a section in Setup that allows marketers to manage their data sources, imports, exports, and transfers in Marketing Cloud. Data Management includes a subsection called FTP Accounts, where marketers can create and manage their SFTP users and passwords for secure file transfers.

 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.

The out-of-the-box Subscription center can display Publication Lists and Lists as options for subscribers to opt in or out of. Data Extensions and Groups are not supported by the default Subscription center.

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.

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

A triggered message is a type of email that is sent automatically based on a subscriber’s behavior or a predefined event. This reduces the manual workload on the team and improves the customer experience by sending timely and relevant messages

To comply with CAN-SPAM regulations for each commercial send, the admin should ensure that their emails contain a preference center link and a physical mailing address1. A preference center link is a link that allows subscribers to manage their subscription preferences and opt out of receiving future emails from NTO. A physical mailing address is an address that identifies NTO’s location and contact information. These elements are required by CAN-SPAM for any email that promotes a commercial product or service1. The other options are incorrect because:

• Business name and a link to the business website. These elements are not required by CAN-SPAM for each commercial send, although they may be useful for branding and marketing purposes. CAN-SPAM only requires that NTO clearly identifies themselves as the sender of the email and provides a valid reply-to address1.
• Business name and physical mailing address. These elements are partially correct, as CAN-SPAM requires NTO to include their business name and physical mailing address in each commercial send1. However, they are not sufficient, as CAN-SPAM also requires NTO to include a preference center link or another easy way for subscribers to opt out of receiving future emails1.
• Preference center link and a link to the business website. These elements are partially correct, as CAN-SPAM requires NTO to include a preference center link or another easy way for subscribers to opt out of receiving future emails in each commercial send1. However, they are not sufficient, as CAN-SPAM also requires NTO to include their physical mailing address in each commercial send1.

One-to-One Relationship is the type of relationship that should be used to link demographic information to its contact model in Contact Builder. This type of relationship indicates that each record in the source data extension matches one and only one record in the target data extension based on a common attribute

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

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

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

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

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 use Sales Cloud data in their queries, the admin should use Synchronized Data Sources. This feature allows Marketing Cloud to automatically import and update data from Sales Cloud objects and fields. The data is stored in data extensions that can be queried using SQL.

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.

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

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

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.

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