Last Attempt PDI Questions

When using the @InvocableMethod annotation in Apex, there are specific considerations to keep in mind:

Option A: Only one method using the @InvocableMethod annotation can be defined per Apex class.

True.

Explanation:

An Apex class can contain only one method annotated with @InvocableMethod.

This ensures that when the class is invoked from a flow or process, there is no ambiguity about which method to execute.

In the provided class:

public class myClass {

public void myMethod() { /* implementation */ }

}

The class myClass is declared without any sharing keyword (with sharing, without sharing, or inherited sharing).

Default Sharing Behavior:

Apex classes without an explicit sharing declaration run in system context, meaning they do not enforce sharing rules.

Option B: Sharing rules will not be enforced for the running user.

Explanation: Since myClass does not specify with sharing, methods within it execute without enforcing sharing rules, allowing access to all data irrespective of the running user's sharing rules.

To efficiently prevent users (except those with the Sales Manager profile) from changing the Opportunity Status to Closed Lost when the lost reason is blank:

Option D: An error condition formula on a validation rule on Opportunity

Validation rules are designed to enforce data integrity by preventing users from saving records that don't meet certain criteria. They are efficient and declarative.

Validation Rule Formula:

AND(

ISPICKVAL(StageName, "Closed Lost"),

ISBLANK(Lost_Reason__c),

$Profile.Name <> "Sales Manager"

)



Option C: Handle low-level events in the event handler and re-fire them as higher-level events.

True.

Explanation:

It's a best practice to encapsulate lower-level events and re-emit them as higher-level, application-specific events to decouple components and simplify event handling.