Login Forensics is a Salesforce feature that allows you to monitor and analyze login behavior and trends in your org. It can help you identify and prevent brute-force password attacks by showing you th e number of login attempts, successes, and failures per user, location, and device. You can also set up alerts to notify you when a user exceeds a certain number of login failures or when a login originates from an unusual location or device. References: h ttps://help.salesforce.com/s/articleView?id=sf.security_loginforensics.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.security_loginforen sics_alerts.htm & type=5

When the feature for Contacts to multiple Accounts is enabled, a Contact can have a direct relationship with multiple Accounts. However, one of these relationships must be designated as the pri mary Account relationship. This relationship is required on a Contact regardless of the page layout settings and cannot be removed unless the Contact is deleted or merged with another Contact. References: https://help.salesforce.com/s/articleView?id=sf.sha red_contacts_set_up.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.shared_contacts_considerations.htm & type=5

A validation rule on the Opportunity Product object to require custom date fields based on the produc t family will ensure that the data is captured properly. A validation rule can check if the product family matches the service plan and if so, require the start and end date fields to be filled out. This way, AW Computing can capture the term length for ea ch service plan sold. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm & type=5

Two practices that the administrator should adhere to in order to ensure a successful deployment to production are:

Add permissions and access settings to outbound change sets in addition to the dependent component list. This can help avoid deployment errors or access issues caused by missing permissions or settings for the components in the change set. For example, if the change set includes a new custom object, the administrator should also include the object permissions, field-level security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This can help test the change set for any errors or conflicts before deploying it to production. Deployment validations simulate the deployment without actually making any changes and report any issues or warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the change set. It can be deployed along with other components as long as they are compatible and have the required dependencies.

Formula field and Dynamic Forms should be created to meet the requirements because a formula field can be used to count the number of open opportunities over US$10 ,000 related to an account using a roll-up summary filter condition, and Dynamic Forms can be used to display or hide a component on an account page based on a visibility filter using the formula field value. References: https://help.salesforce.com/s/articleView?id=sf.customize_functions_i_z.htm

Ex port Data Settings is a feature that allows you to control which users can export data from Salesforce and how much data they can export at a time. You can enable or disable the Export Reports permission for different profiles or permission sets, and set a maximum number of records that can be exported per hour for your org. You can also restrict the export of sensitive data by using field-level security or encryption. References: https://help.salesforce.com/s/articleView?id=sf.admin_exportdata.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm & type=5

Flows deployed with change sets are inactive by default and need to be manually activated in the destination org before they can run. Deploying or redeploying a flow with change sets creates a new version of the flow in the destination org, which preserves the previous versions and allows for rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are automatically added to the change set when a flow is added

As explained in question 3, a price book is a list of products and their prices for a specific segment of customers o r market. By creating a new price book for the U.K product pricing, Northern Trail Outfitters (NTO) can offer different prices for their products in the U.K market due to shipping and raw material cost differences. The price book can also specify which cur rency is used for the prices, such as pounds or euros. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks_def.htm & type=5

Escalation rules are rules that automatically escalate cases if they have not been resolved within a certain time frame or meet certain criteria such as priority or status. Escalation rules can perform actions such as changing ownership of cases, sending email notifications, or creating tasks for users or queues. By using escalation rules, AW Computing ca n ensure that cases are properly prioritized and handled within their SLA time limit. References: https://help.salesforce.com/s/articleView?id=sf.cas e_escalation_rules_overview.htm & type=5

A roll-up summary field is a type of field th at 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 relatio nship 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. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm & type=5 ht tps://help.salesforce.com/s/articleView?id=sf.fields_defining_field_types.htm & type=5