Salesforce PDX-101 Exam Dumps

You can delete a prospect through the prospect table actions. The prospect table is a list of all the prospects in your Marketing Cloud Account Engagement account, which you can access by navigating to Prospects > Prospect List. From there, you can select one or more prospects and click on the Tools button to see the available actions. One of the actions is Delete, which will permanently remove the selected prospects from your Marketing Cloud Account Engagement account. You can also delete a single prospect by clicking on their name and then clicking on the Delete button on their record.

Answer A is incorrect because you cannot delete a prospect through a completion action. A completion action is a task that is performed after a prospect successfully completes a marketing element, such as a form, landing page, or custom redirect. You can use completion actions to perform various actions on prospects, such as sending emails, adjusting scores, changing campaigns, or adding tags, but not deleting them. Answer B is incorrect because you cannot delete a prospect through an automation rule. An automation rule is a criteria-based action that is triggered when a prospect matches the rule. You can use automation rules to perform various actions on prospects, such as sending emails, adjusting scores, changing campaigns, or adding tags, but not deleting them. Answer C is incorrect because you can delete prospects, as explained above. Reference:Prospect List, [Delete Prospects], [Completion Actions], [Automation Rules]

Marketing Cloud Account Engagement can sync with Salesforce custom fields that are on the Lead, Contact, or Account objects. Custom Prospect fields in Marketing Cloud Account Engagement can be mapped to custom Lead or Contact fields in Salesforce. Custom Account fields in Marketing Cloud Account Engagement can be mapped to custom Account fields in Salesforce. Custom Opportunity fields in Marketing Cloud Account Engagement can be mapped to custom Opportunity fields in Salesforce.Custom Record Type fields are not supported by Marketing Cloud Account Engagement and cannot be synced

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

According to theSalesforce documentation, when a prospect is added to a suppression list in an engagement studio program, the prospect is paused from receiving any further emails or actions from the program. However, the prospect's progress in the program is not reset or removed. If the prospect is removed from the suppression list, the prospect will resume the program from where they left off, which is the next step after the last completed step. In this case, the prospect will continue on the engagement studio program onto step 6. Reference:Salesforce documentation

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 type 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. Reference:Marketing Cloud Account Engagement Dynamic Lists for Faster Segmentation (+ 10 Examples),Create a Dynamic List - Salesforce