Platform-App-Builder Exam Dumps - Salesforce Certified Platform App Builder (Plat-Admn-202)

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct answers are C. Lightning App Builder and D. Lightning components in Setup.

In Lightning App Builder, custom Lightning components that are configured for use in Lightning App Builder appear in the Lightning Components pane.

In Setup → Lightning Components, Salesforce allows admins to view a list of Lightning Web Components and Aura components in the org.

Why others are incorrect:

A. Visualforce components in Setup lists Visualforce custom components, not Lightning components.

B. Salesforce Optimizer App analyzes org configuration and recommendations; it is not the place to list available custom Lightning components.

===========

The correct answer is B. This lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created.

A Salesforce roll-up summary field is created on the object that is on the master side of a master-detail relationship. Lookup relationships do not support standard roll-up summary fields. Salesforce documentation confirms that roll-up summary fields are defined on the master object in a master-detail relationship.

A and D are incorrect because formula fields cannot count related child records across a lookup relationship.

C is incorrect because the relationship is currently lookup, so a standard roll-up summary field cannot be created yet.

===========

The correct answer is D. Approval process with a record-triggered flow.

Salesforce does not provide a simple “approval before delete” button behavior by default. The practical declarative pattern is to use an Approval Process for manager permission and a record-triggered Flow to automate the submit/delete logic. Flow includes a Submit for Approval action for Classic Approval Processes and also supports deleting records through the Delete Records element.

Why not the others:

A two-step approval process only handles approval routing; it does not complete the deletion automation by itself. A scheduled path or schedule-triggered flow is not appropriate because this is based on a user’s delete request, not a time-based batch process.

===========

The correct answer is C. Schema Builder.

Schema Builder is designed to help app builders visualize the Salesforce data model, including standard objects, custom objects, fields, and relationships. Salesforce Trailhead states that Schema Builder lets users visualize and edit the data model and is useful for understanding complex data models.

Object Manager and Fields & Relationships are used to configure individual objects and fields, but they do not provide the same visual relationship map. Lightning App Builder is for page layout and UI configuration, not data-model visualization.

The correct answer is C. Flow.

The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.

Why not the others:

Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.

===========