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

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

Salesforce states that to make a custom object ' s records searchable, an administrator can create a custom tab set to Default On or Default Off ; creating the tab enables the object ' s search capability. Salesforce also warns that a custom object ' s tab must be visible for the user ' s profile and specifically says not to set the tab to Tab Hidden. A Search Layout controls which fields users see in search results but does not by itself enable object searchability. A search filter similarly refines results rather than enabling the custom object in Global Search. Therefore, among the available options, creating the custom tab with Default Off is the correct configuration.

The correct formula is:

IF(

NOT(ISBLANK(Nickname__c)),

Nickname__c,

FirstName

)

Salesforce recommends ISBLANK() to check whether a field has no value, including text fields. Since Nickname__c is optional, the formula first checks whether it is not blank. If it has a value, Salesforce uses the nickname. If it is blank, Salesforce uses FirstName .

A is incorrect because BLANKVALUE() is not used this way inside NOT() .

B is incorrect because the logic is reversed and ISNULL() is not preferred for text fields.

D is incorrect because TEXT() is not needed for a text field and does not perform a blank check.

===========

The correct answer is B. Unable to reference the child records.

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

The correct answer is C. Dynamic action.

Dynamic Actions allow an app builder to control which actions appear on a Lightning record page and apply filters to control action visibility. Salesforce documentation states that Dynamic Actions can be assigned in Lightning App Builder and visibility filters can control when actions are shown.

For this requirement, the custom Sync action can be shown only when the Account custom Status field equals Ready to Sync. A custom link alone does not provide the same Lightning App Builder visibility control, a formula field cannot call the Lightning Web Component action, and an AppExchange product is unnecessary.

===========

The correct answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

The requirement has two key parts: the app builder has very little time, and the solution must be fully customizable. Salesforce documentation describes unmanaged packages as suitable for one-time drops of applications that require customization after installation. That fits this scenario better than building everything from scratch.

C is incorrect because managed packages are better for distributed, upgradeable AppExchange apps, but they can restrict subscriber changes to packaged components. The question specifically says the solution still needs full customization, which points to an unmanaged package.

The correct answer is C. Add the standard Chatter feed component.

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========