According to the  Salesforce documentation , if Salesforce has a custom field of the same name on Leads and Contacts, Marketing Cloud Account Engagement pulls the field name from the Lead field. A custom field is a field that is created by the user to store additional information that is not available in the standard fields. A custom field can be created and managed by the administrator in the Admin tab in Marketing Cloud Account Engagement or Salesforce, and it can be synced between the two platforms. A custom field can have the same name on differ ent objects, such as Leads and Contacts, but it can have different values or settings. If Salesforce has a custom field of the same name on Leads and Contacts, Marketing Cloud Account Engagement pulls the field name from the Lead field, as it is the primary source of the field name. Marketing Cloud Account Engagement does not pull the field name from the Contact field, as it is the secondary source of the field name. However, Marketing Cloud Account Engagement can pull the field value from either the Lead o r the Contact field, depending on which object the prospect is associated with in Salesforce. For example, if Salesforce has a custom field called “Industry” on both Leads and Contacts, Marketing Cloud Account Engagement will pull the field name “Industry” from the Lead field, but it will pull the field value from either the Lead or the Contact field, depending on the prospect’s record type in Salesforce. References:  Salesforce docume ntation

According to the  Salesforce documentation , the answer is false. There are some restrictions on how you assign custom users abilities. A custom user is a user who has a custom role assigned to them in Marketing Cloud Account Engagement. A custom role is a feature that allows users to create and assign custom permissions and access levels to other users in Marketing Cloud Account Engagement. A custom role can be created and managed by the administrator in the Admin tab in Marketing Cloud Account Engagement, and it can be assigned to new or existing users. A custom role can be assigned to a user by using different methods, such as editing an existing default role, assigning new users during the import process, or adding a batch of existing users using table actions. However, there are some restrictions on how you assign custom users abilities, such as:

You cannot assign a custom user the ability to create or edit other users, roles, or connectors. This ability is reserved for the administrator only, and it cannot be delegated to a custom user.

You cannot assign a custom user the ability to access or edit the data or settings of another user, unless the custom user is the manager of that user. A manager is a user who is responsible for overseeing and managing other users, and who can view and edit their data or settings. A manager can be assigned to a user in the user record, and they can have a custom role or a default role.

You cannot assign a custom user the ability to access or edit the data or settings of a prospect, unless the custom user is the owner or the assigned user of that prospect. An owner is a user who created the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An assigned user is a user who is assigned to the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An owner or an assigned user can be assigned to a prospect in the prospect record, and they can have a custom role or a default role.

 The combination of automation tools that LenoxSoft should use to achieve their goal is an automation rule and a completion action. An automation rule is a rule that runs continuously in the background and matches prospects based on the criteria you set.  A completion action is an action that Marketing Cloud Account Engagement executes after a prospect successfully completes a desired activity, such as submitting a form or clicking a custom link 1 .  LenoxSoft can use an automation rule to update the custom field for anyone who has submitted the form before today, and a completion action to update t he custom field for anyone who submits the form moving forward. 

 An automation rule is a rule that automatically applies an action to a prospect based on whether they match set criteria. An automation rule consists of two parts: the criteria and the action. The criteria are the conditions that the prospect must meet to trigger the rule, such as having a certain score, grade, or field value. The action is the outcome that the rule will apply to the prospect, such as changing their field value, adding them to a list, or sending them an email.  An automation rule can run once or multiple times per prospect, depending on the settings

According to the  Salesforce documentation , the asset that should be applied during the creation of the Marketing Cloud Account Engagement landing page to accomplish the goal of using pre-existing HTML is a layout template. A layout template is a reusable design that defines the structure and style of a landing page. A layout template can be created using HTML, CSS, and JavaScript, and it can include editable regions where the user can add content and forms. A layout template can be applied to multiple landing pages, and it can be used to create cu stom landing pages with pre-existing HTML. Dynamic content, custom redirect, and stock template are not assets that can be applied during the creation of the Marketing Cloud Account Engagement landing page to accomplish the goal of using pre-existing HTML, as they are related to other aspects of landing page creation, such as personalization, tracking, and design. References:  Salesforce documentation

