Marketing-Cloud-Account-Engagement-Specialist Exam Dumps - Salesforce Marketing Cloud Account Engagement Specialist (SU24)

The limitations of connecting Marketing Cloud Account Engagement to a Salesforce Sandbox account are: if connected to a sandbox first, when you create your production connector, all prospects will not automatically queue to sync, and Marketing Cloud Account Engagement can’t “wipe” data, so you will need to manually delete any prospects and data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector before enabling the connector for your production instance. A Salesforce Sandbox account is a copy of your production environment that you can use for testing and development purposes. Marketing Cloud Account Engagement Sandboxes are test versions of a Marketing Cloud Account Engagement Business Unit that you can provision within a Salesforce Sandbox. However, Marketing Cloud Account Engagement Sandboxes have some limitations that you need to be aware of before using them. One limitation is that if you connect Marketing Cloud Account Engagement to a Salesforce Sandbox first, and then create a production connector, the prospects in your Marketing Cloud Account Engagement account will not automatically sync with the production environment. You will need to manually sync them or use an automation tool to do so. Another limitation is that Marketing Cloud Account Engagement cannot erase the data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector, such as prospects, fields, and assets. You will need to manually delete them before enabling the connector for your production instance, or else you will end up with duplicate or unwanted data in your Marketing Cloud Account Engagement account1112 References: 11: Marketing Cloud Account Engagement Sandboxes: What They Can, and Can’t Do12: Use Marketing Cloud Account Engagement Sandboxes

You can use an automation rule to opt out prospects by changing their field value of ‘Do Not Email’ to ‘true’. This will prevent them from receiving any email communication from you. You cannot use an automation rule to change the field value to ‘Opt-out’, since that is not a valid option for the ‘Do Not Email’ field. You also cannot use an automation rule to opt out prospects by changing any other field value, since the ‘Do Not Email’ field is the only one that controls the opt-out status of prospects. References: [Automation Rules], [Opt Out Prospects]

 A prospect’s score is a numerical value that indicates their level of interest in your products or services. You can change a prospect’s score in two ways: using completion actions or manually. Completion actions are tasks that are performed after a prospect successfully completes a marketing element, such as a form, landing page, or custom redirect. You can use completion actions to adjust a prospect’s score based on their behavior. Manually, you can edit a prospect’s score by entering a new value in the score field on their record. You cannot change a prospect’s score using segmentation rules or profiles. References: [Scoring], Completion Actions, [Edit Prospects]

 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 landing page without a form is the Marketing Cloud Account Engagement asset that an administrator would create to advertise an upcoming event’s schedule without requesting information from those who visit. A landing page is a web page that can display any content, such as text, images, videos, or links. A form is a web element that can collect information from visitors, such as name, email, or preferences. A landing page with a form, a landing page with a form handler, or an email template with a form embedded into the HTML are not suitable for advertising an event’s schedule without requesting information, as they all involve forms that require visitor input3. References: 3: [Landing Pages and Forms]

According to the Salesforce documentation, the actions that can be done with the gear icon on the prospect list are: B) Assign, C) Delete, and D) Edit. The gear icon is a feature that allows users to perform different actions on a prospect or a group of prospects from the Prospect List. The gear icon can be accessed from the Prospects tab in Marketing Cloud Account Engagement, and it can show different options for the selected prospect or prospects, such as assign, delete, or edit. The assign option allows the user to assign the prospect or prospects to a user, a group, or a queue. The delete option allows the user to delete the prospect or prospects from Marketing Cloud Account Engagement. The edit option allows the user to edit the prospect or prospects’ information, such as name, email, or custom fields. The copy option is not an action that can be done with the gear icon on the prospect list, as it is not an available option for the prospect or prospects. References: Salesforce documentation

 According to the Salesforce documentation, the types of fields that are not supported by the Marketing Cloud Account Engagement sync are: B) Formula fields, D) Geolocation fields, and E) Text Area (rich) fields. A Marketing Cloud Account Engagement sync is a feature that allows users to connect and exchange data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A Marketing Cloud Account Engagement sync can be configured by the administrator in the connector settings, and it can be customized for different objects, fields, or actions. A Marketing Cloud Account Engagement sync can support different types of fields, such as text, number, date, checkbox, picklist, or lookup fields. However, a Marketing Cloud Account Engagement sync cannot support some types of fields, such as formula, geolocation, or text area (rich) fields. A formula field is a field that calculates a value based on a formula or an expression. A geolocation field is a field that stores the latitude and longitude coordinates of a location. A text area (rich) field is a field that allows users to enter formatted text, images, or links. These types of fields are not supported by the Marketing Cloud Account Engagement sync, as they are either incompatible, complex, or large for the data exchange. A record type field is a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that defines different business processes, page layouts, or picklist values for different users. A number field is also a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that stores numerical values. References: Salesforce documentation