Ace the Salesforce Advanced-Administrator Exam: Ultimate Preparation Guide

To resolve the issue with the Process Builder, the administrator should do the following steps:

Review the Error Email for the Process Builder and rectify the issues. The error email contains information about what caused the error and how to fix it.

Deactivate the Process Builder in production. This will prevent further errors from occurring while the administrator fixes the Process Builder.

Fix the Process Builder in a sandbox and migrate the change to production. This will ensure that the Process Builder is tested and validated before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.flow_troubleshoot_error_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_deploy.htm &type=5

A primary account relationship is a feature that allows you to link a contact to a single account as its primary account. A primary account relationship is required on a contact regardless of the page layout settings or the contact to multiple accounts feature. This means that you cannot remove the primary account from a contact, but you can change it to another account. You can also add secondary accounts to a contact if you have enabled the contact to multiple accounts feature. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.contacts_fields.htm &type=5

To help ensure that users who are viewing reports and dashboards are who they say they are, DR should require a high assurance session when exporting or printing reports and dashboards. A high assurance session requires users to verify their identity using multi-factor authentication before accessing sensitive data or functionality in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.security_high_assurance_session_level.htm &type=5

One possible reason for the changes to case routing is the difference in the order of execution between before save flow triggers and workflow rules. Before save flow triggers run before assignment rules, which means that any field updates made by the flow can affect how the assignment rules assign the case. Workflow rules run after assignment rules, which means that any field updates made by the workflow do not affect how the assignment rules assign the case. Therefore, replacing workflow rules with before save flow triggers can change the case routing logic. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_of_execution.htm &type=5

Go into the user record and freeze the user is the action that should be taken to ensure the user’s access is immediately revoked. Freezing a user is a way to temporarily prevent a user from logging in to Salesforce without deactivating their user record or changing their profile. Freezing a user can be useful when an employee has resigned or left the company and their access needs to be removed immediately. Freezing a user does not affect the ownership of records or email alerts that are assigned to them

Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will build this functionality. A master-detail relationship creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent. A Roll-up Summary field calculates values from related child records, such as count, sum, min, or max. In this case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and subtract it from the Invoice amount to get the current outstanding value. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

One possible cause of unexpected changes to record values is having multiple automation tools that update the same field on the same object. This can create conflicts and overwrite each other’s values. To resolve this issue, the administrator should consolidate automation tools and use only one tool per object and field combination. This can help avoid confusion and ensure consistent results. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automatio n/automation_considerations

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. References: 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

Email logs are files that provide information about email delivery and activity in your Salesforce org. Email logs contain details such as sender, recipient, subject, date, status, error code, and more for each email sent or received within a specified time range. You can use email logs to investigate issues with email delivery or performance in your org. In this case, you can use email logs to check if the status update emails were sent successfully or if there were any errors or failures. References: https://help.salesforce.com/s/articleView?id=sf.email_logs.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.email_logs_format.htm &type=5