Salesforce Updated Platform-App-Builder Exam Questions and Answers by aron

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

A record-triggered flow is the preferred declarative automation. Salesforce supports record-triggered automation when records are created, updated, or deleted, and its current Flow architecture includes after-delete processing for actions that must occur because a record was removed. The flow can trigger from Task deletion, use information from the triggering Task to identify the related Case, obtain the Case owner, and execute the email notification action. Assignment rules are designed primarily for assigning records such as Cases or Leads and do not respond to Task deletion. Escalation rules manage Case escalation timing, not deletion events. An Apex trigger could technically implement the requirement, but Platform App Builder principles favor native declarative automation when Flow supports the event and required action.

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

The correct answers are A. Create a master-detail relationship field on Application to Open_Position and B. Create a master-detail relationship field on Application to Job Candidate .

This requirement describes a many-to-many relationship : one Job Candidate can apply for multiple Open Positions, and one Open Position can have multiple Job Candidates. The correct Salesforce design is to use a junction object , which in this case is Application__c .

Salesforce documentation states that many-to-many relationships can be modeled using master-detail relationships between a junction object and the two related objects.

So Application__c should have:

A master-detail relationship to Job_Candidate__c

A master-detail relationship to Open_Position__c

This allows applications to appear on the Job Candidate record and also on the Open Position record.

C and D are incorrect because the relationship fields should be created on the junction object , Application__c , not from the parent objects back to Application.

===========

The correct answer is C.

Universal Containers wants to accept clean data and verify that important fields are entered. The best solution is a validation rule, because validation rules verify that data entered by users meets defined standards before the record can be saved. This is stronger than making a field required only on a page layout, because validation rules can enforce requirements based on conditions such as record type.

A is weaker because page-layout required fields apply mainly to that UI layout and do not provide the same conditional data-quality enforcement. B is reactive cleanup after bad data exists. D can calculate or display a value, but it does not enforce user data entry by itself.

===========