Platform-App-Builder Dumps with Practice Exam Questions Answers

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.

===========

The correct answer is D.

Universal Containers wants the Account Region value to appear on related Contact records and stay in sync whenever the Account value changes. A cross-object formula field on Contact is the best declarative solution because it dynamically references the parent Account field. Salesforce Trailhead explains that a cross-object formula can pull information from a parent object through a lookup relationship, such as showing Account information on Contact.

Because Account Region is a picklist, the formula must convert the picklist value to text using the TEXT() function. Trailhead gives the same pattern with Account Industry on Contact: TEXT(Account.Industry) .

B is incorrect because ISPICKVAL() checks whether a picklist equals a specific text value and returns true/false; it does not display the picklist value.

A and C are incorrect because creating a copied field and trying to update it through a relationship is unnecessary when a formula field can stay synchronized automatically.

===========

The correct answer is A because Salesforce provides the Establish upper bound on existing picklists option to protect picklist performance by limiting inactive picklist values. Salesforce documentation states that this setting runs a query to identify picklists with fewer than 4,000 inactive values and enforce the limit.

Why others are incorrect:

B is for reusing picklist values across fields, not reducing inactive picklist performance impact.

C would worsen the issue because it removes limits on inactive values.

D is too drastic and not the recommended Salesforce feature for this issue.

===========

The correct answer is D. Universal Containers wants the real-time value of the Account’s Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.

Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce’s TEXT function supports picklist values in formulas.

Example formula concept:

TEXT(Account.Support_Level__c)

Why others are incorrect:

A is incorrect because the formula must be on Case, not Account.

B is incorrect because Case already relates to Account; a new lookup alone does not display the value.

C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

===========

The requirement specifies that a new vendor must accept terms on Agreements before an Opportunity can be closed. Salesforce Approval Processes are the declarative solution for enforcing such business rules. An approval process can:

Require users (vendors) to accept or approve records (Agreements).

Prevent Opportunities from moving to a closed stage until approval is completed.

Send email notifications automatically to approvers.

Salesforce documentation confirms that approval processes are used to enforce conditions on record lifecycle and ensure required steps are completed before record status changes. (Salesforce Help)

A. Email Alert cannot enforce record progression.

B. Dynamic Action only controls field-level UI visibility, not enforcement.

D. Validation Rule could prevent saving a record, but it cannot require explicit approval from a specific user group.

===========