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

The correct component is the Highlights Panel. More precisely, Salesforce refers to the newer version as the Dynamic Highlights Panel, which displays up to 12 key record fields configured in Lightning App Builder. Since the option list only says Highlights Panel, option B is the exam match.

Path is for guiding users through stages. Accordion is for collapsible sections. A custom Lightning Web Component is not needed because Salesforce provides this functionality declaratively.

===========

A Screen Flow is the best declarative tool when the user must answer questions through a guided UI and use those answers to update record fields. Salesforce documents that screen flows provide a UI that guides users through a business process, and they can be launched from quick actions or Lightning pages.

A custom button or action can launch the flow, collect the extra approval-related information, update the Account fields, and then continue the approval submission logic.

Why not others:

A. Custom object only stores data; it does not provide the popup/question flow.

B. Visualforce could be custom-coded, but Flow is the declarative App Builder solution.

D. Custom Lightning component requires development and is not the best declarative answer.

===========

The correct answers are A. Remove the delete button from the Delivery page layout and C. Remove the Delete permission from the Shipper profile.

The real security control is C because object permissions define whether users can create, read, edit, or delete records for an object. To prevent shipping users from deleting Delivery__c records, the app builder must remove the Delete object permission from the Shipper profile.

A is also a valid supporting UI step because Salesforce page layouts can control whether standard/custom buttons are displayed. Removing the Delete button reduces the visible delete option on the record page. However, this alone is not complete security because hiding a button does not fully remove the underlying permission.

Why others are incorrect:

B is incorrect because a regular permission set grants additional access; it does not remove profile access.

D is incorrect because OWD controls record-level sharing, not object-level Delete permission.

===========

The correct answer is A because Case_Issue__c is described as a junction object. In Salesforce, a junction object is typically built with two master-detail relationships to model a many-to-many relationship.

Salesforce documentation states that sharing access to a junction object record is determined by the user’s sharing access to both associated master records and the sharing setting on the relationship fields.

So, for auditing users to view Case_Issue__c records, they need read access to both parent/master records: Case and Issue__c.

Why others are incorrect:

B misses access to Issue__c.

C includes only the junction object and misses both parent/master records.

D misses access to Case.

===========

The correct answers are C. My Domain must be deployed and D. The component is tagged for record pages instead of home pages.

Salesforce custom Lightning components must be properly configured before they appear in Lightning App Builder. Salesforce Trailhead explains that custom components configured for Lightning App Builder appear in the Lightning Components pane, and the component bundle must be compatible with Lightning App Builder and Lightning pages.

C is correct because Salesforce requires My Domain for adding custom Lightning components in Lightning Experience/App Builder scenarios. Salesforce Help notes that users cannot add a custom Lightning component without enabling and deploying My Domain.

D is correct because Lightning components must be exposed for the correct page type. A component exposed only for record pages will not appear for a Lightning Home page. Salesforce Developer documentation states that lightning__HomePage enables a component to be used on a Home page, while record-page-only configuration is separate.

Why others are incorrect:

A is incorrect because a custom tab is not required to add components to a Lightning Home page.

B is incorrect because “developer permission” is not the normal reason a downloaded component cannot be added to a Lightning Home page.

===========

The correct answers are C. Email Alert, D. Task, and E. Outbound Message.

In a standard Salesforce approval process, available approval action types include Email Alerts, Tasks, Field Updates, and Outbound Messages. Since Field Update is not listed in the answer choices, the three valid action types from the options are Email Alert, Task, and Outbound Message. Salesforce documentation identifies approval-process actions around task, email alert, field update, and outbound message automation.

A. Invocable Flow is incorrect because it is not a standard approval-process action type in this exam context.

B. Decision Element is incorrect because Decision is a Flow element, not an approval-process action.

===========

The correct answers are B. Apex and C. AppExchange.

Cloud Kicks needs to count related Case records on Account based on open and closed status. Standard roll-up summary fields work only in supported roll-up relationships, mainly master-detail relationships. Salesforce documentation states that lookup relationships do not support roll-up summary fields.

Because Cases are related to Accounts through a lookup-style relationship, native roll-up summary fields are not the best available option in this answer set. The app builder can meet the requirement by using:

Apex — Apex triggers can run before or after record changes such as insert, update, or delete, allowing custom logic to recalculate the open and closed Case counts on the Account.

AppExchange — AppExchange roll-up tools, such as lookup roll-up packages, can summarize records across lookup relationships without building custom code.

Why others are incorrect:

Validation Rule prevents invalid data entry; it does not calculate related record counts.

Approval Process routes records for approval; it does not summarize Case counts.

===========

Performing Data Manipulation Language operations such as Update Records inside a Loop is a classic Flow governor-limit anti-pattern. Each loop iteration can perform another database operation, rapidly consuming transaction limits when a large collection of Opportunities is processed. Salesforce ' s official Flow guidance explicitly says never to place DML operations inside loops. Instead, the app builder should iterate through the records, use Assignment elements to modify them and add them to a record collection, and perform one bulk Update Records operation after the loop. Fault paths improve error handling but do not prevent governor-limit consumption. Schedule-triggered flows can update standard objects, so D is incorrect. The scalability problem described is therefore directly caused by performing Update Records repeatedly inside the Loop element.