Salesforce Salesforce Certified Administrator (SU24) Salesforce-Certified-Administrator Exam Dumps: Updated Questions & Answers (December 2025)

A roll-up summary field is a type of field thatcalculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References:https://help.salesforce.com/s/articleView?id=sf.fields_about _roll_up_summary_fields.htm&type=5

Big Deal Alerts are notifications that are sent to users when an opportunity reaches a certain amount, probability, or stage. They can be configured by administrators to alert sales reps or managers when they have a high likelihood of winning a big deal. Key Deals are a feature of Einstein Opportunity Scoring that shows the top opportunities based on their score and stage, but they do not send notifications. Activity Timeline is a component of Lightning Experience that shows the past and upcoming activities related to a record, but it does not notify users of big deals. Performance chart is a type of report chart that shows how well users or teams are performing against their goals, but it does not alert users of big deals. References:https://help.salesforce.com/s/articleView?id=sf.forecasts3_big_deal.htm &type=5

The Knowledge Lightning component is a component that allows users to access articles from the Service Cloud Console app. However, if users want to access articles from a different app that does not use the console, they can use the Knowledge related list instead. The Knowledge related list shows articles related to a record based on data categories and shows article details such as title, summary, rating, and view count. To add the Knowledge related list to a record page, an administrator can use the page layout editor and drag and drop the Knowledge related list to the appropriate section on the page layout. References: https://help.salesforce.com/s/articleV iew?id=sf.knowledge_lightning_component.htm&type=5https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.htm &type=5

To share report folders with different groups of users with different levels of access, an administrator can use folder sharing settings under setup. Folder sharing settings allow administrators to share report folders with public groups, roles, roles and subordinates, territories, or portal roles with view or edit access. In this case, the administrator can share the Helpdesk folder with Support Agents with view access so they can run Helpdesk reports but not edit them; and share the R&D folder with Support Managers with edit access so they can view and edit R&D reports. References:https://help.salesforce.com/s/articleView?id=sf. reports_builder_folders_sharing.htm&type=5

Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.

References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.quick_actions_overview.htm &type=5

Flow Builder supports creating a wizard that can collect user input and perform actions.

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

To update the shipping address on selected orders associated with an account when the shipping address is changed on the account, the administrator should create a screen flow on the account page that lets the reps choose which orders they want to update with the new address. This will give them more control and flexibility over which orders are affected by the change. An autolaunched flow on either object will notallow reps to select specific orders, and may cause unwanted updates or errors. A screen flow on the order page will not be able toupdate multiple orders at once. References:https://help.salesforce.com/s/articleView?id=sf.flow_build_screen.htm &type=5

One possible reason why a manager receives an error when trying to approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields thatare updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process arevisible does not solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page layouts. References:https://help.salesforce.com/s/articleView?id=sf.app rovals_considerations.htm&type=5

An ID variable is a type of variable that can store an ID value of a record or a record type in a flow. It can be used to store the ID of a record type for later use in a flow, such as assigning it to a record or using it in a condition. A boolean variable is a type of variable that can store a true or false value in a flow. A textvariable is a type of variable that can store a text value in a flow. A record variable is a type of variable that can store one or more field values of a record in a flow. References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_eleme nts_variables.htm&type=5

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can require users to select a product type or check a needs review box when saving an opportunity by using an OR function that evaluates both fields. If neither field is populated, then the validation rule will prevent users from saving records with an error message. References:https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5