A form handler setting that allows prospects to receive multiple autoresponders from form submissions within a 24-hour period is Disable Visitor Activity Throttling and send autoresponder emails after every submission.  This setting overrides the default behavior of Marketing Cloud Account Engagement , which is to throttle visitor activity and send only one autoresponder email per prospect per form per day 2 .  Th is setting can be useful for forms that are used for multiple purposes, such as event registration, content download, or contact request

The automatic workflow that can be created to prevent the unassigned prospects from getting assigned is to create an automation rule based on the prospects’ time to adjust their score to 0 if they haven’t been active in 60 days. An automation rule is a rule that runs continuously in the background and matches prospects based on the criteria you set. You can use an automation rule to perform actions on the matched prospects, such as adding them to a list, assigning them to a user, or changing their field val ues. However, an automation rule can only match a prospect once in its lifetime, even if the prospect meets the criteria again later.  This prevents duplicate or conflicting actions from being applied to the same prospect 1 . Therefore, an automation rule is ideal for creating a workflow that resets the score of the unassigned prospects who have been inactive for 60 days, and prevents them from getting assigned by another automation rule that assigns prospects based on their score. To create an automation rule, you need to specify the criteria and the actions that you want to execute.  For example, you can create an automation rule that matche s prospects who have not been assigned to a user, have not had any activity in the last 60 days, and have a score greater than 0, and then use the action Adjust Score to set their score to 0. 

The correct way to use a custom account field in Salesforce for segmentation in Marketing Cloud Account Engagement is to create a custom account field in Marketing Cloud Account Engagement and map it to the account field in Salesforce. This will allow you to sync the data between the two systems and use the custom field as a segmentation criterion in Marketing Cloud Account Engagement. You can create a custom account field in Marketing Cloud Account Engagement by going to Settings > Object and Field Configu ration > Prospect Account Fields > Add Custom Field.  Then, you can map it to the corresponding account field in Salesforce by selecting it from the drop-down menu

A lead qualification model based on implicit prospect interest and explicit information provided by prospects requires the feature of Marketing Cloud Account Engagement Score and Grade. The score is a numerical value that measures the implicit interest of a prospect based on their engagement with marketing activities, such as opening emails, clicking links, and visiting landing pages. The grade is a letter value that measures the explicit fit of a prospect based on the information they provide, such as indu stry, company size, and job title.  By combining the score and grade, marketers can segment and prioritize their prospects more effectively 3 . References:  3 : Scoring and Grading Prospects

 The email in Step 3: Send email “Getting Started” will be received by the prospect on Monday, if the prospect starts the drip program on Wednesday. A drip program is a program that allows you to send a series of emails to your prospects based on a predefined schedule and logic. You can use drip programs to nurture your prospects, educate them about your products or services, or encourage them to take action. You can also use drip programs to send emails only during business hours, which are the hours that you specify for sending emails to your prospects, such as 10am - 4pm M-F. To calculate when the email in Step 3 will be received by the prospect, you need to follow the drip logic and the business hours settings. The drip logic is outlined below:

Start

Step 1: Send email “Welcome.”

Step 2: Pause 3 days.

Step 3: Send email “Getting Started.”

Step 4: Pause 7 days.

Step 5: Send email “Tech Setup.”

Step 6: Pause 7 days.

Step 7: Send email “Complete Configuration.”

End

The business hours settings are:

Only send emails during business hours (10am - 4pm M-F)

Assuming that the prospect starts the drip program on Wednesday at 10am, the email in Step 3 will be received by the prospect on Monday at 10am, following this logic:

Wednesday 10am: The prospect starts the drip program and receives the email in Step 1.

Thursday 10am: The prospect is still in Step 2, which pauses for 3 days.

Friday 10am: The prospect is still in Step 2, which pauses for 3 days.

Saturday 10am: The prospect is still in Step 2, which pauses for 3 days. However, since it is not a business day, the pause does not count.

Sunday 10am: The prospect is still in Step 2, which pauses for 3 days. However, since it is not a business day, the pause does not count.

Monday 10am: The prospect completes Step 2, which pauses for 3 days, and moves to Step 3, which sends the email “Getting Started.”

Therefore, the email in Step 3 will be received by the prospect on Monday at 10am.