A roll-up summary field is used to display a value in a master record based on the values of a set of related detail records. In this case, the administrator can create a roll-up summary field on the Properties object that counts th e number of Open House records in a Pending status. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fie lds.htm & type=5

UESTION NO: 92

Sales management wants a small subset of users with different profiles and roles to be able to

view all data for compliance purposes. How can an administrator meet this requirement?

A. Assign delegated administrator to the subset of users to View All Data.

B. Create a new profile and role for the subset of users with the View All Data permission.

C. Enable the View All Data permission for the roles of the subset of users.

D. Create a permission set with the View All Data permission for the subset of users.

Answer: D

A permission set is a collection of settings and permissions that give users access to various tools and functions. The View All Data permission allows users to view all data, regardless of sharing settings. B y creating a permission set with this permission and assigning it to the subset of users, the administrator can meet the requirement without changing their profiles or roles. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.ht m & type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm & type=5

A change set is a tool that allows you to send customizations from one Salesforce org to another. A change set can contain components such as objects, fields, profiles, permission sets, workflows, and more. You can use change sets to migrate changes from a sandbox org to a production org or between two sandbox orgs that are affiliated with the same production org. In this case, you can deploy a change set from the sandbox to production that includes the Amount field and all the custom profile s that need access to it. This way, you can update the field-level security settings for the field on each profile in one deployment. References: https://help.salesforce.com/s/articleView?id=sf.changesets.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_components_field.htm & type=5

A lookup relationship is a type of field that links one obje ct to another object. It allows you to access related data from another object and display it on a record page. A lookup relationship can be used to link the custom object that stores financial information to the Account object, so that only finance team m embers can see the related financial information about the account. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm & type=5

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

One of the IDs in the batch referenced a record that was in the recycle bin because deleting records with Bulk API does not delete records permanently but moves them to the recycle bin. Therefore, if a record ID in the batch matches an existing record ID in the recycle bin, an ‘entity is deleted’ error will occur.

The error condition formula of a validation rule should return TRUE when the validation rule should fire and display an error message. In this case, the validation rule should fire when the Title field has the value of ‘CEO’ and the Phone field is blank . The formula Title = ‘CEO’ & & ISBLANK(Phone) returns TRUE when both conditions are met, and FALSE otherwise. References: https://help.sales force.com/s/articleView?id=sf.fields_useful_field_validation_formulas.htm & type=5

 Omni-Channel is a feature that allows service reps to receive work assignments based on their availability, capacity, and skills. It also allows administrators to define routing rules and priorities for different types of work items, such as cases, chats, or leads. Omni-Channel can help reduce the wait time for customers and improve the efficiency of service reps.

The Fields component is a Lightning component that allows administrators to display fields from a record on a Lightning page based on certain condition s or criteria. For example, administrators can use filter logic to show or hide fields based on field values or user profiles. In this case, the administrator can use the Fields component to display fields that only apply to condos based on the value of a field that indicates the type of property. References: https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_fields.htm & type=5

To debug platform events in Apex code, you need to set a debug log on the Automated Process entity. This entity represents an automated process user that runs flows and processes in your org. By setting a debug log on this entity, you can capture the events that are published and consumed by your flow and Apex code, as well as any errors or exceptions that occur during the execution. References: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_debug.htm https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm & type=5

A matching rule is a rule that defines how records are compared for duplication based on certain fields or fuzzy logic. By including more fields or changing the matching method, you can make the matching rule more or less strict and reduce false positives or negatives. In this case, including the email field to the existing matching rule for contacts can help avoid duplicate messages for common names by checking if the email addresses are also identical. References: ht tps://help.salesforce.com/s/articleView?id=sf.matching_rules_create.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.matching_rules_consider ations.htm & type=5