Process Automation and Logic: Free PD1 Practice Questions

Question 1

A developer needs to write a method that accepts a List<String> of product names and returns how many unique product names exist in the list. The method should use the fewest lines of code possible. Which approach accomplishes this?

Add all elements from the List into a new Map<String, Integer>, then return the Map's size() value Add all elements from the List into a new Set<String>, then iterate through the Set and increment a counter variable Iterate through the List and use contains() to build a second List of unique values, then return its size() Add all elements from the List into a new Set<String>, then return the Set's size() value

Correct Answer: Add all elements from the List into a new Set<String>, then return the Set's size() value

Adding all List elements to a new Set automatically removes duplicates since Sets only store unique values, so calling size() on the Set directly returns the count of unique product names in the fewest lines of code.

Using a Map to track counts works but requires unnecessary complexity and more code. Iterating with contains() to build a second List is verbose and inefficient. Adding to a Set but then iterating with a counter is redundant since size() already provides that value directly.

Key concept tested: understanding that Set collections inherently enforce uniqueness and provide a concise way to deduplicate data in Apex.

Question 2

In Apex, which keyword is used in a traditional for loop to move to the next iteration of the loop, skipping the remaining code in the current iteration?

The 'next' keyword advances to the following loop iteration The 'break' keyword advances to the next loop iteration The 'continue' keyword advances to the next loop iteration The 'continue' keyword terminates the loop and returns to the caller

Correct Answer: The 'continue' keyword advances to the next loop iteration

In Apex, the 'continue' keyword skips the remaining code in the current iteration of a loop and immediately moves execution to the next iteration, making it the correct answer.

The 'break' keyword does not advance to the next iteration; instead, it terminates the entire loop and continues execution after the loop block. The 'next' keyword does not exist in Apex as a loop control statement. One option incorrectly describes 'continue' as terminating the loop and returning to the caller, which is actually what 'return' or 'break' would do, not 'continue'.

The key concept tested is understanding Apex loop control flow statements, specifically the distinction between 'continue' and 'break'.

Question 3

A developer writes a before update trigger on the Account object. Inside the trigger, they loop through Trigger.new and check if a field called Status__c has changed. They use the following condition: if (acc.Status__c != Trigger.oldMap.get(acc.Id).Status__c). The trigger compiles and runs successfully. A junior developer asks: what type of collection is Trigger.oldMap?

A Map<Id, sObject> that maps each record's Id to a cloned copy of the record before any workflow rules execute A Map<String, sObject> that maps each record's Name field to the previous version of the record A Map<Id, sObject> that maps each record's Id to the newly modified version of the record A Map<Id, sObject> that maps each record's Id to the previous version of the record

Correct Answer: A Map<Id, sObject> that maps each record's Id to the previous version of the record

Trigger.oldMap is a Map that contains the previous versions of the records before the update was initiated, allowing developers to compare old field values against new ones in Trigger.new.

The option describing the newly modified version is wrong because that describes Trigger.newMap, not Trigger.oldMap. The option using Map keyed by Name is wrong because trigger context variable maps are always keyed by record Id, not Name. The option mentioning cloned copies before workflow rules is wrong because Trigger.oldMap contains the database state before the current DML operation, not specifically tied to workflow rule execution.

Key concept tested: understanding Apex trigger context variables, specifically Trigger.oldMap and its role in detecting field changes.

Process Automation and Logic

PD1 - Process Automation and Logic Example Questions

Question 1

Question 2

Question 3

Code on the Salesforce Platform