When preparing test cases for flows, admins should consider the following:
A). Negative scenarios - Test cases should validate what happens when conditions are not met and actions should not fire.
C). Formulas - Test inputs should include cases that help evaluate formula behavior for correctness and edge cases.
E). Expected outcomes - Confirm that intended automation paths execute under certain conditions.
Incorrect options:
B). Number of users affects scalability but not functional test cases.
D). Flow execution time is not typically part of a functional test plan unless performance is in scope.
Reference Extracts from Salesforce Process Automation Study Guide:
"Test flows for both successful and unsuccessful execution paths."
"Validate formula logic using test values to ensure correct evaluation."
"Include cases where no action should occur to ensure criteria are evaluated properly."

The most appropriate and declarative way to display the count of related records (e.g., open Cases related to an Account) is by using a:
D). Roll-Up Summary Field - # This field type allows you to count related child records (e.g., open Cases) on the parent object (e.g., Account).
Roll-Up Summary Fields are available when there ' s a master-detail relationship or a lookup with special tooling (e.g., Declarative Lookup Rollup Summaries for custom objects).
Incorrect Options:
A, B, C: These are programmatic or declarative alternatives that add unnecessary complexity when a roll-up summary is available.
Reference Extracts from Salesforce Help Documentation on Roll-Up Summary Fields:
"Use roll-up summary fields to display aggregate values from related records, such as the number of related open Cases."

Salesforce recommends that you avoid executing DML operations (such as Create or Update Records) or performing SOQL queries inside a loop. Doing so risks hitting governor limits and can significantly reduce flow performance.
Correct Option:
C). # Executing record operations inside a loop should be avoided. Instead, use Assignment to build a collection variable and perform the DML outside the loop.
Incorrect Options:
A). Assigning variables inside loops is acceptable and often necessary.
B). Displaying data is not typical in a loop, but it's not a best practice issue.
D). Nested loops are discouraged but not as critical as avoiding DML operations.
Reference Extract from Salesforce Developer Blog - Best Practices for Designing Efficient Flows:
"Avoid DML operations and SOQL queries inside loops. Use collections to handle record updates after the loop completes."

The utility bar allows flows to be accessible globally within an app - users can access these flows from any screen. This makes it ideal for:
Use cases like time entry, contact lookups, or quick self-service actions.
Scenarios that are not tied to a specific record.
Correct Option:
D). When users need access from anywhere in the app - this is the most accurate description of the purpose of placing a flow in the utility bar.
Incorrect Options:
A). Record-scoped flows should be placed on record pages.
B). Background flows should be auto-launched.
C). "At all times" is vague - "anywhere in the app" is the technical criteria used by Salesforce.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use utility bar to display Screen Flows that users can access from any page within the app."
"Flows in the utility bar are ideal for global, non-record-specific functions."

In Flow Builder, a variable is a type of resource that stores temporary data used during the flow's execution.
Variables can be modified as the flow progresses, making them ideal for dynamic logic, calculations, and user input storage.
Correct Option:
C). # Variable - Designed to hold and change data during a flow's runtime.
Incorrect Options:
A). Error Message is not a data-holding resource.
B). Text Template is static and cannot be changed mid-flow.
D). Formula resources are read-only and recalculated but not updated directly.
Reference Extract from Salesforce Help - Flow Variables:
"Use variables to temporarily store values. Variables can hold strings, numbers, records, and more. They can change throughout the flow."