Salesforce officially ended support for Microsoft Internet Explorer 11 in 2021. Modern automation tools like Flow Builder, Lightning App Builder, and Process Builder require HTML5 and JavaScript features that are not available in legacy browsers.
A). Correct - Internet Explorer is no longer supported for modern Salesforce UI or automation features.
Supported browsers:
B). Apple Safari - Supported
C). Mozilla Firefox - Supported
D). Google Chrome - Supported
Reference Extracts from Salesforce Process Automation Study Guide:
"Salesforce supports the latest stable versions of Chrome, Firefox, Safari, and Edge. Internet Explorer is not supported for Lightning Experience and Flow Builder."

Salesforce Flow supports multiple types of flows, but the two most commonly supported and configurable types are:
B). Autolaunched Flows: These flows do not require user interaction. They can be triggered automatically via processes, record changes, Apex, or scheduled to run at specific times. They are primarily used for behind-the- scenes automation such as record updates, calculations, and decision logic.
C). Screen Flows: These flows include screens that allow user interaction. Screen flows are typically used in wizards or guided processes where user input is required, such as entering data or making selections.
Incorrect Options:
A). Remote Flows: This is not a supported flow type in Salesforce terminology.
D). Managed Flows: This is not a recognized flow type; "managed" might refer to package-managed flows, but it ' s not a flow type classification.
Reference Extracts from Salesforce Process Automation Documents / Study Guide:
"Autolaunched flows run in the background without user interaction."
"Screen flows provide a UI for user interaction."
"Salesforce Flow supports Screen Flows, Autolaunched Flows (with or without triggers), Scheduled Flows, and more."

Salesforce Flow for Service leverages Flows built in Flow Builder and deploys them using the Actions and Recommendations component. Admins use Actions and Recommendations deployments to define which flows and when they should be shown to agents in the Lightning Service Console.
A). Correct - Create flows using Flow Builder, then configure them within an Actions and Recommendations deployment or reference them in a process.
Incorrect Options:
B and C - Actions and Recommendations is not configured from Process Builder or Flow directly but through deployment setup in Setup.
D). Process Builder is deprecated for future use and not the recommended tool for this function.
Reference Extracts from Salesforce Process Automation Study Guide:
"Actions and Recommendations surface guided workflows built with Flow Builder. These are deployed via Actions and Recommendations deployments."
"Use Flow Builder to build Screen Flows, then configure them for use in the console using the component."

The Debug button in Flow Builder is designed to help administrators test their flows in real-time. When using Debug, admins can:
Enter custom values for input variables.
Observe the flow's path of execution.
Monitor how decisions and assignments behave.
See outputs, errors, and element-by-element outcomes.
This helps identify logic issues before activating the flow.
A). Correct - The Debug tool is intended for entering input values and viewing detailed flow execution results.
Incorrect Options:
B). Auto-save settings are unrelated to the Debug tool.
C). Flow versioning is handled manually and not linked to debugging.
D). Flows do not support rollbacks of committed database changes during debugging.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use Debug to test a flow's logic step-by-step, passing values into input variables and monitoring outcomes."
"Debugging helps trace decision paths, assignments, and screen navigation."

Scheduled actions in flows (via scheduled paths) can be triggered relative to:
A). Specific date/time fields on the triggering record (e.g., 3 days before CreatedDate or a custom field).
C). Specific days of the week (supported in Scheduled Flows that run daily/weekly and evaluate record criteria).
A). Correct - You can configure scheduled paths based on a date/time field on the triggering record.
C). Correct - In Scheduled Flows, you can define execution by specific days of the week.
Incorrect Options:
B). Scheduling based on when a process " ran last time " is not a supported scheduling condition.
D). Salesforce scheduling does not support relative dates to rare calendar events like leap year days.
Reference Extracts from Salesforce Process Automation Study Guide:
"Scheduled paths in record-triggered flows can be based on date/time fields or offsets (e.g., 5 days before Due Date)."
"Scheduled Flows can be configured to run on specific days of the week or month."