Free PDT-101 Practice Test Questions and Answers (2026)

A custom redirect is a trackable link created in Pardot that is used for assets hosted on third-party sites, such as banner ads, social media posts, or links from partner websites. When a prospect clicks the custom redirect link associated with the banner ad, Pardot tracks the click as a touchpoint and cookies the prospect's browser before redirecting them to the final destination URL. This allows for precise tracking of engagement with specific marketing assets that are not on your own web properties.

A. Page action: Page actions trigger automation based on a prospect viewing a specific page on your own website where Pardot tracking code is present, not for clicks on external ads.

C. Campaign tracking code: This JavaScript snippet is placed on your own website pages to track visitor activity and associate it with a Pardot campaign; it cannot track clicks on external assets.

D. Landing page: A landing page is a destination page, often used for lead capture. While the banner ad could link to a Pardot landing page, the landing page itself doesn't track the initial click on the ad.

1. Salesforce Help. (2023). Custom Redirects. "Create custom redirects to track banner ad clicks, links from third-party sites, and links on social media... When a prospect clicks the link, you can access the data in Pardot reports and the prospect’s record."

2. Salesforce Help. (2023). Considerations for Using Custom Redirects. "Use custom redirects for links on third-party websites, such as a banner ad on a vendor’s site or a link on a social media post."

3. Salesforce Help. (2023). Page Actions. "Page actions are completion actions that are triggered by a prospect’s page views. You can apply page actions to any page that contains your Pardot tracking code." This confirms page actions are for pages you own and control.

The synchronization between a Pardot prospect and a Salesforce Lead or Contact record is based on two key identifiers. Initially, Pardot uses the prospect's email address as a unique identifier to find a matching Lead or Contact in Salesforce. If a match is found, the records are linked. If multiple records share the same email, Pardot syncs with the one that was most recently updated. Once this initial sync occurs, the Pardot prospect record is permanently tied to the Salesforce record using the unique Salesforce Lead or Contact ID. This ID then serves as the primary key for all future synchronization between the two specific records, ensuring a stable one-to-one relationship.

B. Shared Assigned User ID: The Assigned User ID identifies the owner of the record, not the prospect or contact themselves. Multiple records can be assigned to the same user, so it cannot be used as a unique sync key.

D. Shared tracking pixel: A tracking pixel is associated with a browser cookie to monitor a visitor's online activity. It is not a stable or unique identifier for a person's record in the CRM or marketing automation database.

1. Salesforce Help Documentation, "How Prospects Sync with Salesforce": This document outlines the fundamental relationship. It states, "When a Pardot prospect record is syncing with Salesforce for the first time, Pardot looks for a lead or contact record in Salesforce with a matching email address... After a prospect record is linked to a Salesforce record, it stays linked. The prospect record syncs only with that Salesforce record from then on." This confirms the use of both email address for initial matching and the subsequent link via the Salesforce record ID. (Refer to the sections on "Matching Behavior" and "The One-to-One Relationship").

2. Salesforce Help Documentation, "Considerations for Using the Salesforce Connector": This guide details the connector's behavior. Under the "Syncing Prospects" section, it clarifies, "Pardot uses email address to match prospects to existing lead or contact records. If there's no record with a matching email address, Pardot creates a lead record." This explicitly supports the email address as the matching criterion. It also implicitly supports the Salesforce ID by explaining how records, once linked, maintain that connection.

The fundamental difference lies in how membership is managed. A dynamic list is rule-based; prospects are automatically added or removed when their data changes to match or un-match the list's criteria. Consequently, you cannot manually add or remove a prospect from a dynamic list. In contrast, a static list is a fixed list where prospects must be added or removed explicitly, either through manual user action, an import, or a specific automation action (like a completion action or automation rule).

B. Both list types can be retroactive. A dynamic list is retroactive by default as it evaluates all existing prospects against its criteria upon creation. A static list can be made retroactive by using an automation rule that evaluates existing prospects.

C. This statement is the opposite of the correct functionality. Dynamic list membership is determined solely by its rules and cannot be manually updated, whereas static lists are designed for manual management.

