Pass the Salesforce App Builder Platform-App-Builder Questions and answers with ValidTests

To ensure data integrity where the Region field on the Contact object needs to be filled out conditionally based on the parent Account's status, a validation rule on the Contact is the most effective method:

B. Create a validation rule on Contact. This rule can enforce that the Region field must be filled out for Contacts related to Accounts marked as 'High Priority'.

Steps to create this validation rule:

Navigate to Setup → Object Manager → Contact → Validation Rules.

Create a new validation rule.

In the formula, use:

AND(

ISPICKVAL(Account.Customer_Status__c, 'High Priority'),

ISBLANK(Region__c)

) )

Provide an error message to display when the rule is violated.

Save and activate the rule.

This validation rule checks that if a Contact is associated with an Account marked 'High Priority', the Region field cannot be blank.

For further detail, Salesforce's Validation Rule Considerations provides additional guidance.

Roll-up summary fields can only be created on master-detail relationships, and they can only calculate numeric fields, such as currency, percent, and number. Date and time fields are not supported for roll-up summary fields. Checkbox fields can be used in roll-up summary filters, but not in the field to aggregate

A formula field is a read-only field that derives its value from a formula expression you define. The formula field is updated when any of the source fields change. You can use formula fields to display images based on certain conditions. In this case, a formula field can be used to display a green, yellow, or red circle image based on the case age.

The two steps that should be suggested to meet these requirements are to select insert null values in settings and to use Data Loader to update leads using the CSV file. Selecting insert null values in settings will allow Data Loader to overwrite existing values with null values. Data Loader is a tool that can import, export, update, or delete large amounts of data.

The issue described occurs due to the settings in the master-detail relationship. Specifically:

The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked (B). This setting prevents changing the parent record (contact) of a child record (service plan) once it has been set. If 'Allow reparenting' is unchecked, it restricts the ability to change the associated contact, leading to the issue observed.

The other options do not directly address the inability to change the associated contact on a service plan record. The 'Read Only' and 'Read/Write' settings (A and C) pertain to access rights to the detail records based on the master record's access but do not affect the ability to reparent a record.

For a detailed understanding of master-detail relationships and their settings, including reparenting, see the Salesforce documentation on relationships:

Master-Detail Relationships: https://help.salesforce.com/articleView?id=relationships_considerations.htm &type=5

LEFT(Account.Zip_Code_c, 5) is the correct formula to display only the first five digits of Zip Code from the parent Account. LEFT function returns the specified number of characters from the left side of a text string. Account.Zip_Code_c is the custom text field that stores the Zip Code on Account object. 5 is the number of characters to return from the left side of the Zip Code. The other options are not valid formulas or functions.

Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.

To track the total number of trails associated with a park without writing code, the correct actions to take are:

Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.

Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.

A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.

For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:

Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm &type=5

Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm &type=5

To ensure that only the sales reps and their manager’s executive can view the rep’s evaluation record but the reps should not be able to view the executive comment field on their review, a private sharing model granting record access using hierarchy and field-level security should be used. A private sharing model means that only the owner of a record and users above them in the role hierarchy can view the record by default. Record access can be granted to other users using manual sharing, sharing rules, or Apex sharing. Field-level security controls which fields are visible or editable for different profiles or permission sets.

 The two actions that an app builder should take to meet the requirements are: Implement a sharing rule. A sharing rule is a way to grant additional access to records based on certain criteria, such as record owner, role, profile, or field value. The app builder can create a sharing rule that grants read access to all accounts with the VIP Account field value to all users. This way, all users can view these accounts, but only the owners can edit them. Change organization-wide defaults. Organization-wide defaults are the baseline level of access that users have to records they do not own. The app builder can change the organization-wide default for accounts from Public Read Only to Private. This way, only the owners can view and edit their own accounts, unless additional access is granted by other means, such as sharing rules. Configuring a permission set is not a valid action, as it does not affect record-level access. A permission set is a way to grant additional permissions and access settings to users on top of their profile settings, such as object permissions, field permissions, app permissions, etc. Setting up an Account Team is not a valid action, as it does not restrict record-level access. An Account Team is a way to share an account and its related records with a group of users who work together on the account, such as sales reps, managers, or support agents. An Account Team grants additional access to team members based on predefined roles and access levels.