Free Practice Questions for Salesforce Marketing-Cloud-Account-Engagement-Specialist Exam

Mailable Database usage is the number of prospects in an account that are opted in and can receive emails. It does not include prospects that are opted out, in the recycle bin, or have a hard bounce or do not email status. Therefore, the Mailable Database usage for the marketer with 4,000 total prospects, 3,000 of which are opted in, 500 of which are opted out, and 500 of which are in the recycle bin, is 3,000 (A). The other options (B, C, D) are incorrect because they either include prospects that are not mailable or exclude prospects that are mailable. References: Marketing Cloud Account Engagement - Salesforce.com

In Salesforce Pardot’s enhanced email experience, the process to use a created email content in an engagement program requires converting the email content into an email template.

Convert the email content record to an email template: This functionality allows marketers to leverage the rich content created in the email content record format and utilize it within the structured framework of an engagement program. The conversion process standardizes the email content into a template format, which can then be seamlessly integrated into various Pardot automation tools including engagement programs. This ensures that the aesthetic and functional integrity of the email content is maintained across different marketing campaigns and workflows.

Options such as selecting the engagement program directly from the email or activating the email for use in automation do not align with Pardot’s current capabilities regarding email integration in engagement programs, as they require the email to be in a template format to be used effectively.

 A CNAME or vanity alias is used to provide a seamless transition for your prospects when visiting pages and forms that you host on your site and Marketing Cloud Account Engagement hosted campaign elements such as landing pages, search results and individually tracked links sent in your emails. This is true because a CNAME allows you to use your own domain name instead of the default go.Marketing Cloud Account Engagement.com domain name, which enhances your branding and trustworthiness.

According to the Salesforce documentation, the marketer can accomplish the goal of creating different Marketing Cloud Account Engagement lists to correspond with the different stages of the buying cycle and automatically updating the prospect list membership based on the opportunity stage change in Salesforce by using a dynamic list. A dynamic list is a list of prospects that is updated automatically based on certain criteria, such as prospect field values, activities, or scores. A dynamic list can be used to segment prospects based on their opportunity stage in Salesforce, and to add or remove prospects from the list when the opportunity stage changes. For example, a dynamic list can be created for prospects whose opportunity stage is Negotiations, and another dynamic list can be created for prospects whose opportunity stage is Closed Won. When an opportunity moves from Negotiations to Closed Won in Salesforce, the prospect associated with that opportunity will be removed from the Negotiations list and added to the Closed Won list in Marketing Cloud Account Engagement. A completion action, a page action, or an automation rule are not the best tools to accomplish the goal of creating different Marketing Cloud Account Engagement lists to correspond with the different stages of the buying cycle and automatically updating the prospect list membership based on the opportunity stage change in Salesforce, as they are related to other aspects of automation, such as performing actions after a prospect completes a marketing element, visits a web page, or meets certain criteria, but not segmenting prospects based on their opportunity stage in Salesforce. References: Salesforce documentation

 The process to add a prospect who visits a pricing page to a list is to create a page action. A page action is a feature that allows you to track and act on the behavior of prospects who visit specific pages on your website, such as your pricing page, product page, or thank you page. You can use page actions to perform actions on the prospects who visit the page, such as adding them to a list, assigning them to a user, or changing their field values. You can also use page actions to customize the content or layout of the page based on the prospect’s attributes or behaviors3. To create a page action, you need to specify the URL of the page that you want to track, and the actions that you want to execute when a prospect visits the page. For example, you can create a page action that matches the URL of your pricing page, and adds the prospect to a list of pricing page visitors. 

Marketing Cloud Account Engagement syncs with Salesforce every 10 minutes. Marketing Cloud Account Engagement and Salesforce work together to keep data aligned between the two platforms. Some of the data that syncs bi-directionally are leads, contacts, and campaigns. Some of the data that syncs one-directionally from Salesforce to Marketing Cloud Account Engagement are accounts, opportunities, and tasks. Marketing Cloud Account Engagement syncs with Salesforce every 10 minutes by default, but you can also trigger a sync manually or by certain actions. For example, you can sync a prospect from their record in Marketing Cloud Account Engagement or Salesforce, or you can sync a group of prospects by using automation rules, segmentation rules, or imports. You can also sync a prospect by changing their Marketing Cloud Account Engagement campaign, assigned user, or email opt-out status. You can view the sync status and history on the prospect record in Marketing Cloud Account Engagement or Salesforce. For more details —> 18192021

According to the Salesforce documentation, the two Marketing Cloud Account Engagement form actions that would accomplish enabling bot protection on their forms are honeypot technique and reCaptcha. Bot protection is a feature that helps prevent automated bots from submitting forms and creating fake prospects. Honeypot technique is a method that uses a hidden field in the form that is not visible to human users, but can be detected by bots. If the hidden field is filled out, the form submission is rejected as a bot submission. reCaptcha is a service that uses a challenge-response test to verify that the form submitter is a human and not a bot. The user can enable either or both of these options in the form settings to add bot protection to their forms. Enabling HTTPS, or Hypertext Transfer Protocol Secure, is a method that encrypts the communication between the user’s browser and the web server, but it does not prevent bots from submitting forms. Dependent fields are fields that are displayed or hidden based on the value of another field, but they do not prevent bots from submitting forms either. References: Salesforce documentation

 For a Salesforce Opportunity to sync to Marketing Cloud Account Engagement, the Opportunity must have a Contact Role that is syncing to a prospect in Marketing Cloud Account Engagement. A Contact Role is a way of associating a Contact with an Opportunity, and specifying their role and level of influence in the sales process. Marketing Cloud Account Engagement uses the Contact Role to link the Opportunity to the corresponding prospect, and track their engagement and influence on the Opportunity4. References: 4: Opportunity Contact Roles

 If a new Lead record is created in Salesforce without an email address and the Salesforce connector is set to “automatically create prospects in Marketing Cloud Account Engagement”, no new prospect will be created in Marketing Cloud Account Engagement. This is because email address is a required field for creating a prospect in Marketing Cloud Account Engagement, and without it, the sync will fail. The Lead record will remain in Salesforce, but it will not have a corresponding prospect in Marketing Cloud Account Engagement1. References: Marketing Cloud Account Engagement Sync Behavior