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

Create a page layout with the field and use field-level security to hide the field from all other users is how the app builder should meet the requirement of making the comment field on Review private to anyone outside of HR department. Field-level security can control which profiles can view or edit a field on a record. Create an Apex sharing rule, create a sharing rule to share the field with VP of HR with Role and Subordinates, and create a page layout with the field for HR users and another page layout without the field for all other users are not valid or feasible solutions for this requirement.

Set up a delegated approver for the manager is the recommended solution to ensure all of the appropriate deals are reviewed and the leaderboard is up to date. According to theSalesforce documentation, ''A delegated approver can approve records that are submitted for approval by users below them in the role hierarchy.'' Forwarding the approval request to the manager's assistant, having the manager log on and reassign the approval request, and using Process Builder to assign a delegated approver are not valid or feasible options.

Component visibility filter is the feature on the Lightning app builder that should be utilized to restrict a Lightning component to mobile app users. According to theSalesforce documentation, ''Use component visibility filters to show or hide components on a record page based on field values or user profile.'' Chatter feed, highlights panel, and related list quick links are not features for controlling component visibility, but standard components that can be added to a record page.

Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.

Create a validation rule that uses the PRIORVALUE function is how an app builder can meet the requirement of preventing users from increasing the value of Estimated Hours after it is set. According to theSalesforce documentation, ''PRIORVALUE returns the previous value of a field.'' The validation rule can compare the current value and the prior value of Estimated Hours and display an error message if the current value is greater than the prior value. Creating a formula default value for the custom field, creating a formula field that uses the PREVGROUPVAL function, and creating a validation rule that uses the ISCHANGED function are not valid or correct solutions for this requirement.

Add the standard Chatter feed component is how an app builder can add the Chatter feed to a custom object record page. According to theSalesforce documentation, ''The Chatter Feed component displays updates about records in your org.'' Add the standard related list component, add a custom Chatter feed component, and add the Chatter feed component from the AppExchange are not valid or necessary options.

Two Master-detail relationships on a new custom object is how an app builder should configure the data model to create a relationship between Contact and Solar Project objects where each Contact can be related to multiple Solar Project objects, and each Solar Project can have multiple Contacts associated with it. This is an example of a many-to-many relationship that requires a junction object with two master-detail relationships. One Master-detail relationship on Contact and one Master-detail relationship on Solar Project, two Lookup relationships on a new custom object, and one Lookup relationship on Contact and one Lookup relationship on Solar Project are not valid or correct ways to create a many-to-many relationship.

Create a custom action is the recommended solution to meet the requirement of creating additional accounts to form a hierarchy from a Parent Account record. According to theSalesforce documentation, ''Actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.'' A custom action can auto-populate fields based on the parent account and make it easier for users to create child accounts. Add Path on Account hierarchy, add a custom link on Account, and customize a Global Quick Action are not valid or feasible options.