Salesforce-Certified-Administrator Salesforce Certified Administrator (SP25) Free Practice Exam Questions (2025 Updated)

Web-to-Case allows you to create cases from a form on your website.

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

To create a many-to-many relationship between two existing custom objects, the administrator needs to create a junction object that has two master-detail relationships, one to each ofthe custom objects. This will allow each record of one object to be linked to multiple records from another object and vice versa. References:https://hel p.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm&type=5

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or positionwithin the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to 3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharingsettings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References:https://help.salesforce .com/s/articleView?id=sf.contacts_hierarchy.htm&type=5

Freezing a user is a way to temporarily prevent them from logging in to Salesforce without deactivating their user record. This is useful when you need to perform some cleanup tasks before deactivating a user, such as removing them from being referenced in a hierarchy field like Direct Manager. References:https://help.salesforce.com/s/articleView?i d=sf.users_freeze.htm&type=5

The Assignment Rule checkbox is a checkbox that appears on manual case creation pages when assignment rulesare defined for cases. The Assignment Rule checkbox determines whether or not to apply assignment rules to manually created cases. If the Assignment Rule checkbox is selected by default, then any manually created cases will be assigned according to assignment rules instead of being owned by the agent creating them. To prevent this from happening, an administrator can either deselect the Assignment Rule checkbox when creating cases manually; or change the default setting for this checkbox under setup by selecting or deselecting Use active assignment rules by default. References:https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign. htm&type=5

To enable record sharing and collaboration with groups, you need to add the groups related list to the object layouts and configure the Add Record action in the group publisher.

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

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. References:https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

To track assigned licenses and permission sets in Salesforce instead of using a spreadsheet, an administrator should use User Report type on Report object. User Report type allows creating reports that show information about users such as their profile, role, license type, active status, login history etc. It also allows adding fields related to permission sets such as Permission Set Assignments or Permission Set License Assignments. For example, an administrator can create a User Report that shows user name, profile name, user license name, permission set assignments count etc. Login History, Lightning Usage App, or Permission Set Groups are not features that can be used to track assigned licenses and permission sets in Salesforce. References:https://help.salesforce.com/s/articleView?id=sf.reports_report_types_standard_user.htm &type=5

To route new leads to the correct sales person based on thelead address, the administrator should use lead assignment rules that specify criteria based on lead fields such as City, State/Province, or Country, and assign leads that match those criteria to queues or users. Lead assignment rules can be triggered automatically when leads are created or manually by users. Creating a formula field, assigning with an escalation rule, or configuring a validation rule will not route leads to sales people. References:https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

Contact, lead, and person accountare three objects that will have the individual field available for tracking data privacy information when data protection and privacy is enabled for an org. The individual object is an object that stores data privacy preferences and requests for customers who are subject to privacy regulations such as GDPR; it can be linked to contact, lead, or person account records using the individual field. Case and opportunity, account and user, or individual, user, and account are not combinations of objects that will have the individual field available for tracking data privacy information; they either do not store customer data or do not support individual object relationships. References:https://help.salesforce.com/s/articleView?id=sf.individual_object.htm &type=5

Flow builder is an automation tool that allows administrators to create flows that guide users through screens, collect data, and perform actions on records. It can be used to simplify the account creation process by creating a screen flow that shows onlythe essential fields for creating an account and hides any unnecessary fields or sections from the page layout. Approval process, workflow rule, and validation rule are not automation tools that can simplify the account creation process; they are used fordifferent purposes such as approving records, updating fields, or enforcing data quality. References:https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5

Page layout and field level security are two factors that determine whether a user can see a new field on a record. To troubleshoot this issue, the administrator should ensure that the page layout for the user’s profile has been updated to include the new field and that the field level security of the field for the user profile allows read or edit access. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutoverview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.admin_fls.htm &type=5

A Trailhead Playground is a free, online learning environment that allows you to try out Salesforce features and apps. You can use a Trailhead Playground to test out an app from the AppExchange before you install it in your production org.

A sandbox is a copy of your production org that you can use to test changes and new features. You can install an app from the AppExchange in a sandbox to see how it works in your environment.

Testing an app in a production org is not recommended, as it could affect your live data. Checking edition compatibility is important, but it is not a way to try out an app.

To identify new leads entered by interns from existingleads, the administrator should define a record type and assign it to the interns. This will allow them to select a different record type when creating leads, and distinguish them from other leads based on record type. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. References:https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Picklist values, help text, and decimal places are three aspects of standard fields that an administrator can customize to suit their business needs. Picklist values are the options that users can choose from a picklist field; they can be added, edited, or deleted by administrators. Help text is the text that appears when users hover over a field; it can be customized by administrators to provide additional information or guidance for users. Decimal places are the number of digits that appear after the decimal point in a number or currency field; they can be changed by administrators to adjust the precision of the field values. Field history tracking and field name are not aspects of standard fields that can be customized; they are only available for custom fields. References: https://help.salesforce.com/s/articleView?id=sf.customize_picklists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_edit.htm &type=5https://help.salesforce.com/s/articleView?id=sf.customize_fields_ number.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 make it easy for approvers to respond to approval requests, the administrator should configure three settings:

Update the organization’s chatter setting to allow approvals, which enables approvers to approve or reject requests from chatter feeds or email notifications

Enable the organization’s Email approval response setting, which allows approvers to reply to approval request emails with keywords such as APPROVE or REJECT

Add the Items to approve component to the approvers home page, which shows a list of pending approval requests that can be acted upon with one click Specifying initial submission actions within the approval process will not affect how approvers respond to requests. Creating a flow to automatically approve all records will bypass the approval process altogether. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_one_click.htm &type=5

Campaign hierarchy is afeature that allows administrators to organize campaigns into a parent-child relationship, where the parent campaign represents a larger initiative and the child campaigns represent smaller or more specific activities within that initiative. Using campaignhierarchy can help Ursa Major Solar report on campaign ROI by month and series by creating a parent campaign for the series of networking events and creating individual child campaigns for each monthly event. The parent campaign can show the aggregated metrics and ROI for the entire series, while the child campaigns can show the metrics and ROI for each month. Adding different record types for the monthly event types, creating individual campaigns that all have the same name, or configuring campaign memberstatuses to record which event members attended are not solutions for reporting on campaign ROI by month and series; they either do not group campaigns into a hierarchy or do not track campaign metrics or ROI. References:https://help.salesforce.com/s/articleView?id=sf.campaigns_ hierarchy.htm&type=5

Case escalation rules are a way to automatically escalate cases that meet certaincriteria, such as being open for more than a specified time or having a certain priority. Escalation rules can assign cases to a different owner or queue and send email notifications to the support manager or other recipients. References:https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5