Pass the Salesforce Marketers Marketing-Cloud-Account-Engagement-Specialist Questions and answers with CertsForce

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

The two actions that can be used to change a prospect’s Marketing Cloud Account Engagement campaign are:

Create an automation rule to change Marketing Cloud Account Engagement campaign for prospects meeting certain criteria. 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 changing their Marketing Cloud Account Engagement campaign to the one that is relevant to their attributes or behaviors.

Manually change the prospect’s Marketing Cloud Account Engagement campaign when editing the prospect record. You can also change a prospect’s Marketing Cloud Account Engagement campaign by editing their prospect record and selecting a different campaign from the drop-down menu. This is useful when you want to change the Marketing Cloud Account Engagement campaign for a single prospect or a small group of prospects.

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

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

The list email report metric that represents the total number of emails minus hard and soft bounces is total delivered. Total delivered measures how many emails were successfully delivered to the recipients’ inboxes, without being rejected by the email servers. Hard bounces are permanent delivery failures, such as invalid email addresses or blocked domains. Soft bounces are temporary delivery failures, such as full inboxes or server issues. Total opt outs, total sent, and total queued are not the same as total delivered. Total opt outs measures how many recipients unsubscribed from your emails. Total sent measures how many emails were sent from Marketing Cloud Account Engagement. Total queued measures how many emails were waiting to be sent from Marketing Cloud Account Engagement. References [Email Metrics Glossary]

By default, Marketing Cloud Account Engagement will sync with contact accounts in Salesforce. Contact accounts are the standard account type in Salesforce, where each account can have multiple contacts related to it. Marketing Cloud Account Engagement can sync with contact accounts and their related contacts, leads, and opportunities. However, Marketing Cloud Account Engagement can also sync with person accounts in Salesforce, if they are enabled in your org. Person accounts are a special account type in Salesforce, where each account is also a contact. Marketing Cloud Account Engagement can sync with person accounts and their related opportunities, but not with leads. To sync with person accounts, you need to enable the option in the Salesforce connector settings in Marketing Cloud Account Engagement. For more details —> 121314

 One automation rule can match an individual prospect only once. 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 prospect

The option that accurately defines the capabilities of a segmentation rule is that segmentation rules are used to segment prospects based on their activities and demographic data. A segmentation rule is a type of rule that allows marketers to segment their prospects based on specific criteria, such as field values, activities, or scores. A segmentation rule can be used to create dynamic lists, add prospects to campaigns, or apply tags or completion actions. Segmentation rules are not used to create new forms, score and grade prospects, or assign prospects to users in Salesforce, as these are different functions that require different tools1. References: 1: Segmentation Rules

 You can preview or test matches for automation rules before you run them by using the automation preview option. This option allows you to see how many prospects will be matched by your automation rules without actually running them. You can access this option by clicking the Preview button while the rules are in Paused mode. You will receive an email notification when the preview is finished or you can wait on the page for it to finish in real-time. The preview will tell you how many prospects will be matched and show you a sample of them. If you adjust criteria on existing automation rules, please note that automation previews will identify only prospects who have not already had the rule’s actions applied to them.

Answer A is incorrect because running the automation rule will not only show you how many matches there are, but also apply the actions to them, which may not be what you want. Answer C is incorrect because creating a list and seeing how many prospects are affected will not give you the same results as the automation preview option, since the list criteria may not match the automation rule criteria exactly. Answer D is incorrect because there is no such option as the prospect table actions. References: Automation Rules, Preview Automation Rules