Pass the Salesforce Salesforce Advanced Administrator CRT-211 Questions and answers with CertsForce

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.

One possible reason why the before trigger fails is that the code could be trying to create duplicates in the archive when it is unable to. A before trigger is a type of trigger that executes before a record is saved and can be used to validate or modify record data. In this case, the before trigger is supposed to save the original version of a record to an external database before it is updated or deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try to create duplicate records in the external database when it is not allowed or possible. This could cause the trigger to fail and prevent the record from being saved in Salesforce. References: https://develop er.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_context_variables.htm

One of the IDs in the batch referenced a record that was in the recycle bin because deleting records with Bulk API does not delete records permanently but moves them to the recycle bin. Therefore, if a record ID in the batch matches an existing record ID in the recycle bin, an ‘entity is deleted’ error will occur.

The equivalent field is the field that matches the dashboard filter field on the source report object. For example, if the dashboard filter is on Account Owner, then the equivalent field on the Opportunity object is Opportunity Owner. Changing the equivalent field ensures that the dashboard filter applies correctly to the Opportunity components. References: https://help.salesforce.com/s/article View?id=sf.dashboard_filters.htm&type=5

 Record-triggered flow is a feature that allows administrators to automate actions that occur when a record is created or updated. Record-triggered flow can perform actions such as updating fields, creating records, sending emails, or invoking Apex code. Record-triggered flow can be used to update the account checkbox field ‘Opportunity Created’ when at least one related opportunity has been created

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. References: https://help .salesforce.com/s/articleView?id=sf.app_manager_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex _pages_assign.htm&type=5

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also send email alerts as part of their actions. To send a notification when a record is deleted and by whom, and to maintain their own discovery information, an administrator can use a flow that runs when a record is deleted, queries the record owner’s email address and discovery information from another object or variable, and sends an email alert with those details. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts.htm &type=5

Field history tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. Field history tracking can help you audit data quality, compliance, or business processes. Field history tracking cannot be configured from Schema Builder, but it can be configured from Object Manager. In Object Manager, you can select an object and enable field history tracking from its settings page. Then, you can choose up to 20 fields per object to track and add the history related list to the page layout. References: https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.h tm&type=5 https://help.salesforce.com/s/articleView?id=sf.schema_builder_overview.htm &type=5

Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users’ access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.

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 the 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: https://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