For a seamless integration between Marketing Cloud Account Engagement and a Salesforce custom object, two foundational requirements must be met. First, the custom object in Salesforce must be linked to a core prospect record (Lead, Contact, or Account) via a lookup or master-detail relationship. This association is critical for Account Engagement to relate the custom object's data to a specific prospect. Second, the Salesforce Connector User, which acts as the integration agent, requires at least 'Read' permission to the custom object and its fields. Without this permission, Account Engagement cannot access or sync the data from Salesforce.

C. A relationship to a Campaign or Opportunity is not a prerequisite for linking the custom object to a prospect for syncing purposes.

D. 'Display in Table' is a user interface configuration setting within Account Engagement, configured after the integration is established, not a foundational requirement for the integration itself.

1. Salesforce Help Documentation, "Considerations for Using Custom Objects":

This document explicitly states the prerequisites. Under the "Prerequisites" section, it lists: "To use custom objects with Account Engagement, they must have a relationship with a contact, account, or lead record." This directly supports option A.

The same section also states: "The connector user must have read permission for the custom object." This directly supports option B.

2. Salesforce Help Documentation, "Integrate Custom Objects":

This step-by-step guide reinforces the requirements. Step 1 is: "In Salesforce, create a custom object and associate it with the account, contact, or lead object." (Supports A).

Step 2 is: "Give the connector user read permission to the new object." (Supports B).

Step 5, "Map fields," includes the action to "Choose which fields to display in the Account Engagement table," confirming that this is a later configuration step, not a prerequisite for integration. (Refutes D).

Marketing Cloud Account Engagement provides native functionality for marketers to both import and export prospect data. Prospects can be imported from a .csv file to create new records or update existing ones. Similarly, prospect data can be exported to a .csv file for purposes such as reporting, analysis, or backup.

The "False" option is incorrect because the ability to manage data flow in and out of the platform is a fundamental feature of Account Engagement. The system is designed to allow marketers to bring in leads from various sources (via import) and to extract data for use in other systems or for analysis (via export).

1. Salesforce Help, Account Engagement Documentation, "Import Prospects": This official document outlines the entire process for importing prospects. It states, "You can import a list of prospects into Account Engagement from a CSV file. The import wizard lets you map the columns in your file to fields in Account Engagement and choose how the import affects existing prospect records."

Source: Salesforce Help, Import Prospects, Section: "Import Prospects with Account Engagement".

2. Salesforce Help, Account Engagement Documentation, "Export Prospects": This document details the procedure for exporting prospect data. It specifies, "You can export prospects in .csv format from any prospect table or from the prospect import page. The export file includes the prospect’s information, and any custom fields."

Source: Salesforce Help, Export Prospects, Section: "Export Prospects".

A prospect's score in Account Engagement is a numerical value that can be adjusted both positively and negatively. Automation rules, completion actions, or Engagement Studio programs can be configured to subtract points from a prospect's score. If a prospect has a low or zero score and performs an action that has a negative scoring value associated with it (e.g., visiting a "careers" page, having an invalid job title), their total score can become less than zero. This functionality is often used to penalize actions that indicate a prospect is a poor fit or to reduce the score of unqualified leads.

The "False" option is incorrect because the Account Engagement scoring system is not floored at zero. The platform's design explicitly allows for score decrements through various automation features, which can result in a total score that is a negative integer.

1. Salesforce Help, Account Engagement Documentation, "Scoring": This document explicitly states how scoring functions. In the "How Scoring Works" section, it clarifies the nature of the score value: "A prospect’s score can be a positive or negative number and is a reflection of the prospect’s interest."

2. Salesforce Help, Account Engagement Documentation, "Considerations for Scoring": This guide provides best practices and details about the scoring mechanism. Under the "Scoring" section, it reiterates the core principle: "A prospect’s score can be a positive or negative number."

3. Salesforce Help, Account Engagement Documentation, "Automation Rule Actions": This document details the actions available within automation rules. The action "Adjust prospect's score" allows an administrator to specify a positive or negative integer to add to or subtract from the prospect's current score, providing the mechanism for a score to become negative.

Marketing Cloud Account Engagement is designed to prevent data corruption and conflicting changes by implementing an asset locking mechanism. When a user begins editing an asset, such as an Email Template, the system places a lock on it. If another user attempts to edit the exact same template while it is locked, they are not able to edit it simultaneously. Instead, they are presented with a prompt that gives them the option to either take over the editing session (which forces the original user out) or open the asset in a read-only mode.

