According to the  Marketing Cloud Account Engagement Email Basics , there are three mandatory components for an email to be saved in Marketing Cloud Account Engagement: a text version, a sender, and an unsubscribe link. A text version is required for accessibility and deliverability reasons, as some email clients or recipients may not support HTML emails. A sender is required to identify the source of the email and comply with the CAN-SPAM Act. An unsubscribe link is required to allow recipients to opt out of future emails and comply with the GDPR and other privacy regula tions.  Variable tags, dynamic content, and social posts are optional components that can enhance the personalization and interactivity of the email, but they are not required for saving the email draft. 

The administrator should go to Admin-Domain Management to check if the Email Sending Domains are set up properly after updating the DNS. Email Sending Domains are domains that you can use to send emails from Marketing Cloud Account Engagement, and they require verification and authentication to ensure that your emails are delivered and not marked as spam. To verify and authenticate your Email Sending Domains, you need to update the DNS records of your domain with the values provided by Marketing Cloud Account Engagement.  After updating the DNS, you can go to Admin-Domain Management and click the Verify Now but ton to check if your Email Sending Domains are verified and authenticated

 You can send an automated email to a prospect after they fill out a form using either an automation rule or a completion action. An automation rule is a criteria-based action that is triggered when a prospect matches the rule. You can use an automation rule to send an email to prospects who fill out a specific form or any form. A completion action is a task that is performed after a prospect successfully completes a marketing element. You can use a completion action to send an email to prospects who fill o ut a particular form. You cannot use a segmentation rule to send an email, since segmentation rules are used to segment prospects into lists or update their field values. References: [Automation Rules],  Completion Actions , [Segmentation Rules]

When a user creates and resumes a new automation rule, the rule will continuously look for prospects who match the criteria (B) and evaluate their entire prospect database for matches ©. These are the characteristics of automation rules in Account Engagement, which are different from segmentation rules that run only once. The rule will not run once and must be re-run for prospects to match again (A), nor will it unmatch prospects that no longer match the criteria (D). Unmatching prospects is only possible w ith dynamic lists, not automation rules. References:  Using Account Engagement Automation Rules vs. Salesforce Flows

It is not possible to create a dynamic list of all prospects who have accessed a certain file in Marketing Cloud Account Engagement. Dynamic lists are based on criteria that match prospect fields, not prospect activities. Therefore, you cannot use a dynamic list to segment prospects based on whether they have downloaded a file, watched a video, or visited a page. Option A is not correct because field value mapping has nothing to do with dynamic lists or file access. Option C is not correct because match typ e is irrelevant for this question, as there is no valid criterion for file access. Option D is not correct for the same reason as option C. References:  Marketing Cloud Account Engagement Dynamic Lists for Faster Segmentation (+ 10 Examples) ,  Create a Dynamic List - Salesforce

According to the  Salesforce documentation , a prospect’s score can be changed through automation rules, scoring model changes, or completion actions. A prospect’s score is a numerical value that indicates the level of interest and engagement of a prospect, based on their activities, such as opening an email, clicking a link, or submitting a form. A prospect’s score can be changed by using different methods, such as:

Automation rules: An automation rule is an automation tool that can be used to update a prospect’s score when the prospect meets certain criteria, such as prospect field values, activities, or scores. For example, an automation rule can be created to increase a prospect’s score by 10 points when the prospect visits a specific web page.

Scoring model changes: A scoring model is a feature that allows users to customize the scoring rules for different types of activities, such as email opens, form submissions, or custom redirects. A scoring model can be changed by editing the default scoring model in Marketing Cloud Account Engagement, or by creating a custom scoring model for a specific group of prospects. For example, a scoring model can be changed to assign more points to an email open, or to create a different scoring model for prospects from a certain industry.

Completion actions: A completion action is an automation tool that can be used to adjust a prospect’s score after the prospect successfully completes a marketing element, such as submitting a form, clicking a link, or visiting a web page. A completion action can be used to increase or decrease a prospect’s score by a specific amount, or to reset a prospect’s score to zero. For example, a completion action can be created to decrease a prospect’s score by 5 points when the prospect unsubscribes from an email.

The only required field for a record in Salesforce to be synced or created as a prospect record in Marketing Cloud Account Engagement is the email address. Marketing Cloud Account Engagement uses the email address as the unique identifier for prospects, so it is mandatory for any record to sync between the two platforms. Other fields, such as name, company, or phone, are optional and can be mapped between Marketing Cloud Account Engagement and Salesforce, but they are not required for the sync to happen. Fo r more details — >   1 2 3

 According to the  Salesforce documentation , the issue of none of the lead’s Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce can be addressed by making sure that the administrator has mapped the lead fields to the contact fields in Salesforce. A field mapping is a feature that allows users to sync the data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A field mapping can be configured by the administrator in the connector settings, and it can be customized for different objects, such as leads, contacts, or accounts. When a lead is converted to a contact in Salesforce, the Marketing Cloud Account Engagement information (score/grade) should transfer over to the contact record, as long as the lead fields and the contact fields are mapped correctly in the connector settings. If the fields are not mapped correctly, the Marketing Cloud Account Engagement information (score/grade) will not transfer ov er, and the contact record will not reflect the Marketing Cloud Account Engagement data. Therefore, the administrator needs to make sure that the lead fields and the contact fields are mapped correctly in the connector settings, and that the sync between Marketing Cloud Account Engagement and Salesforce is working properly. Marketing Cloud Account Engagement only showing this information on the lead record, this information showing on the account record and not the contact, or the administrator needing to c reate lookup fields on the contact to see this from the lead are not the correct ways to address the issue of none of the lead’s Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce, as they are either inaccurate, irrelevant, or unnecessary options for the field mapping or the data sync. References:  Salesforce documentation

According to the  Salesforce documentation , the feature in Salesforce that can be enabled to show landing page engagement data on a Salesforce Campaign page layout is Engagement History. Engagement History is a feature that allows users to view and report on how prospects interact with Marketing Cloud Account Engagement marketing assets, such as emails, forms, landing pages, and custom redirects. Engagement History can be enabled for Salesforce Campaigns, Leads, Contacts, Accounts, and Opportunities, and it can display metrics such as views, clicks , submissions, and conversions. Advanced Dynamic Content, Marketing Cloud Account Engagement Activities Visualforce page, and B2B Marketing Analytics are not features that can show landing page engagement data on a Salesforce Campaign page layout, as they are related to other aspects of marketing automation, such as personalization, activity tracking, and analytics. References:  Salesforce documentation

In the enhanced landing page experience within Salesforce, one of the key features is the ability to associate a landing page with either a connected campaign (directly linked to Salesforce campaigns for unified reporting and management) or an unconnected campaign (used solely within Pardot). This flexibility allows marketers to tailor their campaign management strategies according to their specific needs, enhancing the integration and tracking of various marketing efforts directly from within Salesforce.