D. Actions can be triggered when a prospect is added to either list type. An automation rule can be configured with the criteria "Prospect list | is | [list name]" for both static and dynamic lists to initiate subsequent actions.

1. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Static and Dynamic Lists."

This document states, "A dynamic list is rule-based... Prospects are added and removed automatically as their data changes. You can’t add or remove prospects from dynamic lists manually." This directly supports the first part of the correct answer (A).

It also states, "A static list consists of prospects that you add and remove manually." This supports the second part of the correct answer (A).

2. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Automation Rule Criteria Reference."

Under the "Prospect List" criteria, the documentation shows it can be used to evaluate if a "Prospect list | is | [list name]". This functionality is not restricted to only dynamic lists, proving that option D is incorrect as actions can be triggered for additions to static lists as well.

A prospect’s Pardot Campaign is set to track the first marketing touchpoint that generated them. The most direct and explicit method listed is during a prospect import (A). The Pardot import wizard requires the user to select a campaign to associate with all prospects in the CSV file. This action directly sets the Pardot Campaign field for each new prospect created through that import.

While the Google Analytics connector captures campaign data, it populates separate UTM fields (utmcampaign, utmsource, etc.), not the primary Pardot Campaign field itself, which is a distinct object relationship. Therefore, only the import process is a guaranteed event that sets the Pardot Campaign from the options provided.

B. The Google Analytics connector populates UTM text fields from a URL, not the Pardot Campaign lookup field. It tracks a different type of campaign data.

C. Adding a prospect to a static list is a segmentation action. It does not set or change the prospect's source campaign.

D. Associating a profile is part of the lead grading process to determine a prospect's fit. It is unrelated to tracking marketing touchpoints.

1. Salesforce Help. (2023). Import Prospects.

In the procedure for importing prospects, Step 4, "Campaign and Add to List," explicitly states: "From the Campaign dropdown, choose a campaign to associate with the prospects." This confirms that an import is an event that sets the Pardot campaign.

2. Salesforce Help. (2023). Connect Pardot to Google Analytics.

This document details that the connector captures data into five specific fields: Google Analytics Source, Medium, Campaign, Content, and Term. It clarifies, "These fields are separate from Pardot’s source and campaign fields." This confirms the connector does not set the Pardot Campaign field.

3. Salesforce Help. (2023). Pardot Campaigns.

This article defines a Pardot Campaign: "A Pardot campaign tracks the first touchpoint that a prospect has with your online marketing materials." It lists setting the campaign via tracking code, forms, and imports, reinforcing that these are the primary setting events.

For a new Salesforce lead to be created immediately as a Pardot prospect, two conditions are essential. First, the Salesforce connector setting "Automatically create prospects in Pardot if they are created as a Lead or Contact in Salesforce" must be enabled. This setting acts as the specific trigger for this real-time creation process. Second, the lead record itself must contain a valid email address. Pardot uses the email address as the unique identifier for all prospects, making it a fundamental prerequisite for a prospect record to be created under any circumstance. Without both the trigger and the required data, the immediate sync will fail.

A. The lead must meet the active Marketing Data Sharing criteria, but the "sync all" configuration is not strictly required. A more restrictive rule could still permit the sync.

B. The prospect ID is assigned by Pardot after the prospect is created. It is a result of the sync, not a prerequisite for it.

1. Salesforce Help, Document ID: 000385054, "Salesforce Connector Settings," Section: "Prospects." This document explicitly lists the setting mentioned in option D: "Automatically create prospects in Pardot if they are created as a Lead or Contact in Salesforce." It confirms this setting must be enabled to trigger prospect creation from Salesforce.

2. Salesforce Help, Document ID: 000385053, "Considerations for Using the Salesforce Connector," Section: "Syncing." This official guide states, "To create a Pardot prospect from a Salesforce lead or contact record, the record must have an email address." This confirms the requirement in option C is a fundamental prerequisite for the sync to occur.

3. Salesforce Help, Document ID: 000389393, "Marketing Data Sharing Rules," Section: "How Marketing Data Sharing Rules Work." This document explains that these rules act as a filter for which records can sync. This supports the reasoning that option A is incorrect because "sync all" is just one possible configuration; a lead matching any active rule would be eligible, making "sync all" not a mandatory condition.

