Salesforce External Services must be registered using an OpenAPI 2.0 schema (either in JSON or YAML format). Once registered, they appear in Flow Builder as invocable actions. There is also a known limit to the number of External Services that can be registered per org (e.g., 50).
B). Correct - OpenAPI 2.0 in JSON or YAML format is supported.
D). Correct - Limits apply per org for registered external services.
Incorrect Options:
A). Once registered, services can be used like other actions in Flow and modified within Flow Builder.
C). OpenAPI 1.0 is not supported.
Reference Extracts from Salesforce Process Automation Study Guide:
"External Services must use OpenAPI 2.0 schema and support both JSON and YAML formats."
"There is an org limit for the number of external service registrations."

Salesforce Flow for Service is designed to automate and guide complex, multi-step service processes. This includes capturing data, decision logic, external service calls (like credit checks), and completing guided workflows. This is especially helpful in highly regulated industries like banking.
D). Correct - A multi-step process like loan application processing with validations and guided actions is a perfect use case for Flow for Service.
Incorrect Options:
A and C describe simple data lookups, not guided processes requiring automation.
B is irrelevant and not aligned with Flow for Service use cases.
Reference Extracts from Salesforce Process Automation Study Guide:
"Flow for Service provides guided workflows and automations for agents to efficiently complete complex service processes like loan applications or claims processing."
"Actions and Recommendations allows guided, contextual flows to be surfaced during service interactions."

To create dynamic forms in Flow, an admin can use conditional visibility settings on Screen Components.
These settings allow components to appear or hide based on previous user inputs, creating a dynamic, responsive form experience.
C). Screen Components - # Correct. These can be configured to show/hide based on logic using Flow's conditional visibility.
Incorrect Options:
A). Local Actions - Used to trigger client-side operations like closing a tab or refreshing a screen, not to control dynamic screen logic.
B). Decision Graph - Not a recognized Salesforce term; possibly a misnomer for Decision elements.
D). Dynamic Resources - Not a valid feature; "dynamic" behavior is handled via logic and visibility settings.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use conditional visibility on Screen Components to show or hide questions based on responses to earlier inputs."
"Screen elements can be configured with rules that evaluate field values to determine whether they should display."

Salesforce Flow is the name of the overall suite of flow automation tools. This includes the ability to create, run, and manage flows. Flow Builder is the point-and-click UI tool used to create the flows.
Salesforce Flow = entire automation platform (includes Flow Builder, Runtime Engine, Flow Orchestration, etc.) Flow Builder = visual tool used to design and build the flow.
Therefore:
B). Flow Builder is a part of Salesforce Flow. # Correct
A). Incorrect - reversed relationship.
C). Incorrect - speed isn't the defining difference.
D). Incorrect - both are available in Lightning Experience.
Reference Extracts from Salesforce Process Automation Study Guide:
"Salesforce Flow is the product that includes tools like Flow Builder for creating flows and automation."
"Flow Builder is the declarative interface for designing flows within Salesforce Flow."

There are 3 main "building blocks" of any Flow:
1. Elements are the individual building blocks of the Flow. These perform logical actions such as assignments, decisions, or loops. There are also data elements that will query the database or commit record changes.
2. Connectors determine which element leads to which. Winter '21 enables Auto-Layout, and connects the Elements together automatically.
3. Resources are the individual variables of data that are to be used in a Flow - these can be strings of text, numbers, records, formulae, or collections.