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

The app builder should select Enhanced List for the Related List type for the Related List Lightning component. Enhanced List allows users to see ten fields and sort and wrap text on their Related Lists. Option B is incorrect because Basic List only allows users to see four fields and does not support sorting or wrapping text on their Related Lists. Option C is incorrect because ListView does not show Related Lists on record pages, but rather shows list views on object home pages or tabs. Option D is incorrect because List Class is not a valid Related List type.

The app builder should recommend building a global action to create Contacts. A global action allows users to create records quickly from any page in Salesforce on their mobile devices. The app builder can also specify predefined values for some fields in the global action, such as Account Name or Phone Number, to make data entry easier for users. Option A is incorrect because customizing the mobile menu to move Contacts to the top does not help users create new contacts quickly or follow up later. Option C is incorrect because adding a compact layout to Contacts does not help users create new contacts quickly or follow up later, but rather shows them more fields on record detail pages or list views. Option D is incorrect because using Path and setting pre-defined values does not help users create new contacts quickly or follow up later, but rather guides them through different stages of a record.

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.

The two recommended solutions for the app builder to give the users appropriate access are creating a criteria based sharing rule to all opportunities with the sales operations public group and adding a permission set with 'View All' and 'Modify All'' opportunity permissions enabled. A criteria based sharing rule can grant read and write access to all opportunities that meet certain criteria to a specified group of users. A permission set can grant additional object-level permissions to users without changing their profiles. Option B is incorrect because adding a manual share for all opportunities with each user on the sales operations team is not scalable or maintainable. Option D is incorrect because creating a criteria-based sharing rule to share all opportunities with the sales operations private group is redundant, as private groups are used to manually share records with individual users or other groups.

The solution that the app builder should use to meet DreamHouse Realty's needs is Master-Detail Child Object. A master-detail relationship can be used to create a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a roll-up summary field on the parent object to calculate the highest value of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.

The opportunity standard fields that are available to be configured directly are Stage, Lead Source, and Type. These fields can be modified by editing their picklist values, adding or removing values, or changing their default values. Option A is incorrect because Forecast Category is not a standard field on the opportunity object, but rather a system field that is automatically derived from the Stage field.

The best practice that the app builder should follow when building out automation is one record change process per object. A record change process is a type of process in Process Builder that starts when a record is created or updated. Having one record change process per object can avoid conflicts or errors when multiple processes try to update the same record at the same time. Option A is incorrect because one workflow rule per object is not a best practice, as workflow rules are considered legacy tools and have limitations compared to Process Builder. Option B is incorrect because one flow per object is not a best practice, as flows are more complex and require more resources than processes. Option C is incorrect because one invocable process per object is not a best practice, as invocable processes are used to invoke other processes from within a process or a flow.

The solution that should meet this requirement is updating the support team profile to remove the Bronze record type. This way, the support team users will not be able to create new cases with the Bronze record type, as it will not appear in their record type selection list. Option A is incorrect because updating the organization-wide defaults to private for Case does not affect the record type availability, but rather the record access level. Option C is incorrect because creating permission set group for Case that includes Platinum and Diamond record types does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile. Option D is incorrect because making the record type hidden to support users and updating sharing roles to private does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile.

The solution that the app builder should configure to meet these requirements is creating three lead record types each with its own page layout containing the relevant fields. This way, the app builder can customize the fields and sections that appear on each record type based on the source of the lead. Option B is incorrect because creating a partner community and a record type for web and trade show leads does not address the requirement of collecting information that is unique to each type of lead, as partner community users may have different fields and layouts than internal users. Option C is incorrect because creating three sections on the lead layout and instructing users to collapse the non-relevant fields does not address the requirement of collecting information that is unique to each type of lead, as users may still see or enter data in the wrong fields. Option D is incorrect because creating custom page layouts for each type of lead only containing the relevant fields does not address the requirement of collecting information that is applicable to all sources, as users may miss some common fields.