The most accurate evaluation criteria for this use case is:
B). # "When a record is created, and any time it's edited to subsequently meet criteria" This ensures that the rule triggers:
When the record is first created and meets the criteria
Or when it is edited later, and the condition (Stage = Closed Lost and Amount > $1,000,000) becomes true Incorrect Options:
A). Could cause the action to trigger multiple times even when the criteria remains true.
C). Only runs once at record creation.
D). Is not a valid listed option in Workflow Rule settings.
Reference Extract from Salesforce Help - Workflow Rule Considerations:
"Use ' created, and any time it ' s edited to subsequently meet criteria ' when actions should only happen once per record per condition."

In Flow Builder, to assign a value (such as a Contact ID) to a field in a record variable, the Assignment element is used. It allows flow designers to modify the contents of variables, including record variables and individual fields within them.
C). Correct - The Assignment element sets values within variables, including record-type variables such as setting contactId = {!record.ContactId}.
Incorrect Options:
A). Decision is used for conditional branching, not for setting values.
B). "Branching Element" is not a Salesforce Flow term.
D). Create Records is used to insert records into the database, not to assign field values in variables.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use Assignment elements to assign values to variables and record fields in your flow."
"You can assign values to one or more fields on a record variable using a single Assignment element."

Salesforce recommends avoiding DML operations (such as creating or updating records) inside loops when designing flows. Performing such actions inside a loop can cause performance issues and exceed governor limits, especially if the loop iterates over a large data set.
Correct Practice:
Use the Assignment element inside the loop to collect data into a variable (like a collection).
After the loop completes, perform DML operations outside the loop using a single Update or Create Records element.
Incorrect Options:
B). Displaying data is not typically done inside loops, but it is not a best-practice concern.
C). Assigning values to variables inside a loop is acceptable.
D). Nesting another loop is discouraged, but not as problematic as performing DML operations inside a loop.
Reference Extracts from Salesforce Help Documentation on Flow Best Practices:
"Avoid DML operations and SOQL queries inside a loop to prevent hitting governor limits."
"Use collection variables and perform record operations after the loop."

DML operations in Flow include creating, updating, deleting, or getting records from the Salesforce database.
A). Update Records - Issues an UPDATE DML operation.
D). Create Records - Issues an INSERT DML operation.
These elements modify the Salesforce database and are subject to governor limits like the 150 DML per transaction limit.
Incorrect Options:
B). Sort Records is not an element in Salesforce Flow.
C). Share Records is not a standard Flow element; record sharing is typically handled through manual sharing or Apex.
Reference Extracts from Salesforce Process Automation Study Guide:
"Create Records and Update Records are flow elements that trigger DML operations."
"DML elements are subject to governor limits and should be bulkified when inside loops."

To display a confirmation message or static content in a Screen Flow (such as "Your submission was successful"), the administrator should use the Display Text component.
Display Text allows admins to show formatted messages, icons, hyperlinks, or dynamic field values from the flow without allowing user input.
Incorrect Options:
A). Text: Used for capturing single-line input from the user.
C). Lookup: Used for selecting records from a related object.
D). Long Text Area: Accepts multi-line input from the user, not for display-only.
Reference Extracts from Salesforce Help Documentation on Screen Components:
"Use the Display Text screen component to show confirmation messages, instructional content, or merge field values during a Screen Flow." rence: Salesforce Help Documentation on Screen Flow Components.