Salesforce Updated Platform-App-Builder Exam Questions and Answers by abdurrahman

Limitations when changing custom field data types include:

A. It is not possible to change the data type of a formula field – formula fields cannot be converted to other field types because they are calculated dynamically.

D. It is not possible to change a Text Area (Long) field to Text – Salesforce prevents reducing the field length because data loss could occur.

Salesforce documentation highlights these restrictions: (Salesforce Help)

B is partially true; changing fields referenced in Apex requires careful handling, but Apex references can sometimes be updated automatically.

C is allowed with some limitations if the External ID type is compatible.

===========

A Partial Copy sandbox is specifically intended for testing scenarios that need representative production data without requiring an entire production dataset. Salesforce states that Partial Copy sandboxes contain production metadata plus a selected sample of production data defined through a sandbox template and explicitly identifies User Acceptance Testing, integration testing, and training as appropriate uses. The template also lets administrators select the objects required for testing and exclude sensitive or irrelevant data sets when necessary. Developer and Developer Pro sandboxes primarily copy metadata and do not automatically provide representative production data. A Scratch Org is a temporary source-driven development environment rather than the preferred UAT environment for actual business users and realistic production-derived data. Therefore, A is the appropriate sandbox type.

================

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========