The statement "True" is incorrect because the system's architecture explicitly prohibits simultaneous editing by multiple users. The platform's conflict resolution—prompting a second user to take over or view in read-only—is a mechanism to manage sequential, not simultaneous, editing sessions.

1. Salesforce Help: Considerations for Editing Assets

Reference: In the section detailing asset editing behavior, the documentation states, "Only one user can edit an asset at a time. If you try to edit an asset that another user is editing, you’re prompted to take over the editing session or open the asset in read-only mode." This directly confirms that simultaneous editing is not possible.

Source: Official Salesforce Vendor Documentation for Marketing Cloud Account Engagement.

In Marketing Cloud Account Engagement, "CRM User" is not a selectable data type when creating a custom prospect field. A field functions as a user field for the purpose of assignment when a standard field type (such as Dropdown, Text, or Hidden) is mapped to a user lookup field in the connected CRM (e.g., the OwnerID field in Salesforce). The system recognizes this mapping and allows the field to be used for assignments, but the underlying field type within Account Engagement's settings is not "CRM User."

The statement is false because it incorrectly identifies a functional role of a field as a distinct, selectable data type. While Account Engagement has the concept and functionality of a "user field," this is achieved through mapping a standard field type to a specific kind of CRM field, not by selecting "CRM User" from the type list during field creation. The available types are Text, Number, Date, Dropdown, etc.

1. Salesforce Help Documentation, "Prospect Field Settings Reference." This document provides the definitive list of available field types for prospect fields in Account Engagement. The list includes Text, Number, Date, Dropdown, Radio Button, Checkbox, Textarea (Large Text), Multi-Select, and Hidden. It does not list "CRM User" as a selectable type.

Source: Salesforce Help, Marketing Cloud Account Engagement, "Prospect Field Settings Reference."

2. Salesforce Help Documentation, "Considerations for Creating Custom Fields." This document explains the process for creating a field that functions as a user field. It states, "To create a user field, map a prospect field to a CRM user lookup field. You can then use the field for prospect assignment." This confirms that a user field is created by mapping a standard field, not by selecting a specific "CRM User" type.

Source: Salesforce Help, Marketing Cloud Account Engagement, "Considerations for Creating Custom Fields," section on User Fields.

The Salesforce Connector for Marketing Cloud Account Engagement is designed to facilitate a seamless flow of data between marketing and sales. It natively syncs specific standard Salesforce objects that are critical for B2B marketing and sales alignment. Among the options provided, Accounts and Opportunities are standard objects that are synchronized. Accounts represent the companies that prospects belong to, while Opportunities track potential sales deals, allowing marketers to calculate ROI and nurture prospects based on their engagement with the sales cycle.

C. Case: Cases are a standard Salesforce object for customer service and support, but they are not synced by default with the Account Engagement connector.

D. Order: Orders represent confirmed transactions and are not a standard object synced by the Account Engagement connector, which focuses on potential revenue via Opportunities.

1. Salesforce Help, Marketing Cloud Account Engagement: Objects Synced with the Salesforce Connector. This document explicitly lists the standard objects that sync. It states, "When you verify your Salesforce connector, you can sync these objects: Prospects, Accounts, Opportunities, Campaigns, Users, and Custom Objects." This directly confirms that Accounts and Opportunities are synced.

2. Salesforce Help, Marketing Cloud Account Engagement: Salesforce Connector v2 Setup Guide. In the "How Data Syncs with the Salesforce Connector" section, the documentation details the relationships between synced objects, highlighting the connection between Prospects (Leads/Contacts), Accounts, and Opportunities as the core of the B2B data model.

3. Salesforce Help, Marketing Cloud Account Engagement: Considerations for Using the Salesforce Connector. This guide outlines the capabilities and limitations of the connector. It details how prospect records in Account Engagement sync with lead and contact records in Salesforce, and how these are related to Accounts and Opportunities, reinforcing that these are the key synced objects. It makes no mention of Cases or Orders as standard sync objects.

