Free Practice Questions for Salesforce Platform-App-Builder Exam

Changing the data type of custom fields in Salesforce has specific limitations that need to be considered to ensure system integrity and prevent errors:

A. It is not possible to change the data type of a formula field to any data type. Formula fields are calculated based on other field values and cannot be converted into a storage data type because they do not store data themselves.

D. It is not possible to change the data type of a Text Area (Long) field to Text. Text Area (Long) fields support up to 131,072 characters, which far exceeds the 255 character limit of standard Text fields. Converting such a field to a smaller capacity field would potentially lead to data truncation or loss.

For official guidance on data type changes, refer to Salesforce's Custom Field Considerations.

The best actions to take to avoid creating duplicate leads when uploading a list of 400 leads are to utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads, and to upload the lead list using the import wizard and select a Matching type to prevent duplicate lead creation. The Lead Matching Rule defines the criteria for identifying duplicate leads, and the Duplicate Rule defines the actions to take when a duplicate is detected. The import wizard allows users to choose a Matching type based on the Lead Matching Rule and block or allow duplicates. Using Data Loader’s update function or enabling Duplicate Matching in the Data Management section will not prevent duplicate lead creation.

A quick action on the Account object can be used to create Opportunity records related to an Account. The quick action can pre-populate some fields based on the Account record, and also allow the user to input some fields. This would improve the process of creating Opportunity records

The field attribute that should be selected are Unique and External ID. Unique means that the field will not allow duplicate values. External ID means that the field can be used as a foreign key for data imports and upserts. Option B is incorrect because Required means that the field must have a value and cannot be left blank, which is not necessary for this requirement. Option D is incorrect because Text (encrypted) means that the field will store sensitive data in an encrypted format, which is not necessary for this requirement.

Two reasons that can prevent an app builder from adding a custom component to the Lightning home page are if My Domain is not deployed, or if the component is tagged for record pages instead of home pages. My Domain must be deployed to add custom components to the page with the App Builder, as it enables Lightning components and other features. The component must be tagged for home pages in its configuration file, otherwise it will not show up in the App Builder for home pages

The setting for the visibility of custom tabs is default off for all users when they are deployed via change sets without including the profile settings or permission sets. This means that the custom tabs are not visible in any apps or navigation menus for any users unless they are manually added by each user or by an administrator3. Option B, C, and D are not correct settings for the visibility of custom tabs.