Salesforce Certified Marketing Cloud Account Engagement Specialist Practice Test - Questions Answers, Page 4

The list email or email template report deliverability metric that could indicate an unverified sending domain is hard bounces. Hard bounces are permanent delivery failures, such as invalid email addresses or blocked domains. Hard bounces can negatively affect the sender reputation and the email deliverability. One of the possible causes of hard bounces is an unverified sending domain, which means that the email domain used to send emails from Marketing Cloud Account Engagement is not authenticated and verified by Marketing Cloud Account Engagement. An unverified sending domain can result in the email servers rejecting the emails as spam or phishing attempts. To avoid hard bounces and improve email deliverability, the marketer should verify the sending domain in Marketing Cloud Account Engagement by following the steps in the reference link. Forward count, skimmed percentage, and total queued are not deliverability metrics that could indicate an unverified sending domain. Forward count measures how many recipients forwarded the email to another person. Skimmed percentage measures how many recipients opened the email for less than two seconds. Total queued measures how many emails were waiting to be sent from Marketing Cloud Account Engagement. These metrics are not related to the email domain verification or the email delivery failures.ReferenceVerify Your Sending Domain

The feature that the Marketing Cloud Account Engagement administrator should use to gather a prospect's company name and job title, but only once they have captured the prospect's first name, last name, and email address in a previous form submission, is progressive profiling. Progressive profiling is a feature that allows the administrator to display different fields on a form based on the information that the prospect has already provided. This way, the administrator can avoid asking the same questions repeatedly and collect more information gradually. Progressive profiling can be enabled on a form by selecting the option ''Always display even if previously completed'' for the fields that are required, such as first name, last name, and email address, and selecting the option ''Only display if progressive profiling is enabled and the field is blank'' for the fields that are optional, such as company name and job title. This way, the form will only show the optional fields once the required fields are filled out. Always display even if previously completed, reCaptcha, and dependent fields are not features that can achieve the same goal as progressive profiling. Always display even if previously completed is an option that can be used to enable progressive profiling, but it is not a feature by itself. reCaptcha is a feature that can be used to prevent spam submissions on a form, but it does not affect the fields that are displayed on the form. Dependent fields are fields that are displayed or hidden based on the value of another field, but they do not depend on whether the prospect has already provided the information or not.ReferenceProgressive Profiling

What is needed for a page action to trigger for a prospect visiting a high value web page is adding a page action and Marketing Cloud Account Engagement tracking code on the page. A page action is a Marketing Cloud Account Engagement feature that allows the administrator to perform certain actions when a prospect views a specific page on the website, such as increasing the score, changing the field value, adding to a list, etc. A page action can be created by entering the URL of the page and selecting the actions to be performed. A Marketing Cloud Account Engagement tracking code is a snippet of code that can be added to the website to track the page views and activities of visitors and prospects on the website. The Marketing Cloud Account Engagement tracking code is required for the page action to work, as it identifies the prospects who visit the page and executes the actions on them. Creating an automation rule, adding a completion action, or adding a page action on the form are not what is needed for a page action to trigger for a prospect visiting a high value web page. An automation rule is a rule that runs in the background and matches prospects based on certain criteria and performs certain actions. An automation rule can use page views as a criterion, but it is not the same as a page action, as it does not depend on a specific URL. A completion action is an action that is triggered when a prospect completes a specific activity, such as submitting a form, clicking a link, or opening an email. A completion action is not related to a page view, unless the page contains a form or a link. A page action on the form is not possible, as a page action can only be added on a page, not on a form.Reference[Page Actions] [Marketing Cloud Account Engagement Tracking Code]

The expected behavior if an automation rule is not set to repeat is that the prospect matches the criteria once and the action runs once. An automation rule is a rule that runs in the background and matches prospects based on certain criteria and performs certain actions. An automation rule can be set to repeat or not repeat, depending on whether the administrator wants the rule to run multiple times or only once on the same prospect. If the automation rule is not set to repeat, it means that the rule will only run once on each prospect who matches the criteria, and it will not run again even if the prospect matches the criteria again in the future. The other options are not the expected behavior if an automation rule is not set to repeat. The prospect cannot match the criteria multiple times and the action runs each time, as this would require the rule to be set to repeat. The action cannot run only once per day on the prospect, as this would require the rule to have a daily frequency limit. The prospect cannot match the criteria once, but the action runs multiple times, as this would require the rule to have multiple actions or a recurring action.Reference[Automation Rules Overview]

According to theSalesforce documentation, the default scoring model in Marketing Cloud Account Engagement assigns points to prospects based on their activities, such as clicking a link in an email, submitting a form, or visiting a landing page. These activities indicate the level of interest and engagement of the prospects, and help prioritize them for sales follow-up. Converting a lead to a contact or sending an email to the assigned user are not activities that automatically increase the prospect's score, unless they are customized in the scoring rules.

Reference:Salesforce documentation

According to theSalesforce documentation, when a prospect is added to a suppression list in an engagement studio program, the prospect is paused from receiving any further emails or actions from the program. However, the prospect's progress in the program is not reset or removed. If the prospect is removed from the suppression list, the prospect will resume the program from where they left off, which is the next step after the last completed step. In this case, the prospect will continue on the engagement studio program onto step 6.

Reference:Salesforce documentation

According to theSalesforce documentation, when a prospect is permanently deleted from Marketing Cloud Account Engagement, all the associated data and activities are also deleted and cannot be restored. However, if the prospect fills out a new Marketing Cloud Account Engagement form and submits their information, a new prospect record will be created with the same email address as the deleted one, but without any of the previous data and activities. The new prospect will have a new unique ID and will not be linked to the deleted one in any way.

Reference:Salesforce documentation

According to theSalesforce documentation, in order to sync a Marketing Cloud Account Engagement prospect field with both a lead and a contact field in Salesforce, the lead and contact fields must have the same API name, and the Marketing Cloud Account Engagement field must be mapped to the Salesforce field. The API name is the unique identifier for the field that is used by the system to sync the data. The field mapping is the configuration that tells Marketing Cloud Account Engagement which Salesforce field to sync with. The Salesforce field label and the Marketing Cloud Account Engagement field type are not relevant for the field sync, as long as they are compatible.

Reference:Salesforce documentation

According to the [Salesforce documentation], when 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 record 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 lead record cannot be synced or matched with a prospect record. A visitor record is created only when a person visits a tracked web page, not when a lead record is created in Salesforce. A new account will not be created either, as accounts are synced from Salesforce to Marketing Cloud Account Engagement based on the account ID of the associated lead or contact record. A new prospect record will not be created, as explained above.

Reference: [Salesforce documentation]