Free and Premium Salesforce Marketing-Cloud-Administrator Dumps Questions Answers

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

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.

 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

 To clear inactive data stored in data extensions after 12 months, NTO should apply a row-based retention to each data extension as it is created, set to 12 months. This will delete any records that have not been modified in the last 12 months. Row-based retention can be applied to individual data extensions or data extension templates

 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

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

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

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.

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

 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.

 The correct answer is C because File Drop Automation can be used to trigger an automation when a file is dropped on the SFTP, and Import File Activity and SQL Query Activities can be used to import and separate the data into different data extensions. A is incorrect because Scheduled Automation cannot check if the file is present on time. B is incorrect because Scheduled Automation cannot trigger an alert if the file is not present. D is incorrect because Filter Activity cannot separate the data into different data extensions.

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.

To automatically unsubscribe customers who respond to marketing emails asking to be removed from the mailing list, the admin should take two steps:

• Ensure a Custom response is enabled for Automated Response in Reply Mail Management. This will allow Marketing Cloud to process replies that contain keywords such as unsubscribe, remove, or opt out and update the subscriber status accordingly.
• Verify Reply Mail Management has been enabled in the account. This will allow Marketing Cloud to handle replies to marketing emails and route them to a designated email address or domain.

Publication lists are the feature that should be utilized to make this happen. Publication lists are used to manage subscribers’ preferences for different types of communications, such as newsletters, promotions, or alerts. The built-in subscription center allows subscribers to opt-in or opt-out of publication lists, as well as the master list

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.

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.

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

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

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.

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

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

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

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

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

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

 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.

 The security setting ‘Enable Username and Password for Web Services’ allows users to access the API with their Marketing Cloud username and password. If this setting is deselected, users will need to use an API user or an installed package to access the API

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

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.

 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.

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

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

 The Marketing Cloud admin should consider that building desirable sending history and data will be variable based on list size and engagement when sending from the new IP address. A new IP address has no reputation with ISPs and needs to be warmed up gradually by sending emails to engaged and active subscribers. The send volume and frequency should be adjusted according to the list size and engagement level of NTO’s subscribers to avoid being marked as spam or blocked by ISPs. The other options are incorrect because:

• The IP address is on reserve, is already in use, and has an email sending history. This describes an existing IP address, not a new one. An existing IP address already has a reputation with ISPs and does not need to be warmed up.
• Sending in large volumes will alert ISPs the new IP Address is now in use. This is not a consideration, but rather a mistake. Sending in large volumes from a new IP address will raise red flags with ISPs and may result in poor deliverability or blacklisting.
• Migration of larger marketing campaigns is necessary prior to bringing on smaller, triggered campaigns. This is not a consideration, but rather the opposite of what should be done. Migration of smaller, triggered campaigns should be done first before bringing on larger marketing campaigns, as this will help build trust and reputation with ISPs.

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.

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

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

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

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.

 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.

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.

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.

When a subscriber clicks a link in an email, their status is changed from Bounced to Active, and their bounce count is reset to zero. This indicates that the subscriber’s email address is valid and reachable

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.

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.

AMPscript is the skill set that the customer team needs to possess in order for this solution to be viable. AMPscript is a scripting language that allows marketers to create personalized and dynamic content for emails, landing pages, mobile messages, and more. AMPscript can be used to retrieve data from data extensions, track click activity, populate content areas, and apply conditional logic based on regional market or other attributes.