Exactprep PDI Questions

Why Validation Rule?

Validation rules are efficient for enforcing field-level conditions without requiring Apex or Flow.

A formula can check if the user’s profile is not "Sales Manager" and if the Lost Reason field is blank when Status is set to "Closed Lost".

Why Not Other Options?

A: Triggers are more complex and unnecessary for this simple validation.

C: Record-triggered flows are less efficient for field validations compared to validation rules.

D: Approval processes do not handle this type of field-level restriction.

Validation Rule Documentation:

References:

@InvocableMethod Requirements:

Must be declared as public static.

Must accept and return a List to support batch operations.

Return type should be compatible with Flow Builder, in this case, a List.

Why Option C?

Fulfills all @InvocableMethod requirements:

@InvocableMethod(label='Additional Info')

public static List getInfo(List contactIds) {

// Implementation

}

Why Not Other Options?

A, B, D: Do not adhere to the public static requirement or fail to use a List as input/output.

InvocableMethod Documentation:

References:

Lightning Web Components (LWCs) are the best choice for creating custom UI components in Salesforce. They provide robust features such as event handling and server-side communication, allowing for validation of user input before saving data.

Option B: Reusing event logic in the helper ensures cleaner and reusable code.

Option D: Handling low-level events in handlers and re-firing them as higher-level events allows for better abstraction and modularity.