Salesforce Process-Automation Practice Test Questions Answers

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.”

=========================================================

In Screen Flows, when a user navigates backward (using the Back button), data entered on the current screen is not automatically preserved unless it has been stored in a variable or explicitly captured.

Correct Option:

D. ✅ Navigating back will clear values on the current screen unless stored in flow variables. Users will need to re-enter that data.

Incorrect Options:

A. “Allow navigation” is not a standard property; back navigation is enabled through screen flow settings and screen components.

B. There is no special “Navigate Flows” permission.

C. Navigating backward does not result in duplicates unless the flow is poorly structured.

Reference Extract from Salesforce Help – Configure Screen Flow Navigation:

“When users navigate backward, unsaved input on the current screen is lost unless captured in variables.”

===========

Login Flows in Salesforce are typically built using Screen Flows, allowing administrators to present users with prompts, forms, and additional steps during the login process. When more complex logic is needed post-login (e.g., validating conditions or updating data), it is best practice to call an autolaunched flow.

Correct Design:

D. ✅ Use Screen Flow for user interaction and trigger an autolaunched flow in the background to handle logic such as validation, record updates, or redirection.

Incorrect Options:

A. Apex Triggers do not run in login flow context.

B. Handling all logic inside a Screen Flow can result in poor performance or limited modularity.

C. Process Builder and Workflow Rules cannot be used in Login Flows.

Reference Extracts from Salesforce Help – Screen Flows and Login Flows:

“Use Screen Flows for login flows to display forms and route logic through autolaunched flows for complex decisions.”

===========

Following best practices when building flows ensures performance, reliability, and scalability.

A. Correct — Flows should always be built and tested in a sandbox or test environment before deployment to production.

C. Correct — Performing database updates in bulk (after the flow collects all records) minimizes CPU time and DML limit issues.

D. Correct — Accessing external objects after DML operations within the same transaction can cause unexpected behavior due to external system limitations.

Incorrect Options:

B. Allowing end users to change flow structure is not a supported or recommended design pattern.

E. Although saving often is helpful, it is not documented as a core flow design best practice.

Reference Extracts from Salesforce Process Automation Study Guide:

“Avoid

When a Flow encounters an unhandled error, Salesforce sends an error email to the flow owner or the last user who modified the flow. This email includes important debugging information such as:

Flow name and version

The flow element where the error occurred

The error message

The user who was running the flow, including their full name and user ID

Correct Option:

C. View the full name of the run-as user in the email — ✅ This helps identify who encountered the error and what triggered it.

Incorrect Options:

A. You cannot schedule queries from within the email.

B. You cannot directly launch a debugger from an email.

D. The email pertains only to a specific flow instance that failed.

Reference Extracts from Salesforce Help – Debug Flows:

“Error emails contain the user’s name, the element that failed, and details on the error to assist in resolution.”

===========