The answer comes from Salesforce's separation of responsibilities. Use C. Email Alert; D. Task; E. Outbound Message. The scenario is asking for approval governance, and the reason is straightforward: Approval processes are designed for formal review. They route a request, capture a decision, and can lock or update the record through submission and final actions. The wording points to this control because the business result must be reliable when real users work with real records.
For the stated requirement - Choose 3 options. Cloud Kicks wants to set up a new opportunity approval process and execute various action items based on the initial submission. Which three action types should an app builder use in the approval. - the selected answer handles the behavior directly. It is not just a way to make the page look cleaner or to remind users what to do. It places the responsibility in the Salesforce feature that owns the outcome. That matters in an App Builder implementation because access, automation, relationships, page rendering, reporting, and deployment each have different enforcement points.
The alternatives are plausible only if the requirement is read too narrowly. A (Invocable Flow) should be rejected because Flow is broad, but it is not correct unless the requirement is specifically about guided or automated logic. B (Decision Element) would be fragile here because it could produce an inconsistent result once different users, records, or apps are tested. A complete implementation should also check page assignment, field access, record ownership, and mobile behavior where those factors apply.
---