Free MARKETING CLOUD ACCOUNT ENGAGEMENT SPECIALIST Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

When an engagement studio action step is scheduled to send an email on a specific date, it means

that the email will be sent to all prospects who reach that step on or after that date. Therefore, a

prospect arriving after the send date will be sent the email (D). The prospect will not remain on the

step until a new send date is set (A), skip the Send Email step (B), or be removed from the program

©. Reference: Work with Time and Pauses in Engagement Studio

Form reports show the performance and activity of your Marketing Cloud Account Engagement

forms, which are web forms that capture prospect information. You can use form reports to see how

many prospects have viewed, completed, or started but not completed your forms, as well as the

conversion rate and average time to complete. You can also drill down into individual form

submissions and view the prospect’s details and activities. Reference: [Form Reports], [View Form

Reports]

:

According to the [Salesforce documentation], the recommended Marketing Cloud Account

Engagement asset to use for progressive profiling is a Marketing Cloud Account Engagement form. A

Marketing Cloud Account Engagement form is a web form that can be used to collect information

from prospects and store it in Marketing Cloud Account Engagement. A Marketing Cloud Account

Engagement form can be configured to use progressive profiling, which is a feature that allows the

form to display different fields based on the information that is already known about the prospect.

This way, the form can collect more information over time, without asking the same questions

repeatedly or overwhelming the prospect with too many fields at once. A Marketing Cloud Account

Engagement landing page without a form, a Marketing Cloud Account Engagement form handler, or

a third party form are not recommended for progressive profiling, as they do not have the same

functionality and flexibility as a Marketing Cloud Account Engagement form. Reference: [Salesforce

documentation]

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. Reference: Salesforce documentation

A form handler is a feature that allows you to use your own forms to post your data to Marketing

Cloud Account Engagement. A form handler is similar to a form, but instead of displaying the form on

your website, you point your form to Marketing Cloud Account Engagement. This allows you to

submit data to Marketing Cloud Account Engagement as well as your own database3. Form handlers

are useful when you want to keep the look and feel of your existing forms, or when you want to

capture data from multiple forms using one form handler

According to the Salesforce documentation, the first step the user must take in order to change which

email template is used in a running engagement program is to pause the program. A running

engagement program is a program that is actively sending emails and performing actions to the

prospects in the program. To make any changes to a running program, such as changing the email

template, the user must first pause the program to stop the email sends and actions. After making

the changes, the user can resume the program and continue the email sends and actions. Copying

the original engagement program, changing the wait time for the template, or deleting the old sent

email are not the first steps the user must take, as they will not allow the user to change the email

template in the running program. Reference: Salesforce documentation

According to the Salesforce documentation, the information that the tooltip above each step on the

engagement studio program report provides is high-level metrics only for prospects who have

completed the step. An engagement studio program report is a report that shows the performance

and results of an engagement program, such as the number of prospects, emails, and conversions.

The tooltip above each step on the program report shows the number and percentage of prospects

who have completed that step, as well as the number and percentage of prospects who have taken

the positive, negative, or neutral path after that step. The tooltip does not show the metrics for

prospects who are waiting to complete, who have left, or who have skipped each step, as these are

shown in other sections of the report. Reference: Salesforce documentation

According to the Salesforce documentation, the two capabilities that are true for completion actions

are: C) Completion actions cannot be applied directly on a landing page, and D) Completion actions

do not execute on image file downloads. A completion action is an automation tool that can be used

to perform an action after a prospect successfully completes a marketing element, such as clicking a

link in an email, submitting a form, or visiting a web page. A completion action can be used to

perform actions such as adding a prospect to a list, assigning a prospect to a user, sending an

autoresponder email, or adjusting a prospect’s score. Completion actions cannot be applied directly

on a landing page, as landing pages do not have completion actions. However, completion actions

can be applied on the forms or custom redirects that are embedded on the landing page. Completion

actions do not execute on image file downloads, as image file downloads are not considered as

completion events. However, completion actions can be executed on other types of file downloads,

such as PDFs or Word documents. Completion actions are not applied retroactively, as they are only

applied to prospects who complete the marketing element after the completion action is created.

Completion actions do not apply to both visitors and prospects, as they only apply to prospects who

have been identified by their email address or their Marketing Cloud Account Engagement tracking

cookie. Reference: Salesforce documentation

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. Reference: Salesforce documentation

You can define a user’s role in two ways: during the import process or directly from the user record.

During the import process, you can assign a role to multiple users at once by using a CSV file. Directly

from the user record, you can edit the role of a single user by selecting it from the dropdown menu.

