* @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<ContactInfo>.
* Why Option C?
* Fulfills all @InvocableMethod requirements:
@InvocableMethod(label='Additional Info')
public static List<ContactInfo> getInfo(List<Id> 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: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta
/apexcode/apex_classes_annotation_InvocableMethod.htm
References:

An Apex REST class can be used to retrieve real-time data from an external order management system. The flow can then call the REST class to display the retrieved data on the screen dynamically.

* Change sets can only be used between related organizations:
* Change sets require a relationship between the source and target Salesforce orgs, such as a production org and its sandboxes. You cannot use change sets between unrelated Salesforce orgs.

* The Boolean isOK variable is declared but not initialized, meaning its value is null by default in Apex.
* The code evaluates the if-else conditions in sequence:
* Condition 1: isOK == false && theString == 'Hello'
* isOK is null, so this evaluates to false.
* Condition 2: isOK == true && theString == 'Hello'
* Again, isOK is null, so this evaluates to false.
* Condition 3: isOK != null && theString == 'Hello'
* isOK is null, so isOK != null evaluates to false.
* Else block: None of the above conditions are true, so the code enters the else block and sets x = 4.
References:
* Apex Boolean Data Type

* A. Roll-up summary fields can cause the parent record to go through Save:
* When a roll-up summary field on a parent object (like Account) is updated due to changes in child records (like Branch), the parent record (Account) is implicitly saved again.
* This can result in the execution of the trigger on the parent object. Developers must consider this behavior to avoid unintended recursion or infinite loops.