PDT-101 Practice Questions

A Page Action is the most direct and efficient automation tool in Salesforce Account Engagement (formerly Pardot) for this specific scenario. It is designed to trigger a completion action, such as 'Add to List,' when a prospect views a specific page that contains the Account Engagement tracking code. This allows for real-time list building based on a prospect's specific web browsing behavior, like visiting a pricing page.

B. Create a segmentation rule: A segmentation rule runs only once to create a static list. It does not continuously add new prospects who visit the page after the rule has run.

C. Use a Tag: A tag is a label used for organization and segmentation, not an automated process. A process (like a page action) would be required to apply the tag in the first place.

D. Create an automation rule: While an automation rule could achieve this, it is a more resource-intensive tool designed for complex, multi-criteria scenarios. A Page Action is the purpose-built, simpler tool specifically for this use case.

1. Salesforce Help, Account Engagement Documentation, "Page Actions": "Use page actions to create a completion action that is triggered by a prospect’s page view. You can apply page actions to any page that contains your Account Engagement tracking code." This document explicitly lists "Add to list" as a possible completion action.

2. Salesforce Help, Account Engagement Documentation, "Considerations for Page Actions": This section details the setup process, confirming that a Page URL is the trigger and a completion action (like adding to a list) is the result.

3. Salesforce Help, Account Engagement Documentation, "Automation Tools Overview": This guide compares automation tools. It defines Page Actions as the tool to "Trigger completion actions from a page view," distinguishing it from Segmentation Rules which "Build a list one time based on criteria" and Automation Rules which "Create criteria-based rules that are always looking for matching prospects." This clarifies why Page Action is the most appropriate choice.

Scoring in Salesforce Marketing Cloud Account Engagement (formerly Pardot) is a numerical measure of a prospect's interest and intent. It quantifies this interest by assigning points for specific actions and behaviors the prospect undertakes. These actions, or activities, include opening an email, clicking a link, viewing a pricing page, or submitting a form. The cumulative score reflects how engaged a prospect is with the company's marketing assets, helping to identify sales-ready leads. It is based on implicit data (what they do), not explicit data (who they are).

A. This describes grading, which evaluates how well a prospect matches an ideal customer profile based on explicit, personal, or firmographic information.

B. This is too specific. While website activity contributes to a score, scoring measures a much broader range of activities beyond just time spent.

D. This incorrectly merges the concepts of scoring (activities) and grading (explicit information), which are separate and distinct lead qualification mechanisms in Pardot.

1. Salesforce Help Documentation, Pardot Scoring. "A prospect’s score is a numerical value that indicates how interested they are in your product or service. A prospect’s score can increase or decrease based on their actions." This directly confirms that scoring is based on activities.

2. Salesforce Trailhead, Lead Qualification with Pardot Unit, Pardot Lead Nurturing Module. "A score is a numerical value assigned based on a prospect’s activity... It’s an indicator of how interested or active a prospect is." This resource explicitly defines score as a measure of activity.

3. Salesforce Help Documentation, Scoring and Grading Prospects. "Scoring is based on what a prospect does, and grading is based on who a prospect is." This official distinction clarifies that scoring is about activities ("what a prospect does"), while grading relates to personal information ("who a prospect is"), invalidating options A and D.

Engagement Studio programs are designed to be stateful, meaning they track and remember a prospect's progress. When a prospect no longer meets the criteria of a dynamic recipient list, they are effectively paused within the program at their last completed step. If the prospect's data changes again, causing them to re-match the list's criteria, they are added back to the list and resume the program exactly where they left off. Since the prospect had already completed Step 3, they will proceed to the next action in the workflow, which is Step 4.

A. The prospect will continue on the engagement program to Step 3.

This is incorrect because the prospect has already completed Step 3. The program will move them forward to the next step in the sequence, not repeat a completed one.

B. The prospect will begin the engagement program again on Step 1.

This is incorrect. By default, a prospect can go through a specific engagement program only once. Re-adding them to the list resumes their progress, it does not restart the program.

C. The prospect will be added to a suppression list used by the engagement program.

This is incorrect. Being removed from a recipient list simply pauses the prospect's journey. It is not an action that automatically adds them to a suppression list.

1. Salesforce Help Documentation, "Considerations for Using Lists with Engagement Studio."

Reference: Under the "Recipient Lists" section, the documentation states, "If a prospect is removed from the recipient list, they’re paused in the program. If the prospect is added to the list again, they resume the program where they left off." This directly supports the conclusion that the prospect continues from their last position.

2. Salesforce Help Documentation, "Start an Engagement Program."

Reference: In the "Notes on Starting Engagement Programs" section, it is noted, "A prospect can go through an engagement program only one time." This rule clarifies why the prospect would not restart at Step 1 (Option B). The exception requires an administrator to explicitly enable the "Allow prospects to reenter the program" setting, which is not the default behavior described in the scenario.