You cannot define a user’s role from the list view or through an automation rule. Reference: Create

and Edit Users, Import Users

In Pardot, when a prospect is included in both the recipient list and the suppression list for a list

email, the suppression list takes precedence. This means the prospect will not receive the email.

Importantly, being on the suppression list for one specific email send does not impact the prospect's

status for future email sends. The suppression is specific to the email in question, and future email

sends will proceed based on the prospect's inclusion in or exclusion from those specific recipient or

suppression lists. This ensures that one-time suppression does not inadvertently affect the prospect’s

eligibility for future communications.

The key difference between an email template and an email content record in the enhanced email

experience within Pardot lies in their usability across different Salesforce platforms. An email

template, once created in Pardot, can be utilized by users across Pardot, Sales Cloud, and Service

Cloud. This allows for a consistent messaging and branding experience across various customer-

facing platforms within the Salesforce ecosystem. In contrast, an email content record in Pardot is

specific to Pardot and designed for use within the platform's email marketing campaigns, focusing on

specific layouts and elements tailored to Pardot's capabilities.

According to the Salesforce documentation, an automation rule is an automation tool that can be

used to send an email to a prospect when a form is submitted and a specific field value is selected on

that form. An automation rule can be configured to trigger an action (such as sending an email) when

a prospect meets certain criteria (such as submitting a form and having a specific field value). The

criteria can be set to Match All or Match Any, depending on the logic required. In this case, the Match

All option should be used, as the prospect needs to meet both conditions (form submission and field

value) to receive the email. A completion action is another automation tool that can be used to

perform an action after a prospect successfully completes a form, but it cannot be used to check for a

specific field value. A dynamic list is a list of prospects that is updated automatically based on certain

criteria, but it cannot be used to send an email directly. A list email is an email that is sent to a

specific list of prospects, but it cannot be triggered by a form submission or a field value.

Reference: Salesforce documentation

The best way to understand how many prospects are currently waiting on a step in an engagement

program is to look at the tooltip above that step. The tooltip will show you the number of prospects

that are currently on that step, as well as the number of prospects that have completed that step.

You can also see the percentage of prospects that have taken a specific action or followed a specific

path from that step. The tooltip is a quick and easy way to get an overview of the performance of

each step in your program

The main cause of a sync from Salesforce to Account Engagement is making field changes to a Lead

or Contact record (D). This will trigger a sync of the updated fields to the corresponding prospect

record in Account Engagement. Updating a formula field in Salesforce (A) will not cause a sync, as

formula fields are not supported by Account Engagement. Updating a field on a Contact record that

does not have an email address (B) will not cause a sync, as email address is a required field for

syncing. Opening a one to one email © will not cause a sync, as it is not a field change event.

Reference: What Causes a Prospect to Sync from Salesforce to Account Engagement?

When users leave the company and have assigned prospects, the best practice is to reassign all

prospects in the CRM and review and modify any completion actions, automation rules, drip

programs and dynamic lists that reference the user. This will ensure that the prospects are not left

unattended and that the marketing activities are updated accordingly. Deleting the user from

Marketing Cloud Account Engagement is not recommended as it will remove the user’s history and

activity data.

The engagement dashboard in B2B Marketing Analytics shows the total submissions across all

Marketing Cloud Account Engagement landing pages, as well as other metrics such as views,

conversion rate, cost per lead, etc. The engagement dashboard helps marketers measure the

performance of their marketing campaigns and optimize their content strategy. The pipeline

dashboard shows the revenue generated by marketing campaigns, the account-based marketing

dashboard shows the engagement and influence of key accounts, and the multi-touch attribution

dashboard shows the impact of marketing touchpoints on sales outcomes. Reference B2B Marketing

Analytics Overview

Opportunities in Salesforce must be tied to a contact syncing with Marketing Cloud Account

Engagement for them to be created in Marketing Cloud Account Engagement. This means that the

opportunity must have at least one contact role in Salesforce, and that contact must be syncing with

a prospect in Marketing Cloud Account Engagement. If the opportunity does not have any contact

roles, or the contact is not syncing with Marketing Cloud Account Engagement, the opportunity will

not be created in Marketing Cloud Account Engagement. This is because Marketing Cloud Account

Engagement needs a prospect to associate the opportunity with, and the contact role is the link

between the opportunity and the prospect. For more details —> 91011

Completion actions are actions that Marketing Cloud Account Engagement executes after a prospect

successfully completes a desired activity, such as submitting a form or clicking a custom

link. Completion actions only affect prospects, not visitors, because visitors are anonymous and have

not been identified by Marketing Cloud Account Engagement yet