Sender Policy Framework (SPF) records are a standard email authentication method managed at the domain level, not within the Salesforce application. An SPF record is a specific type of TXT record within a company's Domain Name System (DNS). While the Salesforce platform, under "Email Sending Domains," will report an error if the SPF record is missing or incorrect, the administrator must log into the company's DNS provider (e.g., GoDaddy, Cloudflare, AWS Route 53) to add or modify the entry. Salesforce only provides the required values and validates the external configuration.

A. Account Settings: This area within Salesforce is used to view the required DNS values and check the validation status, but not to edit the external DNS records themselves.

B. Dashboard: Dashboards are used for data visualization and reporting. They have no function related to the technical configuration of domain authentication records.

D. CRM: This is a general term. The specific action of modifying an SPF record occurs at the DNS level, which is a system external to the CRM application.

1. Salesforce Help Documentation, "Set Up Your Email Sending Domain": In the step-by-step guide for setting up an email sending domain in Marketing Cloud Account Engagement (Pardot), the instructions explicitly state, "Add the records to your DNS." This confirms the action takes place in the company's DNS, not within Salesforce settings. (Found under the section "Set Up Your Email Sending Domain").

2. Salesforce Help Documentation, "Considerations for Setting Up Email Sending Domains": This document clarifies the process, stating, "To complete the setup process, you must add TXT and/or CNAME records to your DNS provider." This directly attributes the responsibility of record modification to the DNS provider's interface. (Found in the overview section).

3. Salesforce Help Documentation, "Email Authentication": This guide explains the purpose of SPF and DKIM, noting that "Sender Policy Framework (SPF) is a DNS text entry that shows a list of servers that are permitted to send email on behalf of your domain." This defines SPF as a DNS entry, reinforcing that it must be managed where DNS is controlled. (Found in the "Sender Policy Framework (SPF)" section).

To troubleshoot why a prospect did not receive an Engagement Program email, an administrator must verify three key areas. First, check the prospect's overall mailability on the Overview tab (D) to ensure they are not opted-out or marked 'Do Not Email'. Second, confirm on the Lists tab (E) that the prospect is on the correct recipient list and not on any suppression lists used for that email send. Third, review the prospect's activity history, often found in a Lifecycle or Engagement History view (B), to confirm they entered the program before the email step was scheduled to execute. These three steps cover the most common reasons for non-delivery.

A. Check the Audits tab to see if the prospect was on the correct lists when the email was sent.

The Audits tab tracks field changes, which is less direct than the Lists tab for confirming current list membership and suppression status.

C. Check the Profile tab to make sure the prospect has the right engagement program profile.

A prospect's Profile is used for grading and segmentation based on persona (e.g., job title, industry), not for determining eligibility to receive an email in an engagement program.

References

1. Salesforce Help. Prospect Mailability.

Reference: This document details the fields that control a prospect's mailability, such as Do Not Email and Prospect Opted Out. It states, "If Do Not Email is checked, the prospect won’t receive any emails from Account Engagement, including operational emails." This directly supports checking the prospect's mailability status (Option D).

2. Salesforce Help. Considerations for Using Lists.

Reference: This documentation explains the function of recipient and suppression lists. It clarifies, "When you send a list email... you choose recipient lists and suppression lists." This confirms the necessity of checking a prospect's membership on both types of lists to determine send eligibility (Option E).

3. Salesforce Help. Engagement Studio Reporting and Troubleshooting.

Reference: In the "Troubleshoot Prospects in Engagement Studio" section, the guide explains how program timing affects prospects. It notes that prospects begin a program when they are added to the recipient list and that they will not experience steps that occurred before they joined. This validates checking the prospect's entry time relative to the email send (Option B).

4. Salesforce Help. Grading Prospects.

Reference: This article defines a profile as "a set of criteria used to grade a prospect on how well they fit your ideal customer." It is used for scoring, not for inclusion in an email send, which is typically based on list membership or automation rules. This confirms that checking the Profile tab is not a relevant troubleshooting step for this scenario (Option C).

