Explanation:

During Account Engagement implementation, several technical configurations must be established for proper functionality and compliance. Tracking codes capture visitor activity, while email authentication improves deliverability. CNAMEs ensure branded, secure URLs, and IP whitelisting keeps API and system connections safe. Fonts, however, are purely cosmetic and have no bearing on technical setup. Together, these four required items enable accurate tracking, trustworthy communication, and secure account performance.

Correct Options:

📊 A. Tracking Code
Adding the Pardot tracking code to web properties is essential to capture visitor data. Without it, prospect activity such as page views and form submissions cannot be tracked. It underpins automation, scoring, and reporting, making it one of the first tasks in implementation.

📧 B. Email Authentication
Configuring SPF, DKIM, and DMARC validates Account Engagement as a trusted sender. This step prevents emails from being flagged as spoofed or spam. Skipping authentication leads to poor deliverability and reduced engagement, so it’s non-negotiable for reliable sending.

🔗 C. CNAME
Setting up a CNAME allows branded URLs for tracking links, files, and landing pages. Instead of Pardot-hosted domains, prospects see your company’s branded domain, which improves trust, click-through rates, and brand consistency. It also helps avoid spam filtering.

🔒 D. IP Whitelisting
Ensuring Salesforce Pardot IPs are whitelisted in your organization’s network prevents sync disruptions. This setup step ensures that emails, API calls, and connector data flow without being blocked by internal firewalls. It’s part of securing reliable integration.

Incorrect Option:

🎨 E. Using Custom Fonts
Custom fonts can enhance design but are not a technical requirement during setup. Implementation priorities focus on deliverability, security, and tracking. Fonts are purely stylistic choices and can be added later without impacting functionality.

Reference:
Salesforce Help – Pardot Implementation Guide

Explanation:

The Salesforce Marketing Cloud Account Engagement (Pardot) Facebook connector allows users to schedule and post content to Facebook directly from Pardot’s Social Posting feature. This integration supports posting to specific types of Facebook accounts, enabling marketers to manage social media campaigns alongside other marketing activities. As of September 2025, the Pardot Facebook connector supports posting to Company Pages (also known as Business Pages) and Personal Pages, provided the user has the necessary permissions to post to these accounts.

Let’s analyze each option:

A. Video Pages (Incorrect):
Facebook does not have a distinct category called “Video Pages” as a page type. While videos can be posted to Company Pages or Personal Pages, there’s no specific “Video Page” account type supported by the Pardot Facebook connector. This option is misleading and not a valid Facebook account type, making A incorrect.

B. Linked Instagram Pages (Incorrect):
The Pardot Facebook connector is designed for posting to Facebook accounts, not Instagram. While Facebook and Instagram are part of the same Meta ecosystem, and some business pages can be linked to Instagram accounts, the Pardot connector does not support direct posting to Instagram Pages. Instagram posting requires separate integrations (e.g., via third-party tools), making B incorrect.

C. Company Pages (Correct):
Company Pages (or Business Pages) on Facebook are supported by the Pardot Facebook connector. Marketers can connect a Company Page to Pardot and schedule posts, allowing for brand-aligned social media campaigns. This is a common use case for businesses, making C correct.

D. Personal Pages (Correct):
The Pardot Facebook connector also supports posting to Personal Pages, provided the user has access to the page and authenticates it via the connector. This allows individuals or small businesses using personal profiles for marketing to post directly from Pardot, making D correct.

In summary, C and D are correct because the Pardot Facebook connector supports posting to Company Pages and Personal Pages on Facebook. A and B are incorrect, as “Video Pages” is not a valid account type, and Instagram Pages are not supported by the Facebook connector. This question tests knowledge of Pardot’s social media integration capabilities.

Reference/Source:
Salesforce Help Documentation - “Social Posting in Marketing Cloud Account Engagement” (details the Facebook connector’s support for posting to Company and Personal Pages).

Explanation:

In Salesforce Marketing Cloud Account Engagement (Pardot), forms placed on landing pages are used to capture prospect data, such as registrations for events like a tradeshow. To track unique submissions for a form (i.e., the number of distinct prospects who have successfully submitted the form), administrators need a report that aggregates form submission data in the context of the landing page hosting the form. In Pardot, the Landing Page report provides metrics specific to landing page performance, including the number of unique form submissions for forms embedded on that page. This report is ideal for understanding how many unique prospects have engaged with the form on the tradeshow landing page.

