Roll-up summary fields only work for master-detail relationships. Since the standard relationship between Account and Case is lookup (not master-detail), a roll-up summary field cannot be used directly. Instead, the correct solution is to use Flow to count the number of open related cases and update the custom field on the Account.
C). Correct - A scheduled or record-triggered Flow can count related Cases and update the custom field accordingly.
Incorrect Options:
A). Not supported because Account # Case is not master-detail.
B). Process Builder does not support looping or counting related records.
D). Scheduled Apex would work but is not declarative and requires code.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use Flow to roll up data in lookup relationships by counting or summarizing related child records."
"Roll-up summary fields are only available for master-detail relationships."

Salesforce Flow for Service empowers agents by combining automation with guided workflows, enabling more efficient and personalized service. Two key capabilities include:
B). Seamlessly resuming customer interactions - # Agents can pick up exactly where they left off with customers by accessing flows tied to service records.
C). Step-by-step guidance - # Screen Flows combined with Quick Actions walk agents through resolution processes based on service scenarios.
Incorrect Options:
A). Salesforce Flow does not generate print-friendly checklists.
D). While mentoring is beneficial, it ' s not a function of Salesforce Flow.
Reference Extracts from Salesforce Help and Blog on Flow for Service:
"Salesforce Flow for Service uses flows and UI actions to streamline support tasks and personalize agent- customer interactions."

Salesforce Screen Flows support embedding custom Lightning Web Components. To allow users to select an asset during onboarding, the LWC should be embedded directly into the flow via the Screen element.
C). Correct - The LWC must implement the lightningFlowScreen interface to be used within a flow screen.
Incorrect Options:
A). iframe embedding is not supported in Screen Flows.
B). Workflow Rules are deprecated and do not support interaction with LWCs.
D). Lightning Out is used to run Salesforce components in external applications-not relevant for internal Screen Flows.
Reference Extracts from Salesforce Process Automation Study Guide:
"To use a custom LWC in a Screen Flow, implement the lightningFlowScreen interface."
"Screen Flows allow you to incorporate custom LWCs to extend UI functionality."

Flow Builder provides a Loop element under the Logic category that allows flow designers to iterate over a collection (list) of records one at a time. This is useful for applying changes to each record, evaluating conditions, or accumulating results.
B). Correct - The Loop element under Logic is designed specifically for iterating through collections.
Incorrect Options:
A). Integration elements are used for calling external services.
C). Screen is for user input, not iteration.
D). Action elements execute tasks, not control flow iteration.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use the Loop element to iterate over items in a collection. It's a type of Logic element in Flow Builder."
"Each loop cycle processes one item from the collection."

When a flow contains screen components, it must be embedded in user-facing areas of the Lightning Experience UI. Salesforce officially supports distributing Screen Flows through:
A). Lightning Pages - Using the Flow component in the Lightning App Builder, screen flows can be placed on record pages, app home pages, and more.
B). Utility Bar - Admins can configure flows to appear as pop-up panels in the utility bar, available globally in apps.
Other options:
C). Buttons: Custom buttons can launch flows, but only auto-launched flows or flows embedded via screen flows and actions. Buttons are not a direct distribution channel for screen flows.
D). LWC JavaScript: Developers can wrap flows in custom Lightning Web Components, but this is not a standard, declarative distribution method.
E). Related List: Related lists do not support embedding flows.
Reference Extracts from Salesforce Process Automation Study Guide:
"To make screen flows available to users, add them to record pages using the Flow Lightning component or add them to the utility bar in the app."
"Utility bar flows appear in the footer of the Lightning Experience and are accessible globally."