Kiosk/Data Entry Mode is a specific setting for Pardot forms designed for scenarios like trade shows where multiple individuals submit information from a single device. When enabled, this mode prevents Pardot from placing a cookie in the browser after a form submission. This is critical because, without it, all subsequent submissions from that same browser would be incorrectly associated with the first prospect who filled out the form, overwriting their data. Kiosk Mode ensures each submission creates a new, unique prospect record, maintaining data integrity during high-volume, shared-device registrations.

A. reCAPTCHA: This is a security feature used to prevent spam and bot submissions, not to manage multiple unique prospect entries from a single computer.

C. Progressive Profiling: This feature shows new fields to known, returning prospects to gather more information over time, which is the opposite of registering many new prospects.

D. “Not you”? Link: This link allows a user to manually clear a cookied prospect's data, but Kiosk Mode is the correct administrative setting to automate this process for many users.

1. Salesforce Help & Training, Pardot Documentation, "Pardot Form Settings Reference".

Section: Completion Actions > Kiosk/Data Entry Mode.

Content: This section explicitly states, "Select Kiosk/Data Entry Mode if the form is on a public computer, such as at a trade show. This setting prevents prospect sessions from tracking to a single prospect record." This directly confirms the feature's purpose for the trade show scenario.

2. Salesforce Help & Training, Pardot Documentation, "Considerations for Using Forms".

Section: Kiosk Mode.

Content: The documentation advises, "When you use a form at a trade show or for data entry, enable Kiosk Mode. When Kiosk Mode is enabled, prospects who submit the form aren’t cookied." This reinforces that Kiosk Mode is the designated solution for this use case.

Verifying the Salesforce connector is a critical administrative task that establishes the data sync between Pardot (now Marketing Cloud Account Engagement) and Salesforce. This action is performed within the administrative settings of the Pardot account. The Pardot Administrator is the only standard user role with the necessary permissions to access and configure account-wide settings, including integrations and connectors. This role ensures that only authorized personnel can manage foundational system connections, maintaining data integrity and security.

A. Sales manager: This role is designed for managing sales teams and viewing reports, not for configuring system-level integrations like the Salesforce connector.

B. Sales: The Sales role has the most limited permissions, typically focused on accessing and managing assigned prospect records, and lacks administrative access.

C. Marketing: While this role has broad access to marketing assets and campaign management, it does not include permissions to manage or verify connectors.

1. Salesforce Help. "Account Engagement User Roles." Salesforce.com. Accessed October 26, 2023. In the "Default User Roles" table, the Administrator role is described as having access to "all settings, users, and prospect data," which includes the ability to "Administer connectors." The other roles (Marketing, Sales Manager, Sales) do not have this permission listed.

2. Salesforce Help. "Verify the Salesforce Connector for Account Engagement." Salesforce.com. Accessed October 26, 2023. The navigation path provided to verify the connector begins with "Open the Account Engagement Settings page and select Connectors," a section only accessible to users with the Administrator role. This procedural documentation implicitly confirms the required permission level.

Within Pardot (now Marketing Cloud Account Engagement), administrators can create custom fields to store data that is not captured by the standard default fields. This capability is limited to three specific objects: Prospect, Account, and Opportunity. These custom fields are essential for advanced segmentation, automation rules, dynamic content, and personalization, allowing marketers to tailor their engagement based on unique data points synced from Salesforce or collected directly through Pardot forms and landing pages.

A. Campaign, Opportunity, Prospect: Custom fields cannot be created on the Pardot Campaign object. Pardot Campaigns are primarily used for first-touch attribution and grouping marketing assets.

B. Case, Contact, Lead: These are Salesforce objects. While Contact and Lead fields can be mapped to Pardot Prospect fields, you do not create custom fields for these objects within Pardot.

C. Account, Prospect, User: Custom fields cannot be created for the User object within the Pardot settings interface. User management is handled separately from marketing data objects.

1. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Considerations for Using Custom Fields." This document explicitly states, "You can create custom fields for prospect, account, and opportunity records." This directly confirms that only these three objects support custom field creation within Pardot.

2. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Create Custom Prospect Fields." This guide provides the step-by-step process for adding custom fields specifically to the Prospect object.

3. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Create Custom Account Fields." This article details the procedure for creating custom fields on the Account object within Pardot to sync with corresponding Salesforce Account fields.

4. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Create Custom Opportunity Fields." This resource outlines the steps for creating custom fields on the Opportunity object in Pardot, which are then mapped to Salesforce Opportunity fields.

A dynamic list is fundamentally defined by its rule-based criteria. Its primary component is the ability to automatically add or remove prospects as their data changes to match or un-match these criteria, ensuring the list is always current. This makes option B a core characteristic.

Another key capability associated with dynamic lists is the "Split List" function. This allows a user to divide the members of a large dynamic list into several smaller, static lists. This is a common action used for A/B testing or creating targeted segments from a broader audience, making option D a valid component of its functionality.

A. This describes the behavior of a static list after its initial creation. A dynamic list continuously updates, adding and removing prospects whenever their data changes.

C. Actions are not components of the list itself. They are configured through separate tools like Automation Rules, which can use list membership as a criterion to trigger an action.

1. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Dynamic Lists": This document states, "A dynamic list is a 'smart' list that automatically adds and removes prospects based on criteria that you set... Prospects are added to and removed from dynamic lists as their data changes." This directly supports answer B and refutes A.

2. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Split a List": This source confirms, "You can split a static or dynamic list into smaller static lists." This directly supports answer D.

3. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Automation Rule Criteria Reference": This reference details how list membership can be used as a criterion for an automation rule (e.g., "Prospect list :: is :: [List Name]"). This clarifies that the action is part of the rule, not the list, refuting option C.

In Salesforce Account Engagement (formerly Pardot), a suppression list's function within an Engagement Studio program is to specifically prevent email sends to the prospects on that list. However, the prospect is not removed from the program's logic flow. They will continue to progress through the program's steps, and any non-email steps, such as actions (e.g., 'Add to List', 'Assign to User'), rules, or triggers, will still execute for them. Therefore, the prospect receives no emails, but other defined actions are still triggered.

B. This is only partially correct. While the prospect gets no emails, this answer omits the critical fact that they continue through the program and other steps still execute.

C. A suppression list explicitly prevents prospects from receiving emails, making this option the opposite of the expected behavior.

D. This is incorrect. The prospect is on a suppression list, which prevents emails, and no mechanism in this scenario would cause duplicate sends.

---

1. Salesforce Help & Training Documentation, "Considerations for Using Suppression Lists with Engagement Studio":

Section: Main Body

Content: "When you add a suppression list to an Engagement Studio program, prospects on the list don’t receive emails from the program. They continue to move through the program, and other actions still affect them." This directly confirms that emails are suppressed while other actions proceed.

2. Salesforce Help & Training Documentation, "Engagement Program Recipient and Suppression Lists":

Section: Main Body

Content: "Prospects on a program's suppression lists can be included on its recipient lists. These prospects enter the program, but they aren't sent emails." This reference supports the fact that prospects are not blocked from the program entirely, only from the email sends within it, allowing other logic to apply.

The Admin | Domain Management section in Pardot (now Marketing Cloud Account Engagement) is the centralized area for configuring all domains associated with the account. This includes adding and verifying new email sending domains. To authorize Pardot to send emails on behalf of a new domain, an administrator must add it here and then publish the provided SPF and DKIM records to the domain's DNS settings. This administrative step is crucial for email authentication and deliverability.

A. Marketing | System Emails: This area is used to customize the templates for operational emails, such as unsubscribe notifications or email preference center confirmations, not for adding sending domains.

B. Marketing | Email Sending Domains: While the task is to add an email sending domain, this is an administrative function. The 'Marketing' menu is for creating and managing marketing assets like campaigns and emails.

C. Admin | Security: This section is for managing user access, password policies, and IP whitelisting. It does not handle the configuration of email sending domains.

1. Salesforce Help Documentation: Add and Verify a Domain for Email Sending.

