Default actions that developers can add to a flow include:

Default actions that developers can add to a flow include:

• A. Ask for approvals
• B. Create or update records
• C. Update record
• D. Notify user

Answer: (A)

When building a flow, you use built-in actions to drive the process. Approvals are one of these standard, out-of-the-box actions that handle human decision making. They let a flow pause for a decision from a user or group and then continue based on the outcome, providing a reusable, ready-made pattern for governance and sign-off. This makes asking for approvals the best choice for a default action in many flows, since it directly handles the common need for a decision before proceeding. Other actions like creating or updating records or notifying a user are also available, but they are generic data operations or communications. They don’t inherently capture or manage a human approval step, which is why the approval action is the most fitting default in this context.

When building a flow, you use built-in actions to drive the process. Approvals are one of these standard, out-of-the-box actions that handle human decision making. They let a flow pause for a decision from a user or group and then continue based on the outcome, providing a reusable, ready-made pattern for governance and sign-off. This makes asking for approvals the best choice for a default action in many flows, since it directly handles the common need for a decision before proceeding.

Other actions like creating or updating records or notifying a user are also available, but they are generic data operations or communications. They don’t inherently capture or manage a human approval step, which is why the approval action is the most fitting default in this context.