Marketing-Cloud-Account-Engagement-Specialist Salesforce Marketing Cloud Account Engagement Specialist (SP25) Free Practice Exam Questions (2025 Updated)

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 values. 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 prospect1. 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 matches 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. 

 According to the Salesforce documentation, the step type that would be used in engagement studio to add prospects to another engagement studio program’s recipient list is an action. An engagement studio program is a feature that allows users to build, test, and report on automated programs that send targeted emails and perform actions based on prospect behavior and criteria. An engagement studio program consists of steps that define the logic and flow of the program. There are three types of steps: triggers, actions, and rules. A trigger is a step that checks for a prospect’s activity, such as opening an email, clicking a link, or submitting a form. An action is a step that performs an action on a prospect, such as sending an email, adjusting a score, or adding to a list. A rule is a step that checks for a prospect’s attribute or value, such as score, grade, or field value. To add prospects to another engagement studio program’s recipient list, the user can use an action step that adds prospects to a list. The user can then use that list as the recipient list for another engagement studio program. A rule, an end, or a trigger are not the step types that would be used in engagement studio to add prospects to another engagement studio program’s recipient list, as they are related to other functions, such as checking for criteria, ending the program, or checking for activity. References: Salesforce documentation

 The recommended way to accomplish sending out a new whitepaper to prospects and tracking who opens the PDF is to upload the whitepaper PDF as a content file and link to it in the body of the email. A content file is a type of file that can be uploaded and stored in the Content Builder, which is a tool that allows marketers to create and manage content assets. A content file can be linked to in the body of an email, which allows prospects to access the file by clicking the link. By linking to a content file, marketers can also track who opens the PDF, as the link will generate a tracking code that records the open activity. Uploading the whitepaper PDF as a content block, attaching it to the email, or embedding it in the email are not recommended ways to accomplish sending out a new whitepaper to prospects and tracking who opens the PDF, as they either do not allow linking, do not allow tracking, or do not display properly. References: : Content Files

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 industry, company size, and job title. By combining the score and grade, marketers can segment and prioritize their prospects more effectively3. References: 3: Scoring and Grading Prospects

The user role that a Marketing Cloud Account Engagement user must have in order to verify the Salesforce connector is Administrator. A Salesforce connector is a feature that allows you to connect your Marketing Cloud Account Engagement account with your Salesforce CRM system, and enable bi-directional data sync and alignment between sales and marketing. To verify the Salesforce connector, you need to have the Administrator user role in Marketing Cloud Account Engagement, which gives you full access to all features and settings in Marketing Cloud Account Engagement, including the connectors. You also need to have the appropriate permissions in Salesforce, such as the API Enabled and Modify All Data permissions

 According to the Salesforce documentation, the asset that needs to be created first in order for a user to send a prospect a one-to-one email is an email template. A one-to-one email is an email that is sent to an individual prospect, such as a follow-up or a confirmation email. A one-to-one email can be sent from the prospect record, a list, a report, or a campaign. To send a one-to-one email, the user needs to have an email template that defines the content and layout of the email. An email template can be created in Email Studio or Content Builder, and it can be personalized with variable tags or dynamic content. An autoresponder, an engagement studio program email, or a list email are not assets that need to be created first in order for a user to send a prospect a one-to-one email, as they are related to other types of email sends, such as automated responses, program emails, or mass emails. References: Salesforce documentation

According to the Salesforce documentation, the option that is not a way to assign a custom role to a user is: D) Add a user to a Custom Role directly from their User Record. 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:

Edit an existing Default Role, and it will automatically convert to a Custom Role: A default role is a predefined role that comes with Marketing Cloud Account Engagement, and that has a fixed set of permissions and access levels. A default role can be edited by the administrator in the Admin tab in Marketing Cloud Account Engagement, and it will automatically convert to a custom role when the changes are saved. The administrator can then assign the custom role to a user or a group of users.

Assign new users to a previously created Custom Roles during the import process: A new user is a user that is not yet added to Marketing Cloud Account Engagement, and that needs to be created and assigned a role. A new user can be imported by the administrator in the Admin tab in Marketing Cloud Account Engagement, and they can be assigned to a previously created custom role during the import process. The administrator can use a CSV file to import multiple new users at once, and to assign them to different custom roles.

Add a batch of existing users to a Custom Role using table actions: An existing user is a user that is already added to Marketing Cloud Account Engagement, and that has a role assigned to them. An existing user can be added to a custom role by the administrator in the Admin tab in Marketing Cloud Account Engagement, and they can use the table actions to add a batch of existing users to a custom role at once. The administrator can select multiple existing users from the User List, and then click on the Change Role option in the table actions. The administrator can then choose the custom role that they want to assign to the selected users.

The option that is not a way to assign a custom role to a user is: Add a user to a Custom Role directly from their User Record. A user record is a feature that shows the detailed information and settings of a user in Marketing Cloud Account Engagement. A user record can be accessed from the Admin tab in Marketing Cloud Account Engagement, and it can show different sections of information for the user, such as details, permissions, or activity. The user record can also show the role that is assigned to the user, but it cannot be used to add a user to a custom role directly. The user record can only be used to edit the user’s information, such as name, email, password, or timezone, but not the user’s role. To add a user to a custom role, the administrator needs to use one of the methods mentioned above, such as editing an existing default role, assigning new users during the import process, or adding a batch of existing users using table actions. References: Salesforce documentation

 When an opportunity is created in Marketing Cloud Account Engagement from the sync with Salesforce, the campaign that is set on the opportunity is the first campaign of the first contact associated with the opportunity. This means that Marketing Cloud Account Engagement will look at the contact roles of the opportunity in Salesforce, and find the contact that was added first. Then, Marketing Cloud Account Engagement will look at the campaign history of that contact, and find the campaign that was assigned first. That campaign will be the one that is associated with the opportunity in Marketing Cloud Account Engagement. This helps Marketing Cloud Account Engagement track the source and influence of the opportunity. For more details —> 678