Full Access Salesforce Platform-App-Builder Tutorials

Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

When configuring an approval process, the available initial submission actions (triggered when a record is first submitted for approval) include sending notifications, creating tasks, and sending outbound messages.

Why A (Outbound Message) is correct:Exact Extract:“Outbound messages can be configured as approval actions to send information to external systems when a record is submitted or approved.” — Salesforce Help | Approval Processes Overview

Why C (Task) is correct:Exact Extract:“Approval processes can create tasks for users as part of approval actions to ensure follow-up on record changes.” — Salesforce Help | Approval Actions

Why D (Email Alert) is correct:Exact Extract:“Email alerts can be sent automatically when a record is submitted, approved, rejected, or recalled.” — Salesforce Help | Approval Processes Overview

Why not B (Invocable Flow):Invocable Flows are not selectable as approval actions — they are used in Process Builder or Flow itself, not Approval Process configuration.

Why not E (Decision Element):Decision elements are Flow components, not part of the Approval Process action set.