Free Salesforce Advanced-Administrator Practice Exam with Questions & Answers | Set: 3

Debug Log is a tool that captures information about database operations, system processes, and errors that occur when executing a transaction or running a unit test. Debug Log can help troubleshoot issues related to triggers, workflows, validation rules, or other custom logic by showing the order of execution and the values of variables and expressions

Validation rules and page layouts are two tools that can be used to require data to be entered in a field and improve data quality on a record in Salesforce. Validation rules are a way to enforce data quality and integrity by checking the values of fields before a record is saved and displaying an error message if the values do not meet the specified criteria. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Page layouts can also make fields required so that users must enter a value before saving a record.

Role hierarchy is a sharing mechanism that should be used to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers. Role hierarchy is a way to grant access to records based on the user’s position in an organization’s hierarchy of roles. Role hierarchy can grant users access to records owned by or shared with users below them in the hierarchy for objects that have organization-wide defaults set to Private or Public Read Only. By using role hierarchy, the administrator can ensure that directors can access opportunities owned by or shared with regional managers who report to them

Salesforce Authenticator is an app that adds an extra layer of security for logging into Salesforce by requiring users to verify their identity using their mobile device after entering their username and password on Salesforce login page. To see how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two methods:

A) Create a new view In Identity Verification History, specifying Method.

Identity Verification History is a tool that shows information about each identity verification event for users in your org, such as the date and time, the verification method used, the IP address, and the status of the verification. By creating a new view in Identity Verification History and specifying the method as Salesforce Authenticator, an administrator can see how many users have used the app to verify their identity when logging in. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5

D) Export Login History and filter based off of Authentication Method Reference.

Login History is a tool that shows information about each login attempt for users in your org, such as the date and time, the username, the source IP address, the login type, and the status of the login. By exporting Login History as a CSV file and filtering based on the Authentication Method Reference column, an administrator can see how many users have used Salesforce Authenticator as their authentication method when logging in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

To debug platform events in Apex code, you need to set a debug log on the Automated Process entity. This entity represents an automated process user that runs flows and processes in your org. By setting a debug log on this entity, you can capture the events that are published and consumed by your flow and Apex code, as well as any errors or exceptions that occur during the execution. References: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_debug.htm https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm &type=5

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by replacing it with fictitious data. This can help you protect your data privacy and comply with regulations while testing in a realistic environment. You can use the data masking tool to mask data for standard and custom objects, including person accounts, and choose from different masking formats and options. References: https://help.salesforce.com/s/articleView?id=sf.data_mask.htm &type=5

When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible. References: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.htm &type=5

Giving the account owner Read access to both the Account and the Quota objects will give access to all Item records. Since Item is a junction object between Account and Quota, users need to have at least Read access to both parent objects to see Item records. If users have access to only one parent object, they will not be able to see Item records related to the other parent object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

Roll-up Summary calculations are performed after processes and workflows are executed, which means that any changes made by processes or workflows will not be reflected in the roll-up summary field until after the transaction is committed. This could cause inaccurate or outdated information to be delivered to the agent if the flow relies on the roll-up summary field value.

A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce. A permission set can be used to extend users’ functional access without changing their profiles. You can assign permission sets to individual users or groups of users based on their business needs. In this case, you can create a permission set with Read access to the Government ID field on the custom object and assign it to the Institutional Team users who need access to this field via reports. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_sets_create.htm &type=5