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

The order of execution for flows that are configured to run before the record is saved on the same object is unpredictable and may vary depending on factors such as flow version, flow name, or flow creation date. Therefore, it is recommended to avoid creating multiple flows with the same trigger conditions and instead consolidate them into a single flow.

A validation rule can enforce data quality by preventing users from saving records that do not meet certain criteria. In this case, the validation rule can check if both the Sales Engineer and the Account Executive lookup fields are blank, and display an error message if so. This way, the director of sales can ensure that every opportunity has either a sales engineer or an account executive assigned to the deal.

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

When Contacts to Multiple Accounts is enabled, a contact must always be associated with a primary account, even if the account field is not required on the page layout. The primary account determines how the contact is shared and how roll-up summary fields calculate values from the contact records. To remove the primary account from a contact, the contact must be deleted or merged with another contact.

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

A price book is a list of products and their prices for a specific segment of customers or market. By creating a separate price book for the special bundle deal on monitors and keyboards, AW Computing can offer different prices for these products without affecting their standard prices or requiring VP approval. The price book can also specify which products are included in the bundle and which are not.

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

A record type allows administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating a record type for the type of property (single-family home or condo), DreamHouse Realty can assign different page layouts to each record type that display only relevant fields for each property type. The record type can also determine which sales process and path are available for each opportunity.

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

Permission set groups are a combination of permission sets that grant users access to various tools and functions. Muting permission sets are used to remove access that is granted by other permission sets in the group. However, muting permission sets cannot remove object-level access that is granted by Modify All or View All permissions. Therefore, if a user is assigned to a permission set group that gives them Modify All access to Accounts, a muting permission set that mutes Delete access on Account will not have any effect. The user will still have Modify All access on the Account object, which includes Delete access.

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

When creating a new custom object, administrators can choose to mark it as deployed or in development. If an object is marked as in development, it is not visible to users or available in tools such as Data Loader, even if they have access to it through their profile or permission set. To make the object available for data import, the administrator needs to mark it as deployed.

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

The Fields component is a Lightning component that allows administrators to display fields from a record on a Lightning page based on certain conditions or criteria. For example, administrators can use filter logic to show or hide fields based on field values or user profiles. In this case, the administrator can use the Fields component to display fields that only apply to condos based on the value of a field that indicates the type of property.

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

Sharing rules are automatic exceptions to organization-wide sharing settings that grant additional access to records based on record ownership or criteria. By creating a sharing rule on the Account object for all members of the account services role to have Read/Write access, the administrator can allow users in that role to edit and change ownership of Accounts owned by any of their team members, regardless of the organization-wide sharing setting for Account.

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