Salesforce Certified Platform App Builder Practice Test - Questions Answers, Page 4

Creating both customer and dealer as accounts, creating account teams on each account and associating the dealer records with the parent account would allow UC to track each customer and dealer separately, as well as their relationships and reps.Account hierarchy is not suitable for this scenario, as it is used to show the relationships among parent and child accounts within a single company

A text-only Visualforce page can be used to show a text notification on a case record page based on a condition. The Visualforce component can be dragged into the Case Lightning page and its visibility can be set to show when the account support level is platinum.This is the simplest and most flexible way to meet the requirement

Big objects and external objects can be used to archive historical data and reduce data storage in Salesforce, while still allowing users to access the archived data using reports, queries, and lookups.Big objects store data within Salesforce, while external objects store data outside Salesforce and integrate it with Salesforce using an external data source

Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user's search experience by showing more relevant information and allowing more refined filtering.The view filter settings and the accounts tab columns displayed are not related to the search functionality

To configure a custom Lightning component for use in a record page, the app builder needs to edit a record page using the Lightning App Builder and drag the component onto the page.The Page Layout editor and the App Manager are not used for this purpose

A template for a new Lightning record page determines how the page is divided into regions. The template is responsive and will automatically adapt to the device being used to view the record page.The template can be changed after the initial save, and users do not need ''View All Data'' permissions for the object

Changing custom field types may result in data loss if the new field type is incompatible with the old one. For example, changing a text field to a number field may cause text values to be deleted. Field history tracking records value changes of 255 characters or less. If a rich text field value exceeds this limit, only the first 255 characters are tracked.

An indirect lookup relationship is a custom relationship between two objects that are linked by an external ID field. The external ID field must be a custom field on the parent object that has the ''External ID'' attribute enabled. The child object must be a standard or custom object that is on the detail side of a master-detail or lookup relationship.

Workflows that cause each other to fire back and forth recursively can result in workflow limits errors. For example, if workflow A updates a field that triggers workflow B, and workflow B updates a field that triggers workflow A, this can create an infinite loop of workflows that exceed the maximum number of workflow time triggers per hour.