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

The requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

The correct answers are A. The NOW() function in the formula field and D. A cross-object field referenced in the formula field.

Salesforce allows roll-up summary fields to summarize formula fields only when the formula does not contain unsupported dynamic or cross-object references. Salesforce documentation states that roll-up summaries can calculate formula fields only if the formula does not contain cross-object field references or functions that derive values dynamically, such as NOW() or TODAY().

A is correct because NOW() changes dynamically based on current date/time.

D is correct because cross-object field references prevent the formula from being used in the roll-up summary.

C is incorrect because CASE() itself is allowed.

B is incorrect because the issue is not simply a field update; the restriction is specifically cross-object references or dynamic formula functions inside the formula being summarized.

===========

The correct answer is C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

The correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

The validation must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

The correct answers are C. Unique and D. External ID.

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answer is A. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.

To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.

Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object’s page layout. Salesforce documentation for related lists confirms that related lists are managed from the object’s page layout.

Why others are incorrect:

B is incorrect because a roll-up field does not create the relationship or related list.

C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.

D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

===========

The correct answers are A. Unique and D. External ID.

The legacy ID should be marked as an External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce REST API documentation states that records can be inserted or updated using a specified external ID field.

The field should also be marked Unique so that the legacy system ID identifies one Salesforce Account record only. Salesforce documentation explains that an external ID can represent an ID from another external system, and uniqueness helps prevent duplicate matching values.

B is incorrect because encrypted text is not appropriate for a matching/upsert key.

C is incorrect because Required only forces a value; it does not make the field usable for upsert matching or prevent duplicate legacy IDs.

===========