CERTIFIED TIA-942 DESIGN CONSULTANT
CTDC EXAM 2026 FULL PRACTICE
QUESTIONS AND ANSWERS
◉ Disable Specific Pieces of Code Answer: You might need to disable
code when you:
Import large sets of data (many thousands of records at once)
Integrate with external systems
Troubleshoot code errors
◉ Create Your Own Custom Code Answer: If you're developing your
own custom Apex code or integrating an external system with
Salesforce, you should familiarize yourself with the TDTM
architecture. Salesforce and many expert developers recommend
that you have only ONE trigger for each object (one for Contacts, one
for Accounts, and so on).
When you learn how to extend TDTM functionality into your code,
you don't need to create new triggers—you just use the trigger that
already exists in TDTM to pass environment data to your custom
Apex classes. By using the existing TDTM infrastructure instead of
creating your own, you get the most reliable and efficient behavior
as a result.
,◉ Control the Order In Which Your Code Executes Answer: Apex
triggers do not come with a way to control the order of operation
but TDTM fills that gap.
◉ Map Recurring Donation Fields to Custom Opportunity Fields
Answer: You can use Recurring Donations Custom Field Mapping to
copy custom fields from Recurring Donation records to child
Opportunity records whenever you create a new recurring donation.
You may want to do this so that details from the Recurring Donation
record appear in child Opportunity records as well for easy
reference or billing.
Mapping requires that you have two fields (one on the Recurring
Donation and one on the Opportunity) of a matching type in order to
create a mapping between them.
◉ Aggregate Rollups Answer: Summarize data from multiple records
and roll it up to a target field. Aggregate Rollups are used for
summing, averaging, or counting. For example, NPSP comes with
aggregate rollups for Total Gifts (summing), Average Gift Amount
(averaging), and Total Number of Gifts (counting).
◉ Single Result Operation Rollups Answer: Copy data from a field on
a single record to the target field. These rollups are used for
searching through a group of records to find the first or last date, or
,finding the smallest or largest number (currency, number, etc) and
copying data from that record. Out-of-box in NPSP, you get single
result operations such as Largest Gift Amount, First Gift Date, and
Last Gift Date. But, with Customizable Rollups, you can select any
field from the single Opportunity (or Payment) result and copy it to
the target object. A great example that wasn't possible before is that
you can configure a rollup to automatically copy the record ID of that
found single record, and add it to a custom lookup field on the target
object (for example, a Contact or Account record). That way you can
easily click through to see the record itself (and find any information
you need)! With that lookup, you can also create cross-object
formula fields to pull any data you need from that Opportunity or
Payment to the Contact or Account.
◉ In NPSP, soft credits (including any partial soft credits) and soft
credit rollups are tracked on Contacts. Answer: With Customizable
Rollups, all of the Contact Soft Credit Rollup fields still exist, but the
rollups that populate them are now defined in Customizable Rollups.
Users can edit the existing ones or create new ones.
◉ With Customizable Rollups, we also offer the ability to roll up
Account soft credits. Answer: An Account soft credit is a credit for a
donation that the Account didn't actually make, but may have
somehow influenced. For example, a Donor Advised Fund uses a
bank to manage their money. When a donation comes from the
Donor Advised Fund, the check is actually generated by the bank, so
the bank gets the hard credit for the donation. Using Account soft
credits, you can ensure that the Donor Advised Fund gets a soft
, credit for their donation, and you can roll up those soft credits to the
Account.
◉ We can create Customizable Rollups that roll up all Contact level
soft credits to the Household Account. Answer: These soft credits are
valuable if you want to be able to see the total giving for an entire
Household. For example, you may have major donors that give on an
annual basis, but the money is coming from a donor advised fund or
family foundation (not their personal checkbook) managed by a
financial institution. Thus, all donations come directly from that
financial institution. This results in hard credits and the majority of
the rollups pointing to the financial institution (for accounting
reasons), which makes it hard to fully realize the amount of money
the Contact or Household has given when you view their records in
NPSP.
◉ Pardot
A static list consists of prospects that you build once and edit
manually to make changes. A dynamic list is rule-based and
automatically updates when a prospect's data changes. Answer: The
benefit of a dynamic list is that it's created based on criteria and
updates as prospects meet or fail to meet the criteria. a dynamic list
is are most helpful when you are creating a list based on prospect
data that changes often.
◉ You can't convert a static list to a dynamic list. Answer: Use a
static list when you have no reason to remove prospects, such as a
CTDC EXAM 2026 FULL PRACTICE
QUESTIONS AND ANSWERS
◉ Disable Specific Pieces of Code Answer: You might need to disable
code when you:
Import large sets of data (many thousands of records at once)
Integrate with external systems
Troubleshoot code errors
◉ Create Your Own Custom Code Answer: If you're developing your
own custom Apex code or integrating an external system with
Salesforce, you should familiarize yourself with the TDTM
architecture. Salesforce and many expert developers recommend
that you have only ONE trigger for each object (one for Contacts, one
for Accounts, and so on).
When you learn how to extend TDTM functionality into your code,
you don't need to create new triggers—you just use the trigger that
already exists in TDTM to pass environment data to your custom
Apex classes. By using the existing TDTM infrastructure instead of
creating your own, you get the most reliable and efficient behavior
as a result.
,◉ Control the Order In Which Your Code Executes Answer: Apex
triggers do not come with a way to control the order of operation
but TDTM fills that gap.
◉ Map Recurring Donation Fields to Custom Opportunity Fields
Answer: You can use Recurring Donations Custom Field Mapping to
copy custom fields from Recurring Donation records to child
Opportunity records whenever you create a new recurring donation.
You may want to do this so that details from the Recurring Donation
record appear in child Opportunity records as well for easy
reference or billing.
Mapping requires that you have two fields (one on the Recurring
Donation and one on the Opportunity) of a matching type in order to
create a mapping between them.
◉ Aggregate Rollups Answer: Summarize data from multiple records
and roll it up to a target field. Aggregate Rollups are used for
summing, averaging, or counting. For example, NPSP comes with
aggregate rollups for Total Gifts (summing), Average Gift Amount
(averaging), and Total Number of Gifts (counting).
◉ Single Result Operation Rollups Answer: Copy data from a field on
a single record to the target field. These rollups are used for
searching through a group of records to find the first or last date, or
,finding the smallest or largest number (currency, number, etc) and
copying data from that record. Out-of-box in NPSP, you get single
result operations such as Largest Gift Amount, First Gift Date, and
Last Gift Date. But, with Customizable Rollups, you can select any
field from the single Opportunity (or Payment) result and copy it to
the target object. A great example that wasn't possible before is that
you can configure a rollup to automatically copy the record ID of that
found single record, and add it to a custom lookup field on the target
object (for example, a Contact or Account record). That way you can
easily click through to see the record itself (and find any information
you need)! With that lookup, you can also create cross-object
formula fields to pull any data you need from that Opportunity or
Payment to the Contact or Account.
◉ In NPSP, soft credits (including any partial soft credits) and soft
credit rollups are tracked on Contacts. Answer: With Customizable
Rollups, all of the Contact Soft Credit Rollup fields still exist, but the
rollups that populate them are now defined in Customizable Rollups.
Users can edit the existing ones or create new ones.
◉ With Customizable Rollups, we also offer the ability to roll up
Account soft credits. Answer: An Account soft credit is a credit for a
donation that the Account didn't actually make, but may have
somehow influenced. For example, a Donor Advised Fund uses a
bank to manage their money. When a donation comes from the
Donor Advised Fund, the check is actually generated by the bank, so
the bank gets the hard credit for the donation. Using Account soft
credits, you can ensure that the Donor Advised Fund gets a soft
, credit for their donation, and you can roll up those soft credits to the
Account.
◉ We can create Customizable Rollups that roll up all Contact level
soft credits to the Household Account. Answer: These soft credits are
valuable if you want to be able to see the total giving for an entire
Household. For example, you may have major donors that give on an
annual basis, but the money is coming from a donor advised fund or
family foundation (not their personal checkbook) managed by a
financial institution. Thus, all donations come directly from that
financial institution. This results in hard credits and the majority of
the rollups pointing to the financial institution (for accounting
reasons), which makes it hard to fully realize the amount of money
the Contact or Household has given when you view their records in
NPSP.
◉ Pardot
A static list consists of prospects that you build once and edit
manually to make changes. A dynamic list is rule-based and
automatically updates when a prospect's data changes. Answer: The
benefit of a dynamic list is that it's created based on criteria and
updates as prospects meet or fail to meet the criteria. a dynamic list
is are most helpful when you are creating a list based on prospect
data that changes often.
◉ You can't convert a static list to a dynamic list. Answer: Use a
static list when you have no reason to remove prospects, such as a