Let’s analyze each option:

A. Form handler report (Incorrect):
Form Handlers in Pardot are used to process submissions from external (non-Pardot) forms, not native Pardot forms embedded on Pardot landing pages. Since the question specifies a “Marketing Cloud Account Engagement form” on a “Marketing Cloud Account Engagement landing page,” a Form Handler report is irrelevant, as it tracks external form submissions, not native form activity, making A incorrect.

B. Event report (Incorrect):
Pardot does not have a specific “Event report” as a standard report type. While custom reports could be created to track event-related activities (e.g., using tags or campaign data), there’s no dedicated Event report that directly tracks form submissions on a landing page. This option is misleading and not applicable to the scenario, making B incorrect.

C. Form report (Incorrect):
The Form report in Pardot provides detailed metrics about a specific form, such as total submissions, unique submissions, and conversion rates, regardless of where the form is embedded (e.g., on multiple landing pages or websites). While it does show unique submissions, it aggregates data across all instances of the form, not specifically for the form on the tradeshow landing page. The Landing Page report is more precise for this context, as it isolates submissions to the specific landing page, making C less suitable.

D. Landing page report (Correct):
The Landing Page report in Pardot (found under Reports > Landing Pages) provides metrics specific to a landing page, including the number of unique form submissions for any forms embedded on it. For the tradeshow landing page, this report will show how many distinct prospects submitted the form, aligning perfectly with the administrator’s need to track unique submissions for that specific page.

In summary, D is correct because the Landing Page report directly provides the number of unique form submissions for the form on the tradeshow landing page. A, B, and C are incorrect, as they either apply to unrelated assets (Form Handlers), don’t exist as standard reports (Event report), or are too broad (Form report). This question tests knowledge of Pardot’s reporting capabilities and their application to specific assets.

Reference/Source:
Salesforce Help Documentation - “Landing Page Reports in Marketing Cloud Account Engagement” (describes how Landing Page reports track metrics like unique form submissions for forms on specific landing pages).

Explanation:

📝 Question Explanation:
This is a specific question about the campaign attribution logic used by the Salesforce connector when it automatically creates a new Opportunity in Salesforce from a Pardot-connected prospect.

💡 Why This is Correct:

Option B: The first campaign of the first contact associated with the opportunity ✅
Account Engagement uses a specific order of operations for attribution. It looks at the first Contact (in alphabetical order by ID) associated with the Opportunity and then assigns the first Campaign (by Campaign ID) that this Contact was associated with. This ensures a consistent, though very specific, attribution model.

❌ Why These Are Incorrect:

Option A: The last campaign of the last contact ❌
The logic does not use the "last" of anything. It specifically uses the "first" contact and the "first" campaign from that contact's record.

Option C: The first campaign of the last contact ❌
The connector does not use the "last" contact. It identifies the first contact alphabetically by their Salesforce record ID.

Option D: The last campaign of the first contact ❌
While it uses the "first contact," it does not use that contact's "last" campaign. It uses the "first campaign" associated with that contact's record.

🔗 Reference:
Salesforce Help: "How Campaigns are Assigned to Opportunities"

Explanation:

📝 Question Explanation:
This scenario requires diagnosing why a large number of prospects were automatically added to the 'Do Not Email' list after an email send. The key is to identify which email metrics directly correlate with prospects becoming unmarketable.

💡 Why This is Correct:

Option D: Total Opt Outs and Hard Bounces ✅
Total Opt Outs shows how many recipients actively clicked the unsubscribe link, which automatically marks them as 'Do Not Email'. Hard Bounces indicate invalid, non-existent, or permanently closed email addresses, which the system will also mark as 'Do Not Email' to protect sender reputation.

❌ Why These Are Incorrect:

Option A: Total Sent and Suppression Rate ❌
Total Sent shows volume, and Suppression Rate shows how many were removed from the send, but it doesn't explain why they were suppressed (e.g., could be due to an existing 'Do Not Email' status before the send).

Option B: Click-Through Rate and Soft Bounces ❌
A high click-through rate is positive engagement. Soft bounces are temporary delivery issues (like a full inbox) and do not result in a 'Do Not Email' status.

Option C: Tracker Domain Verification and Open Rate ❌
Tracker domain status is a configuration setting, and open rate measures engagement. Neither of these metrics explains why a prospect becomes unsubscribed or invalid.

🔗 Reference:
Salesforce Help: "View Email List Reports"