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

Identity Verification History is a tool that tracks the verification methods used by users when they log in to Salesforce via multi-factor authentication. It can help identify any issues or errors related to verification methods such as email, phone, or app. Login History is a tool that tracks the login attempts and status of users who access Salesforce. It can help identify any issues or errors related to login credentials, IP addresses, browser types, or locations.

A junction object is a custom object with two master-detail relationships that allows you to create many-to-many relationships between two objects. In this case, the Job Application object can be used as a junction object to link the Application object and the Job Posting object, so that each application can be related to one or more job postings, and each job posting can have one or more applications.

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

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.

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

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also have decision elements that evaluate conditions and determine which path to follow in the flow. By combining the two flows into one with decision elements, the administrator can ensure that the flow runs in the correct order and updates the field on the child record after it is created by the first flow.

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

Change sets are tools that allow administrators to move customizations such as fields, page layouts, profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators need to establish a deployment connection between a source org (such as a sandbox) and a target org (such as production). Then, administrators can create an outbound change set in the source org that contains the components they want to deploy, and upload it to the target org. In the target org, administrators can view and validate the inbound change set before deploying it to their org.

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

Debugging a flow allows administrators to test how a flow behaves before activating it or making changes to it. Debugging a flow runs it in real time using test data provided by the administrator or default values from the flow. However, debugging a flow also performs any actions defined in the flow, such as creating, updating, or deleting records. Therefore, if a flow has a delete element that deletes a record based on certain criteria, debugging the flow will delete the test record even if the flow is inactive.

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

A custom summary formula is a formula that calculates values from summary fields in reports such as sum, average, min, max, etc. Custom summary formulas can use functions such as PREVGROUPVAL to compare values from different groups in reports. For example, to calculate the year-over-year change in dollar amount of opportunities, an administrator can create a custom summary formula that uses PREVGROUPVAL to compare the sum of amount from this year's group with the sum of amount from last year's group, and divide it by last year's sum of amount.

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

change sets are tools that allow administrators to move customizations from one Salesforce org to another. However, change sets do not track dependencies or conflicts between components in different orgs, so administrators need to manually verify that all required components are included in the change set and that they do not overwrite existing customizations in the target org. To avoid losing changes in production due to deploying an incomplete or incorrect change set, administrators should push the change set to another sandbox first and test it there before deploying it to production.

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

The Analyze button is a tool that allows administrators to view the performance metrics of a Lightning record page, such as load time, component count, and component type. The Pages menu is a tool that allows administrators to access the Lightning Page Performance Optimizer app, which provides recommendations and best practices for improving the performance of a Lightning record page