Reference: Under the "Add an Email Sending Domain" section, the first step explicitly states: "To add an email sending domain, open the Domain Management page. In Pardot, navigate to Admin | Domain Management." This directly confirms the correct navigation path.

2. Salesforce Help Documentation: Domain Management.

Reference: The overview section states: "The Domain Management page shows all the domains that you use for landing pages, forms, files, and email. From this page, you can add and validate new domains." This confirms that Domain Management is the correct location for this task.

The Google Analytics connector in Pardot is designed to capture and link UTM parameter data to prospect records. When a visitor first arrives on a tracked website from a URL containing UTM parameters (e.g., utmsource, utmmedium, utmcampaign), the Pardot tracking code captures this information. If that visitor later converts into a prospect by submitting a form, the connector populates the corresponding Google Analytics fields on the new prospect record. This provides valuable first-touch attribution data, allowing marketers to identify which campaigns are effectively generating leads.

A. Syncing prospects with Google AdWords (now Google Ads) is the function of the separate Google Ads connector, which tracks paid search cost and ROI, not the Google Analytics connector.

B. Sending emails from Gmail is a feature enabled by integrations like Salesforce Inbox or other email client plugins, and is unrelated to the Google Analytics connector's functionality.

C. The connector's primary data flow is from the visitor's session to Pardot. It does not push conversion data from Pardot back to update fields within the Google Analytics platform.

1. Salesforce Help, "Connect Pardot to Google Analytics." This document explicitly states, "The Google Analytics connector connects Pardot to your Google Analytics account to track data from your UTM parameters. When a visitor comes to your site from a link tagged with UTM parameters, Pardot captures the parameters and stores them in the prospect’s record."

2. Salesforce Help, "Considerations for Using the Google Analytics Connector." This guide clarifies the mechanism: "The connector captures UTM parameters from a prospect’s first touchpoint and syncs them to the prospect record." It details the specific fields populated: Google Analytics Source, Medium, Campaign, Content, and Term, confirming the function described in option D.

3. Salesforce Help, "Google Ads Connector." This documentation outlines the purpose of the Google Ads connector, which is to "connect to a Google Ads account to track your paid search efforts." This confirms that syncing with Google Ads (formerly AdWords) is a separate function from a different connector, invalidating option A.

A prospect record sync from Pardot (now Marketing Cloud Account Engagement) to Salesforce is initiated by specific prospect activities that indicate active interest or by explicit user action. Both submitting a form and submitting a landing page that contains a form are primary, prospect-initiated activities that trigger this synchronization. When these events occur for an unassigned prospect, Pardot queues the record to sync and create a corresponding Lead or Contact in Salesforce, provided a matching record does not already exist and the prospect is assigned to a user.

C. Mapping new custom fields: This is an administrative action. It prompts the administrator with an option to manually start a mass sync for all prospects, but it is not an automatic, event-driven trigger for an individual record.

D. Opening an email: An email open is considered a passive activity and does not trigger a sync. A more engaged action, such as clicking a tracked link within a Pardot email, is required to initiate a sync.

1. Salesforce Help, Account Engagement Documentation, "Prospect Syncing Between Pardot and Salesforce": This document explicitly lists the activities that trigger a sync. Under the section "Sync Triggers," it states, "A prospect record syncs from Account Engagement to Salesforce when a user takes an action that requires a sync." The list of prospect activities includes:

Form submission

Form handler submission

Landing page submission

Custom redirect click

2. Salesforce Help, Account Engagement Documentation, "Considerations for Using Pardot Forms": This guide reinforces that form submissions are a key mechanism for data capture and initiating CRM integration. Section "Form Submission and Syncing" details how a successful form completion is a direct trigger for syncing with Salesforce.

3. Salesforce Help, Account Engagement Documentation, "Considerations for Custom Prospect Fields": This document clarifies the process for field mapping. In the "Syncing Custom Field Values" section, it explains, "When you map a prospect field to a Salesforce field, you can choose to sync your entire prospect database..." This confirms the action is an optional, administrator-initiated bulk process, not an automatic trigger for a single prospect record based on the mapping event itself.