Changed Advanced-Administrator Exam Questions

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.

Two combined automation tools that the administrator can use to create the task record and assign based on date criteria are:

Create a formula field to capture the MAX date. A formula field is a custom field that calculates a value based on other fields or expressions. In this case, a formula field can be used to capture the maximum value between Estimated Shipping Date and Client Need By Date fields and store it as a date value.

Make a Process Builder to create the task. A Process Builder is an automation tool that allows you to create processes that perform actions based on certain criteria. In this case, a Process Builder can be used to create a task record when a certain condition is met and assign its due date based on the formula field value.

The other two options are incorrect because:

An approval process is an automation tool that allows you to route records for approval based on certain criteria and approval steps. It does not create or assign tasks based on date criteria.

A workflow rule is an automation tool that allows you to perform actions based on certain criteria and evaluation time. It does not create or assign tasks based on date criteria.

References: https://help.salesforce.com/s/articleView?id=sf.customize_functions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_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

To manage both B2C and B2B customers, CK should use Person Accounts and Contacts to Multiple Accounts features. Person Accounts allow CK to store information about individual consumers without requiring a separate account record. Contacts to Multiple Accounts allow CK to associate a contact with multiple accounts, such as their employer and their personal account. References: https://help.salesforce.com/s/articleView?id=sf.account_person_behavior.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account_contact_rel_overview.htm &type=5