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

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.

Reference: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.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.

Reference: 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 high assurance session is a type of session security level that requires users to verify their identity using a second factor of authentication, such as Salesforce Authenticator, a verification code, or a security key. Administrators can configure certain actions or permissions to require a high assurance session, such as exporting reports, viewing encrypted data, or accessing connected apps.

If users are able to run reports but are taken to a login screen and prompted for additional verification when they try to export a report, it could be because exporting is configured to require a high assurance session. This means that users need to use a second factor of authentication to export reports, even if they have already logged in with their username and password.

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

A session security level is a setting that determines how secure a user's session is based on factors such as their login method, their IP address, their browser, or their device. Administrators can configure different session security levels for different user profiles and assign different actions or permissions to each session security level.

Multi-factor authentication (MFA) is a feature that requires users to verify their identity using two or more factors of authentication when they log in to Salesforce, such as their username and password plus a verification code or an app-generated token. MFA can enhance the security of user sessions and prevent unauthorized access.

If an administrator recently implemented MFA with a standard security level selected and is receiving cases that users are unable to log in, they should check the session security level required at login on the user profile. This setting determines what session security level users need to have when they log in based on their profile. If this setting is higher than the standard security level, users may not be able to log in with MFA alone and may need additional factors of authentication.

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

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

A delegated administrator is a user who has been granted limited administrative privileges by an administrator through delegated administration groups. Delegated administrators can perform some administrative tasks without having full access to Setup.

Some functions that delegated administrators can perform are:

B) Build automation and validation rules using screen flows

Screen flows are types of flows that guide users through screens with elements such as text boxes, picklists, radio buttons, etc. Screen flows can also perform actions such as creating records, updating fields, sending emails, etc. Delegated administrators can build automation and validation rules using screen flows if they have been granted access to create and edit flows by an administrator.

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

D) Make updates to permission set configurations

Permission sets are collections of settings and permissions that can extend users' functional access without changing their profiles. Delegated administrators can make updates to permission set configurations if they have been granted access to manage users by an administrator. Reference: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_useradmin_delegated.htm&type=5

A custom summary formula is a formula that calculates values from summary fields in reports such as sums, averages, counts, etc. Custom summary formulas can use functions such as PREVGROUPVAL which returns the value of a field from the previous row at the same grouping level. By using a custom summary formula with the PREVGROUPVAL function, an administrator can create a report to calculate the year-over-year change in the dollar amount of a company's opportunities by subtracting the amount from the previous year from the amount from the current year and dividing by the amount from the previous year.

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

Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.

B) Configure custom duplicate rules.

Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for contacts or other objects.

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

C) Create custom matching rules.

Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads. Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are detected for contacts or other objects. Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5

Knowledge is a feature that allows administrators to create, manage, and share articles that provide information and solutions for common issues or questions. Knowledge articles can be searched by users using keywords or phrases.

To improve its customers' ability to search for knowledge articles, UMS can use two options:

B) Create synonyms for specific search terms.

Synonyms are words or phrases that have the same or similar meanings, such as ''TV'' and ''television'' or ''fix'' and ''repair''. By creating synonyms for specific search terms, administrators can ensure that customers can find relevant articles even if they use different words or spellings than the ones used in the articles.

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

D) Promote specific search terms for specific articles.

Promoted search terms are keywords or phrases that administrators can associate with specific articles to boost their relevance and ranking in search results. By promoting specific search terms for specific articles, administrators can ensure that customers can find the most helpful or popular articles for their queries. Reference: https://help.salesforce.com/s/articleView?id=sf.knowledge_search_promotion.htm&type=5