While the standard, out-of-the-box Account Engagement Email Preference Center does not require a login (it uses a unique, tokenized URL to identify the prospect), it is a common and supported implementation to create a custom preference center that does require a login. This is typically achieved by hosting the preference management page within a secure customer portal or a Salesforce Experience Cloud site. In this scenario, a user logs in to their account, and their preference changes are synced back to their Account Engagement prospect record via the Account Engagement API or a form handler. This provides a more secure and integrated user experience.

The statement is not False because the platform's capabilities extend beyond the default features. A key role of a consultant is to understand how to meet specific business requirements, such as a secure, login-gated preference center, through customization and integration. Stating this is False would incorrectly limit the platform's capabilities to only its default, out-of-the-box functionality and ignore the robust API that enables such custom solutions.

1. Salesforce Help Documentation - Create a Custom Preference Center Page: This official document outlines the methods for creating a custom preference center. It states, "You can build a preference center page on your own website and use a Pardot form, form handler, or API to sync prospect preferences." A page built on a company's own website can be placed behind a login authentication system.

Source: Salesforce Help, Account Engagement / Email Marketing / Email Preference Pages / "Create a Custom Preference Center Page".

2. Account Engagement Developer Guide - API Reference: The Account Engagement API provides the necessary endpoints to programmatically manage a prospect's list memberships from an external, authenticated system. The prospect list memberships object allows a developer to read, create, and update a prospect's subscription status for various lists, which is the core mechanism for a custom, login-required preference center.

Source: Salesforce Developers, Account Engagement Developer Guide, API Reference Version 5, Objects / "Prospect List Memberships".

3. Salesforce Architects Design - Marketing Cloud and Experience Cloud Integration Patterns: Architect-level documentation frequently discusses the pattern of using an Experience Cloud site (which is a login-based portal) to manage marketing communication preferences. Data from the authenticated Experience Cloud user is updated on their Contact/Lead record, which then syncs to the corresponding Account Engagement prospect record.

Source: Salesforce Architects, "Customer 360 Guide for Architects", Solution Kits / "Enhance Marketing with Transactional Data from Experience Cloud". This guide describes patterns where authenticated portal users interact with systems that sync back to marketing platforms.

Marketing Cloud Account Engagement (formerly Pardot) imposes daily API call limits that vary by edition to ensure system stability and performance. The limits are tiered based on the subscription level. The Growth edition is allocated 25,000 calls per day, the Plus edition receives 50,000 calls per day, and the Advanced edition is provided with 100,000 calls per day. These limits reset every 24 hours. Exceeding these limits will result in API calls being temporarily blocked until the next 24-hour window begins.

A. Incorrect. All cloud-based platforms, including Account Engagement, have API limits to maintain system health and prevent abuse.

B. Incorrect. The API limits are not uniform across all editions; they are tiered, and the base limit is higher than 10,000.

C. Incorrect. This option incorrectly states the limit for the Plus Edition as 25,000. The correct limit for the Plus Edition is 50,000 calls per day.

1. Salesforce, Account Engagement Developer Guide: API Usage and Limits. This document explicitly lists the daily API call limits for each edition. It states: "Your daily API call limit is determined by your Account Engagement edition. Growth: 25,000; Plus: 50,000; Advanced: 100,000; Premium: 100,000."

2. Salesforce Help: Pardot Editions and Pricing. The official pricing and feature comparison page details the features and limits, including API calls per day, for each Account Engagement edition, corroborating the numbers in the developer guide. (Note: Specific pricing pages can change, but the developer guide is the canonical source for technical limits).

The "Email" field is a required, default prospect field in Marketing Cloud Account Engagement, not a custom field type. When an administrator creates a new custom field, they must select from a predefined list of field types such as Text, Number, Date, or Dropdown. The "Email" type is reserved exclusively for the default Email Address field and is not an available option for custom field creation.

The statement "True" is incorrect because it conflates the existence of the default "Email" field with the available types for custom fields. While an "Email" field is fundamental to the system, its special data type cannot be assigned to any new, user-created fields.

1. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Create Custom Prospect Fields." This document outlines the process for creating custom fields and lists the available field types. The list includes Text, Number, Date, Dropdown, Radio Button, Checkbox, Textarea, Multi-Select, and Hidden. The "Email" type is not included in this list of options for custom fields.

2. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Prospect Fields." This resource details the default fields that come standard with Account Engagement. It explicitly states, "The email address field is a default field and is required on all records." This confirms its status as a default, not a custom, field.