Salesforce Certified Advanced Administrator (CRT-211) Practice Test - Questions Answers, Page 24

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.

Reference: 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

To restore the deleted Review records, you need to restore both the Account and Product master records from the Recycle Bin. A master-detail relationship is a type of relationship that links two objects together and enforces a parent-child relationship between them. A master-detail relationship affects the security and deletion of the child records. If you delete a master record, all of its detail and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or subdetail record, you must first restore its parent record.

Reference: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.recyclebin_overview.htm&type=5

The change can be made through the desktop site by using the Edit All button on the related list of products on the opportunity page. This button allows you to edit multiple products at once and change their price book entries. You cannot use this button on the mobile app, as it is not supported. You also cannot change the price book on the opportunity once it has products added to it, unless you remove all the products first.

Reference: https://help.salesforce.com/s/articleView?id=sf.opportunity_products_edit.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.opportunity_products_change_pricebook.htm&type=5

To make sure that the changes are in production, you need to add the components to an outbound change set and deploy it to production. 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 need to add the master-detail field and all the affected profiles to an outbound change set in your sandbox org and then deploy it to your production org.

Reference: 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

VisualStudio Code is a recommended tool to make the change in the displayed text in one of the Lightning web components. VisualStudio Code is an integrated development environment (IDE) that supports Salesforce development tools such as Salesforce Extensions for Visual Studio Code, Salesforce CLI, and Lightning Web Components. You can use VisualStudio Code to create, edit, debug, and deploy Lightning web components and other Salesforce metadata. To make the change in the displayed text, you need to open the HTML file of the Lightning web component in VisualStudio Code and modify the text element accordingly.

Reference: https://developer.salesforce.com/tools/vscode https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components

A joined report is a type of report that allows you to create multiple report blocks that provide different views of your data. Each report block can have its own fields, columns, sorting, and filtering. A joined report can only be created from summary or matrix reports. You can use a joined report to show data from different report types or data sources on a single report. In this case, you can use a joined report to show Accounts with Open Cases by creating two report blocks: one for accounts and one for cases with a filter for open status. You can then join the two blocks by a common field such as Account ID or Account Name.

Reference: https://help.salesforce.com/s/articleView?id=sf.reports_joined_format.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_examples_joined.htm&type=5

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.

Reference: 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

Multiple automation tools have been used and the automation is executed in a different order. This could cause some cases to route in unexpected ways, because the before save flow might override or conflict with the assignment rules or other automation tools that run after the record is saved. The administrator should review the order of execution and ensure that the flow logic is consistent with the other automation tools.

Reference: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm

One possible reason why the before trigger fails is that the code could be trying to create duplicates in the archive when it is unable to. A before trigger is a type of trigger that executes before a record is saved and can be used to validate or modify record data. In this case, the before trigger is supposed to save the original version of a record to an external database before it is updated or deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try to create duplicate records in the external database when it is not allowed or possible. This could cause the trigger to fail and prevent the record from being saved in Salesforce.

Reference: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_context_variables.htm