Explanation:

In Engagement Studio, suppression lists take priority over recipient lists. If a prospect is included in both, suppression wins, and the prospect will not receive emails. The only way for them to become eligible is by removing them from the suppression list while keeping them on the recipient list. Removal from both lists cancels eligibility altogether, and opting out blocks sends regardless of list membership.

Correct Option:

🚫 C. The prospect is removed from the suppression list
Suppression lists override recipient lists by design. To allow a prospect to receive program emails, they must remain in the recipient list but be removed from the suppression list. This action restores eligibility, ensuring the prospect flows into Engagement Studio sends.

Incorrect Options:

📉 A. The prospect is marked as opted out
An opted-out status is global, meaning the prospect cannot receive marketing emails at all, regardless of list membership. Removing them from suppression would not override an opt-out status.

❎ B. The prospect is removed from the recipient list
Without being in the recipient list, the prospect is no longer targeted by the Engagement Studio program, so they wouldn’t receive emails even if removed from suppression.

🔄 D. The prospect is removed from both the suppression list and the recipient list
Taking the prospect out of both lists disqualifies them entirely. No recipient membership means no eligibility for the program, making this option incorrect.

Reference:
Salesforce Help – Pardot Engagement Studio Lists

Explanation:

The scenario requires a list that updates automatically when a prospect’s status changes. A dynamic list continuously evaluates its rules—form completion plus opt-out status—and adjusts membership accordingly. Unlike automation rules or one-time table actions, dynamic lists ensure that if someone opts back in, they are automatically re-included, eliminating the need for manual adjustments or repeated automation triggers.

Correct Option:

⚡ B. Use a dynamic list to automatically add or remove prospects based on the form completion and their opt out status
Dynamic lists evaluate rules in real time. Prospects who complete the Contact Us form and remain opted in stay on the list, while those who opt out are removed. If a prospect later opts back in, they are automatically re-added, ensuring the list remains accurate without further admin intervention.

Incorrect Options:

🛠️ A. Use an automation rule
Automation rules run once per prospect. While they could add or remove based on criteria, they won’t continuously re-check changes like opting back in. This makes them unsuitable when the list must always stay in sync with current status.

📋 C. Use a completion action
Completion actions trigger only at the moment of form submission. They can add prospects to a list, but cannot remove them later if status changes. They also won’t re-add a prospect who opts back in after unsubscribing.

📊 D. Use table actions
Table actions are one-time updates, not ongoing automation. Running them manually to add or remove prospects would be inefficient and error-prone. They don’t deliver the self-updating behavior required in this scenario.

Reference:
Salesforce Help – Pardot Lists

Explanation:

When using Account Engagement, marketers can connect multiple social accounts for posting and tracking. Unlike email sending limits or CRM sync restrictions, Account Engagement does not restrict the number of connectors per platform. This flexibility allows organizations with multiple brand pages, regional accounts, or product lines to manage all of their social publishing from within the same system without running into connector caps.

Correct Option:

🌐 C. There is no limit of accounts per platform
Account Engagement places no hard cap on how many connectors you can establish for supported platforms like LinkedIn, Facebook, and Twitter. This design ensures scalability for large organizations running multiple social identities. Each connected account can publish, track clicks, and capture engagement data back into Pardot without the need to consolidate accounts.

Incorrect Options:

🔢 A. Five accounts per platform
There is no “five account” limitation in Pardot. This option may sound plausible because other tools sometimes impose caps, but Account Engagement’s structure supports as many connectors as needed.

👥 B. One account per user role, per platform
Connector access is not tied to user roles. Users may manage or authenticate connectors, but the number of connectors allowed per platform is not determined by assigned roles.

1️⃣ D. One account per platform
A single connector per platform would severely limit flexibility. Most companies run multiple business units or regional pages. Pardot explicitly allows multiple connectors, making this answer incorrect.

Reference:
Salesforce Help – Pardot Social Posting

Explanation:

📝 Question Explanation:
This question checks your understanding of the limitations of field synchronization between Salesforce and Account Engagement. Not all Salesforce field types can have their data passed through the connector to Pardot.

💡 Why This is Correct:

Option A: Lookup ✅
Lookup fields establish a relationship between two different Salesforce objects (e.g., linking a Contact to an Account). The connector cannot sync the data from the related object through a lookup field. To sync this data, you must create a custom formula field on the original object that pulls in the value.

❌ Why These are Incorrect:

Option B: Picklist ❌
Picklist fields are fully supported for synchronization. The values from a Salesforce picklist can be mapped to a Pardot dropdown field.

Option C: Number ❌
Number fields are fully supported for synchronization. Data from Salesforce number fields can be mapped to Pardot number fields.

Option D: Formula ❌
Formula fields are supported for synchronization. The connector syncs the calculated result of the formula, not the logic itself, which is often the preferred method for getting data into Pardot.

🔗 Reference:
Salesforce Help: "Field Sync Between Pardot and Salesforce"

Explanation:

📝 Question Explanation:
This question addresses the automated spam protection features in Account Engagement. Sometimes, a reCAPTCHA challenge appears on a form even when the marketer has not enabled it, which is a proactive security measure by the system.

💡 Why This is Correct:

Option A ✅
Account Engagement integrates with real-time databases of known spammers and suspicious IP addresses. If a form submission originates from an IP or source flagged in these databases, the system will automatically override the form's settings and display a reCAPTCHA to verify the submitter is a human and not a bot, protecting your data quality.

❌ Why This is Incorrect:

Option B ❌
Pinging a database of known prospects would not trigger a reCAPTCHA. Finding a match in your prospect database is the desired outcome of a form fill and would not be treated as a suspicious, spam-like activity requiring verification.

🔗 Reference:
Salesforce Help: "Add reCAPTCHA to a Form"