Salesforce Updated Marketing-Cloud-Account-Engagement-Specialist Exam Questions and Answers by maksymilian

There are three ways the Marketing Manager can create a new prospect in Marketing Cloud Account Engagement. They are:

• Click the “Send to Account Engagement” button on a Salesforce Lead. This option allows the Marketing Manager to send a one-to-one email to a lead in Salesforce using an Account Engagement email template. If the lead does not already exist as a prospect in Account Engagement, it will be created automatically and synced with Salesforce1
• Manually add a prospect in Marketing Cloud Account Engagement. This option allows the Marketing Manager to create a new prospect record in Account Engagement by entering the prospect’s email address and other information. The prospect can then be added to lists, campaigns, or engagement programs2
• Import a .CSV file with the prospect’s email address. This option allows the Marketing Manager to import a list of prospects from a .CSV file into Account Engagement. The file must contain the prospect’s email address as the first column, and can also include other fields. The imported prospects can then be assigned, tagged, or added to lists or campaigns

For a Pardot form used on a computer tablet in a setting like a conference, the Kiosk/Data Entry Mode is an ideal feature to enable. This mode is specifically designed for public or shared use scenarios, where multiple individuals will be filling out the form in succession. When this mode is enabled, the form automatically resets after each submission, clearing all previously entered data and preparing the form for the next user. This ensures that each participant sees a fresh form, preventing the accidental sharing of personal information between users and facilitating a smooth data entry process in high-traffic environments.

The scenario in which a prospect would be able to receive the emails in the program is when the prospect is removed from the suppression list. A suppression list is a list that prevents prospects from receiving emails from an engagement studio program, even if they are in the recipient list. A recipient list is a list that defines the prospects who are eligible to receive emails from the program. If a prospect is in both the recipient list and the suppression list, they will not receive any emails from the program. Removing the prospect from the suppression list will allow them to receive the emails, as long as they are still in the recipient list and not opted out. Removing the prospect from the recipient list, marking the prospect as opted out, or removing the prospect from both the suppression list and the recipient list will not allow them to receive the emails from the program. References [Engagement Studio Suppression Lists]

According to the Salesforce documentation, the two form field options that should be enabled to make the “Comments” field visible and empty every time a prospect returns to one of the forms are: B) Always display even if previously completed, and C) Maintain the initial value upon subsequent form submissions. The Always display even if previously completed option ensures that the field is not hidden or pre-filled with the previous value when the prospect revisits the form. The Maintain the initial value upon subsequent form submissions option ensures that the field is not overwritten with the new value when the prospect submits the form again. These two options combined will make the field appear as visible and empty every time the prospect returns to the form. The Do not prefill option will prevent the field from being pre-filled with the prospect’s information from Marketing Cloud Account Engagement or Salesforce, but it will not prevent the field from being pre-filled with the previous value from the same form. The Display other fields in this form based on the value of this field option will create a dependent field that will show or hide other fields based on the value of the “Comments” field, but it will not affect the visibility or emptiness of the “Comments” field itself. References: Salesforce documentation