Salesforce Plat-Admn-301 - Salesforce Certified Platform Administrator II

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 the number of Open House records in a Pending status. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.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. By 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.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm &type=5

Assignment rules and validation rules are two features that can satisfy these requirements:

Assignment rules are used to automatically assign leads or cases to users or queues based on certain criteria. In this case, an assignment rule can be used to assign leads to different planetary teams depending on which planet the lead is coming from.

Validation rules are used to validate the data entered by users and prevent records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to ensure that every team has all of the information they need by making certain fields required or dependent on other fields.

The other two options are incorrect because:

Matching rules are used to identify duplicate records based on certain fields or fuzzy logic. They do not assign records or validate data.

Workflow rules are used to automate tasks or actions based on certain criteria. They do not assign records or validate data.

Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users’ access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.

A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. A roll-up summary field can be used to count, sum, min, or max values from child records. You can create a roll-up summary field on an object that has a master-detail relationship with another object. In this case, you can create a roll-up summary field on Room that counts the number of Equipment records related to it. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_types.htm &type=5

A lightning action is a type of quick action that can invoke a Lightning component, a Visualforce page, or a URL. The administrator can use a lightning action to redirect the user to a different page after they finish the screen flow. This way, the user will not see the initial screen again and will not misuse the flow tool.

As explained in question 13, permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. Permission sets are useful when a user is part of a team with an assigned profile that covers the majority of their needs but requires more access than the rest of their team for some specific tasks or functions. For example, a user may need access to a custom object or field that is not available to their profile, but only for a limited time or project. In this case, assigning a permission set to the user can grant them the additional access they need without affecting their profile or other users with the same profile. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5

The order in which record-triggered flows are executed is not guaranteed. If there are multiple record-triggered flows on the same object and trigger type, Salesforce does not guarantee which one runs first. Therefore, the administrator should consider this when designing record-triggered flows that depend on each other’s outcomes. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm &type=5

Delegated administrators in Salesforce are designated users who are given limited administrative privileges to assist system administrators without having full access to all administrative functions. The two functions they can typically perform, which align with the permissions available to delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users, resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have the ability to manage custom objects or perform extensive customization. These functions are reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify permission sets. This is also restricted to full administrators, as it involves controlling access at a granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can maintain security and control while also sharing some administrative workload.

Role hierarchy is a sharing mechanism that should be used to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers. Role hierarchy is a way to grant access to records based on the user’s position in an organization’s hierarchy of roles. Role hierarchy can grant users access to records owned by or shared with users below them in the hierarchy for objects that have organization-wide defaults set to Private or Public Read Only. By using role hierarchy, the administrator can ensure that directors can access opportunities owned by or shared with regional managers who report to them

A phone field that provides the full phone number of the seller, a number field that designates the square footage of the listing, and a picklist field that designates the county of the listing should be used as filter criteria because they are fields that can be used to narrow down the report results based on specific values or ranges. A multi-select picklist field that designates features of the listing and a formula field that calculates a price for the listing should not be used as filter criteria because they are fields that cannot be filtered on in reports. References: https://help.salesforce.com/s/articleView?id=sf.reports_filtering.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_fields_unavailable.htm &type=5