The standard and secure procedure for an administrator to grant a Pardot employee temporary access to their account is performed directly within the Pardot application interface. This self-service method ensures that the account administrator maintains control and can set a specific duration for the access, typically for troubleshooting or support purposes. The action is logged for auditing and security. The designated path is to navigate to the user settings, typically represented by a person icon, and select the specific "Grant Account Access" option from the menu.

A. By calling Pardot Support.

This is an indirect method. Support personnel would guide the administrator to grant access through the user interface themselves, rather than performing the action on their behalf.

B. By emailing Pardot Support.

Similar to calling, this is a communication step, not the direct action. The secure protocol requires the administrator to explicitly grant access from within their own authenticated session.

C. By contacting Pardot Success Specialist.

Contacting a specialist is for strategic guidance. For technical access, they would direct the administrator to use the built-in "Grant Account Access" feature in the application.

1. Salesforce Help Documentation: Grant Account Access. This document explicitly outlines the procedure: "To grant access to your account, hover over the person icon, and then select Grant Account Access. Select the access duration from the dropdown. Click Grant Access." This is the primary, official vendor documentation for this function.

2. Trailhead by Salesforce: Pardot Basics Module, Account Administration Unit. This official training module covers fundamental administrative tasks. The section on "Pardot Support" details that administrators can grant access to support for a specified period directly within their Pardot settings, reinforcing the in-app procedure.

The Salesforce connector for Marketing Cloud Account Engagement (formerly Pardot) acts as a bridge, allowing data to sync between the two platforms. This connection is established through a designated Salesforce user, known as the "connector user." To authenticate this connection and grant Account Engagement the necessary permissions to access and modify Salesforce data, the setup process requires the Salesforce username, password, and security token of this specific connector user. This user's profile and permission sets in Salesforce dictate the scope of data that can be synced.

A. The Administrator’s Pardot credential

The connection authenticates into Salesforce to access its data; therefore, Salesforce credentials, not Account Engagement (Pardot) credentials, are required for verification.

B. The Administrator’s Salesforce credential

While an administrator can be the connector user, it is not a requirement and is often not the best practice. The credential must belong to the designated connector user, regardless of their profile.

D. The connector user’s Pardot credential

The connector needs to prove its identity to Salesforce, not to Account Engagement (Pardot). Thus, it requires the user's Salesforce credentials to establish the connection.

1. Salesforce Official Documentation, "Considerations for a Connector User":

Reference: In the overview section, the document states, "The connector user is a specific Salesforce user whose credentials are used to grant Pardot access to your Salesforce org’s data." This directly confirms that the connector user's Salesforce credentials are required.

Source: Salesforce Help, Document ID: 000384891, "Considerations for a Connector User".

2. Salesforce Official Documentation, "Set Up the Salesforce Connector, v2":

Reference: In the "Connect Pardot to Salesforce" section, Step 5 explicitly instructs the administrator to: "Enter the credentials for your Salesforce connector user." This step is a mandatory part of the verification process.

Source: Salesforce Help, Document ID: 000384893, "Set Up the Salesforce Connector, v2".

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.

The Identified Companies table, a standard component on the Pardot (now Marketing Cloud Account Engagement) dashboard, is designed to show recent activity from anonymous visitors. For each company identified through reverse IP lookup, the table displays information for the single most recent visitor from that organization. This provides a concise view of which accounts are showing interest, focusing on the latest engagement rather than a comprehensive list of every visitor from that company.

A. The table is designed for a high-level overview and intentionally shows only the most recent visitor, not all of them, to remain concise.

C. The system is not configured to show a fixed number of two visitors; it is designed to display only the single most recent one.

D. The system is not configured to show a fixed number of three visitors; it is designed to display only the single most recent one.

1. Salesforce Help Documentation, "Pardot Dashboard": In the section describing the "Identified Companies" component, the documentation states, "The table shows the most recent visitor from the company, how many pages they viewed, and when they last viewed a page." This confirms that only one visitor is displayed per company. (Salesforce Help, Document ID: 000385103, "Pardot Dashboard").

2. Salesforce Help Documentation, "Visitors Report": This report provides more detailed information on anonymous visitors. The dashboard component, however, is a summary. The documentation for the Visitors Report clarifies its comprehensive nature, which contrasts with the dashboard's summary view. The Identified Companies table on the dashboard specifically isolates the latest activity per company. (Salesforce Help, Document ID: 000385107, "Visitors Report").

The sequence of events begins when an anonymous visitor, tracked by a cookie, clicks a custom redirect. This action queues a completion action (to add a tag). When the same visitor submits a form, they are converted into a prospect. This conversion event triggers three primary outcomes:

1. The form submission itself is recorded as a key event in the new prospect's activity history (A).

2. The form's configured completion action executes immediately, adding the prospect to the specified list (B).

3. The previously queued completion action from the custom redirect click is now applied to the identified prospect, adding the tag (D).

All prior anonymous activities are merged with the new prospect record upon conversion.

C. While the custom redirect click is indeed associated with the new prospect's activity history, the form submission (A) and the two direct data modifications (B, D) represent the most significant outcomes of the conversion event.

E. This is incorrect. The first submission is the critical event that converts an anonymous visitor into an identified prospect, triggering all associated actions and activity consolidation.

1. Salesforce Help, Account Engagement Documentation, "How Visitors Become Prospects": This document explains the conversion process. It states, "When a visitor submits a form... Pardot creates a prospect record... All of the visitor’s previous activity is converted to prospect activity and is shown in the prospect record." This supports that both the form submission (A) and the prior custom redirect click (C) will be in the prospect's activities.

2. Salesforce Help, Account Engagement Documentation, "Completion Actions": This resource details how completion actions function. It specifies, "Completion actions are triggered by... form submissions, ...custom redirect clicks... When a visitor or prospect completes the action, the completion action is applied to their record." This confirms that the actions to add to a list (B) and add a tag (D) will both be executed. The action from the custom redirect is queued until the visitor is identified.

3. Salesforce Help, Account Engagement Documentation, "Track Clicks with Custom Redirects": This page confirms that custom redirects can have completion actions. It notes, "You can also add completion actions that fire after a prospect clicks the redirect." This supports the premise that the tagging action (D) is a valid outcome.

A Pardot (now Marketing Cloud Account Engagement) business unit is architecturally designed to have a one-to-one relationship with a single Salesforce organization. This fundamental design ensures data integrity, a single source of truth for prospect and customer data, and reliable synchronization between the marketing automation platform and the CRM. Consequently, only one Salesforce connector can be active and verified for a single Pardot instance at any given time. To connect to multiple Salesforce orgs, a company would need to provision multiple Pardot business units.

B. 2: The system is not designed for a one-to-many connection; a single Pardot instance cannot sync with two separate Salesforce orgs.

C. 5: This is an arbitrary number and does not reflect the technical limitations of the Pardot-Salesforce connector architecture.

D. Unlimited: Allowing unlimited connectors would be technically infeasible and would create significant data management and integrity issues.

1. Salesforce Help Documentation. Considerations for Using the Salesforce Connector. Under the "Connector Settings" section, the documentation explicitly states, "A Pardot business unit can have only one Salesforce connector." This confirms the 1:1 relationship.

2. Salesforce Help Documentation. Pardot Multiple Salesforce Orgs Architecture. This document outlines solutions for customers with multiple Salesforce orgs, reinforcing the core principle: "Each Pardot Business Unit can connect to only one Salesforce Org." This architecture guide clarifies that separate Pardot instances are required for each Salesforce connection.

The most effective and standard method in Pardot (Marketing Cloud Account Engagement) to collect information from prospects for a specific initiative, such as a product launch, is by using a form hosted on a landing page. A landing page provides a focused, campaign-specific destination for prospects. The embedded form is the primary tool designed to capture prospect data, such as their name, email, and interest level, converting anonymous visitors into known prospects or updating existing records. This combination directly addresses the core requirement of "collecting information."

A. Engagement program with product launch details.

An Engagement Program is a nurturing tool used to send a series of automated communications to prospects over time; it does not directly collect information.

B. Email template with a form embedded into the HTML.

Embedding forms directly into emails is not a reliable practice, as most email clients block form functionality for security reasons, preventing submissions.

C. Landing page without a form.

A landing page without a form is purely informational. It cannot fulfill the primary requirement of the question, which is to collect prospect information.

1. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Pardot Landing Pages": "Use landing pages to collect information about your visitors and turn anonymous visitors into identified prospects. A landing page is a web page that a visitor typically reaches after clicking a link or advertisement. This page generally displays content that is specific to the ad, search keyword, or link clicked." This source confirms that the primary purpose of a landing page is to host content and collect information, typically via a form.

2. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Pardot Forms": "Pardot forms are the key to conversion. Use them on your landing pages and website to collect information about your visitors and turn anonymous visitors into identified prospects." This document explicitly states that forms are the mechanism for collecting information and are used on landing pages.

3. Salesforce Help, Marketing Cloud Account Engagement Documentation, "Engagement Studio": "Engagement Studio is the true intelligence engine of Marketing Cloud Account Engagement, allowing you to build complex, multi-path prospect nurturing campaigns." This reference defines Engagement Programs as tools for nurturing, not for initial data collection.