Explanation:

📝 Question Explanation:
This question asks about the specific reporting feature in Account Engagement designed to track the performance and engagement levels of your forms. Understanding where to find this data is key to optimizing your lead capture efforts.

💡 Why This is Correct:

Option C: Form reports ✅
The dedicated Form Reports section provides a comprehensive view of a form's success. It shows vital metrics like the number of views, submissions, submission rate, and the specific prospects who converted. This is the definitive tool for analyzing form activity.

❌ Why These Are Incorrect:

Option A: Campaign reports ❌
Campaign reports show the overall performance of a marketing campaign, which may include multiple assets, not the granular, individual performance of a single form.

Option B: Landing Page reports ❌
These reports focus on page views and visitor engagement with a landing page itself, but they do not specifically break down the submission data for a form hosted on that page.

Option D: Conversion reports ❌
While form submissions are a type of conversion, this is not a standard report name in Account Engagement. The most direct and accurate report is the Form report.

Option E: None of the above ❌
This is incorrect because "Form Reports" is the correct and standard reporting feature for this purpose.

🔗 Reference:
Salesforce Help: "View Form Reports"

Explanation:

Summary: ➡️1️⃣
Marketing Cloud Account Engagement (Pardot) is fundamentally designed to sync prospect data with one specific Salesforce organization (or environment). It can only support a single active Salesforce connector at any given time, meaning you cannot link one Account Engagement business unit to two separate Salesforce production accounts simultaneously.

Correct Option:

B. No, you can only have one Salesforce connector at a time. 🛑
One-to-One Design: The Marketing Cloud Account Engagement data model is built around a one-to-one relationship with a Salesforce org. This single connector is the pipeline for all prospect-to-Lead/Contact syncs, user syncs, and field mappings.

Security and Integrity: Allowing multiple connectors would compromise data integrity and security by creating complex conflicts and data-matching issues across different Salesforce environments. Therefore, the system enforces a limit of one active connector per Account Engagement business unit.

Incorrect Options:

A. Yes, you can have up to 2 Salesforce accounts linked to one Marketing Cloud Account Engagement account ❌
The limit is one active Salesforce connector, not two.

C. Yes, but you would need to contact Marketing Cloud Account Engagement Support to enable the feature for you. 📞
This feature cannot be enabled by support, as it is a core structural limitation of the Account Engagement connector architecture.

D. Yes, but it's only available to customers with the Pro Edition 💰
The one-connector limit is a fundamental design rule that applies to all Account Engagement editions (Growth, Plus, Advanced, Premium), not a feature restriction based on edition level.

Reference:
Salesforce Help: Salesforce Connector

Explanation:

User roles in Marketing Cloud Account Engagement (Pardot) define the level of access and permissions for different user types. Default Roles are pre-built by the system and cannot be altered, ensuring a baseline level of security and function. Custom Roles provide flexibility; they must be created by an admin and are fully editable to meet specific, tailored organizational needs.

Correct Options:

A. Default roles are included with Marketing Cloud Account Engagement 📦
Pre-Built: Default roles (like Administrator, Marketing User, Sales Manager, and Sales User) are pre-installed and ready to use upon setting up your Account Engagement account. They provide a standard set of access permissions.

B. Custom roles can be edited ✏️
Flexible: The primary benefit of a custom role is its editability. An administrator can modify its permissions at any time to add or remove access to features like sending emails, managing users, or deleting prospects, ensuring fine-grained control.

E. Custom Roles can be created from scratch 🛠️
New Design: Custom roles can be created by an administrator beginning with a blank slate, where every permission (user type, object access, asset control) is manually configured, or they can be created by copying and then editing an existing default role.

Incorrect Options:

C. Default roles can be edited ❌
Default roles are fixed by the system and cannot be edited by administrators. This restriction prevents accidental changes to core security profiles.

D. Default roles can be deleted 🚫
Since default roles are foundational to the system, they cannot be deleted. Only custom roles can be deleted by an administrator.

F. Custom roles can be created from a default role 👥
While true that a custom role can be created based on a default role (by cloning it), this is an action taken during the creation process, not a defining difference. Option E, that they can be created from scratch, is the broader, defining feature. The difference is the ability to create and edit, not the method of creation.

G. Default roles are included with Marketing Cloud Account Engagement 🎁
This is the same as Option A, which is already selected as a correct and defining difference.

Reference:
Salesforce Help: User Roles

Explanation:

The distinction between a Visitor and a Prospect in Marketing Cloud Account Engagement (Pardot) is entirely based on identity. A Visitor is an anonymous individual whose activity is being tracked via a cookie, but whose identity is unknown (no email address). A Prospect is an identified individual who is known to the system because they have a recorded email address, allowing for targeted communication and synchronization with Salesforce.

Correct Option:

A. A prospect has an identified email address, while a visitor does not have an identified email address. ✅
Visitor (Anonymous): A visitor is a record that tracks activity (like page views) associated with a tracking cookie. Crucially, the system does not know the individual's identity, meaning there is no email address associated with the visitor record.

Prospect (Identified): Once an individual performs an action that reveals their email address (like submitting a form or clicking a tracked link in an email), the system converts the visitor record into a prospect record, which is the necessary prerequisite for all further marketing and sales actions.

Incorrect Options:

B. A prospect has an opportunity associated with it, while a visitor does not have an opportunity associated with it. 💼
While a prospect can have an opportunity, this is not the main difference. A prospect is defined by their email address, not by an association with a Salesforce object like an Opportunity. Many prospects exist without a linked opportunity.

C. A prospect has submitted a Marketing Cloud Account Engagement form, while a visitor has not submitted a Marketing Cloud Account Engagement form. 📝
Submitting a form is a common way a visitor becomes a prospect (by providing their email), but it's not the only way. A prospect is defined by the existence of the email address, which could also be obtained via a Salesforce sync or a list import.

D. A prospect has an assigned user, while a visitor does not have an assigned user. 🧑‍💻
While visitors cannot be assigned to a user, a prospect is not defined by their assignment status. A prospect record exists as soon as an email address is identified, even if they are still unassigned and waiting for an assignment rule to fire.

Reference:
Salesforce Help: Visitor and Prospect Tracking

Explanation:

Account Engagement only syncs opportunities that are tied to Contacts who themselves sync as Prospects. If an opportunity in Salesforce has no linked contact, or the contact isn’t syncing with Pardot, the opportunity record will not appear in Account Engagement. This ensures opportunities are tied to actual people for accurate attribution and ROI reporting within Pardot.

Correct Option:

📊 A. True
Opportunities require a contact role that is linked to a syncing prospect in Pardot. Without that connection, Pardot has no way to associate the opportunity to marketing influence. This design ensures only relevant opportunities tied to actual contacts flow into Pardot for campaign reporting and revenue attribution.

Incorrect Option:

❌ B. False
Claiming this statement is false would suggest that opportunities could sync without being tied to contacts, which contradicts how Pardot’s Salesforce connector works. Opportunities must always be linked to contacts that sync as prospects; otherwise, they never appear in Pardot.

Reference:
Salesforce Help – Pardot Opportunities