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

To help a user who has attempted to log in multiple times and has been locked out of Salesforce, the administrator should reset password on the user’s record detail page and use the unlock button on the user’s record detail page. Resetting password will generate a new temporary password and send it to the user’s email address. Using unlock will restore access for a locked-out user without changing their password or waiting for lockout period to end. Logging in as the user or resetting the password policies will not help a locked-out user log in to Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.users_passwords.htm &type=5https://help.salesforce.com/s/articleView?id=sf.users_unlock.htm &type=5

Get Records is a flow element that allows you to retrieve one or more records from an object that meet certainconditions and store them in a collection variable or a record variable for use later in the flow. You can also choose which fields from those records you want to store in variables. References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_data_getrecords.htm &type=5

To transfer data from a lead custom field to an opportunity field upon lead conversion, an administrator needs to create a custom field on the opportunity object that matches the data typeand length of the lead custom field, and then map the two fields using the lead field mapping tool under setup. This will ensure that the value of the product category field on the lead is copied to the corresponding field on the opportunity when the leadis converted. References:https://help.salesforce.com/s/articleView?id=sf.leads_customize_map.htm &type=5

Muting permission sets allow you to remove permissions that are granted by a permission set group.

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

To surface important values based on stage of opportunity , an administrator should use Path Key fields feature on Opportunity object . This feature allows adding up to five fields that display key information about each stage along path . Users can edit these fields inline without leaving path . For example , an administrator can add Amount , Close Date , Next Step , Probability , and Stage fields as key fields for Opportunity path . Opportunity Processes , Dynamic Forms , and Workflow Rules are not tools for surfacing important values based on stage of opportunity . References : https :// help . salesforce . com / s / articleView ? id = sf . lex_path_setup_key_fields . htm & type = 5

Native debug feature is atool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings that indicate where the flow failed or might fail. References:https://help.salesforce.com/s/articleView?id=sf .flow_debug.htm&type=5

A gauge component shows a single value along with its percentage of a total value within predefined ranges using colors (red-yellow-green). It is useful for showing keyperformance indicators (KPIs) such as total sales amount and progress towards sales goal. References:https://help.salesforce.com/s/articleView?id=s f.dashboards_gauge_component_type.htm&type=5

Permission sets are used to grant additional permissions and access settings to individual users without changing their profiles or requiring a new profile to be created. You can use permission sets to extendusers’ functional access without changing their existing profiles. To meet the request of giving comprehensive edit access on Campaigns to a few marketing users who have read-only access by default, you need to create a permission set with edit access onCampaigns and assign it to those users. References:https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5

Path is a feature that can be used to visually see the sales stages on an opportunity page. Path can include guidance and key fields for each stage to help users move opportunities along the sales process. Guidancecan provide tips, policy information, or best practices for each stage. Key fields can display important fields that users need to fill in or update for each stage. References:https://help.salesforce.com/s/articleView?id=sf.path_overview.htm &type=5

Maximum invalid login attempts, password complexity requirements, and number of days until expiration are three password policies that anadministrator can configure to encourage employees to choose secure and appropriate passwords for their Salesforce accounts. Maximum invalid login attempts determines how many times a user can enter an incorrect password before being locked out of Salesforce. Password complexity requirements determine how complex a user’s password must be based on criteria such as length, case sensitivity, alphanumeric characters, etc. Number of days until expiration determines how often users must change their passwords. References:https://help.salesforce.com/s/articleView?id=sf.security_password_policies.htm &type=5

Process Builder is a tool that can be used to automate business processes by creating record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can be usedto create a flow that executes when an opportunity is closed won and creates a client welcome task and a welcome email for the primary contact. References:https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm&type=5

Guided selling, validation rules, and required fields on the page layout are three options that can be used to ensure sales reps fill out key fields when working on an opportunity through the process. Guided selling allowsadministrators to add prompts and guidance at each stage of the path to help reps move forward with confidence. Validation rules allow administrators to enforce data quality and business logic by preventing reps from saving records that do not meet certaincriteria. Required fields on the page layout allow administrators to make certain fields mandatory for reps to enter before saving records. Configuring opportunity path can help reps visualize and update key fields at each stage, but it does not make themrequired or prevent them from moving forward without entering them. Using flow to mark fields required is not possible because flows cannot modify page layouts or field properties. References: https://help.salesforce.com/s/articleView?id=sf.path_guided_se lling.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fields _defining_field_properties.htm&type=5

Component visibility filters are a way to make the record pages more dynamic and easier to use by showing or hiding components based on certain criteria. For example, users can see different components based on their profile, role, record type, or field values. References:https://help.salesforce.com/s/articleView?id=sf.app_builder_component_visibility.htm &type=5

An external ID is a custom fieldthat has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using Salesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating records from an external system because it is generated by Salesforce and may not match with the external system’s IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier whenimporting and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records from an external system because it may not be available or consistent across systems. References:https://help.salesforce.com/s/articleView?id=sf.custom_fiel d_attributes.htm&type=5

Two considerations when installing a managed package in a sandbox are:

The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.

The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data andmetadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm &type=5

Report type is a tool that can be used to pull contact fields into the custom report for Event. Report type defines the set of records and fields available to a report based on the relationships between a primary object andits related objects. To edit the custom Event report type and add fields related via lookup, go to Setup > Report Types and select the Event report type. Then click Edit Layout and drag the fields from the Contact object to the layout. References:https://help.salesforce.com/s/articleView?id=sf.reports_builder_create_report_type.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

Master-detail lookup is atype of relationship field that can be used to create a relationship between Account and Shoe and prevent orphaned Shoe records. Master-detail lookup establishes a parent-child relationship between two objects, where the parent record controls certain behaviors of the child record, such as security, ownership, and deletion. If the parent record is deleted, all the child records are deleted as well. References:https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5

To automate applying discounts on opportunity products when an opportunity is won, the administrator should use Flow Builder, which is a tool that allows creating complex business processes with clicks. The administrator can create anautolaunched flow that runs when an opportunity is updated, checks if its stage is “Closed Won”, and updates its related opportunity products with discounts from a formula or variable. Approval Process, Prebuilt Macro, and Formula Field are not able to update related records based on criteria. References:https://help.salesforce.com/s/articleView?id=sf.flow_build_overview.htm &type=5