Salesforce CRT-211 - Prepare for your Advanced Administrator Certification Exam (SP25)

Check the Reevaluate Workflow Rules After Field Change box on the Approval Process Field Update Action is what the administrator should do to troubleshoot the issue. This option allows the approval process field update to trigger any workflow rules or processes that are based on the updated field value. If this option is not checked, the approval process field update will not trigger any workflow rules or processes, and the Process Builder will not fire

Two reasons why the user cannot find the Location object while using Data Loader are:

The label of Location may have been changed. The label of an object is the name that is displayed in the user interface and can be different from the API name that is used by Data Loader and other tools. If the label of Location has been changed to something else, such as Site or Venue, then the user may not be able to find it by searching for Location in Data Loader. The user should check the API name of the object in Object Manager or use the Describe Global operation in Data Loader to see all available objects and their labels.

The user’s profile needs create access to Location. The user’s profile determines what objects and fields they can access and what actions they can perform on them, such as creating, reading, updating, or deleting records. If the user’s profile does not have create access to Location, then they will not be able to load records into that object using Data Loader. The user should check their profile permissions in Setup or ask their administrator to grant them create access to Location.

The other two options are incorrect because:

Data Loader should only be used with standard objects is not a reason because Data Loader can be used with both standard and custom objects, as long as they are accessible and queryable via the API.

Location has a master-detail field to Account is not a reason because having a master-detail field does not prevent an object from being available in Data Loader, as long as it meets the other requirements such as accessibility and queryability.

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.

To access a junction object record, a user needs to have at least read permission on one of its master records and on the junction object itself. If the user does not have access to either master record, they cannot access the junction object record. If the user has access to both master records, they can access the junction object record with the most permissive access level of either master record. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relation ships_manytomany.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

A permission set is a collection of settings and permissions that can extend users’ functional access without changing their profiles. By creating a permission set with view All on Accounts and assigning it to the service and sales managers, an administrator can grant them access to all account records in their org without modifying their existing profiles. References: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm &type=5

To resolve the issue with the Process Builder, the administrator should do the following steps:

Review the Error Email for the Process Builder and rectify the issues. The error email contains information about what caused the error and how to fix it.

Deactivate the Process Builder in production. This will prevent further errors from occurring while the administrator fixes the Process Builder.

Fix the Process Builder in a sandbox and migrate the change to production. This will ensure that the Process Builder is tested and validated before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.flow_troubleshoot_error_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_deploy.htm &type=5

Product schedules are features that allow administrators to track revenue or quantity over time for products in opportunities or orders. Product schedules can be either revenue schedules or quantity schedules, depending on whether the product is sold by amount or by quantity. Product schedules can be either standard or customizable, depending on whether they use predefined settings or custom settings.

Line item schedules are records that represent each installment of revenue or quantity for a product over time. Line item schedules are created automatically when a product with a product schedule is added to an opportunity line item or an order product.

One limitation of product schedules is that line item schedules are unavailable in Process Builder and Workflow. This means that administrators cannot use these tools to automate actions based on line item schedules, such as sending email alerts, creating tasks, updating fields, or invoking flows. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_product_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.orders_line_item_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.product_schedule_considerations.htm &type=5

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_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. 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.ht m&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm &type=5