Salesforce Administrator Certification: 25 Free Practice Questions
This set contains 25 original Salesforce Certified Platform Administrator practice questions with explanations. These are independently written study scenarios, not leaked or official exam items. Use them to test reasoning about access, object relationships, sales and service processes, data quality, automation, and Agentforce.
Salesforce’s published Platform Administrator exam outline covers configuration and setup; Object Manager and Lightning App Builder; Sales and Marketing; Service and Support; Productivity and Collaboration; Data and Analytics Management; Automation; and Agentforce. Release-specific details can change, so verify the current official outline before booking.
Answer and explanation: No. Deactivate the user when access must end and reassign record ownership where necessary. Salesforce retains the historical user identity for audit and data relationships. Deleting a user is not the ordinary offboarding workflow.
Answer and explanation: Assign a permission set, or a permission set group where several permissions belong together. Profiles provide a baseline while permission sets add privileges. Review effective access rather than assuming an additive permission set can remove an existing grant.
Answer and explanation: Begin with organization-wide defaults and the role hierarchy, then use sharing mechanisms when access does not follow the hierarchy. Object permission is also required; record sharing cannot grant access to an object the user cannot read.
Answer and explanation: Login hours are a profile-level security setting. Confirm which profile applies to those users and whether other authentication and session controls are needed for the business requirement. Do not confuse login hours with a scheduled Flow.
Answer and explanation: A master-detail relationship enables roll-up summary fields on the master object for supported child data. Validate the intended ownership, sharing, and deletion behavior before converting a relationship. A lookup relationship does not automatically offer the same roll-up capability.
Answer and explanation: Record types can determine the available business-process choices and picklist values, while page layout assignments control field and related-list presentation. Record type alone does not replace field-level security.
Answer and explanation: No. Lookup and master-detail relationships have different behavior and configuration choices. Check the lookup deletion settings and business dependencies before changing or deleting related records. Never assume automatic cascade deletion from the word “relationship.”
Answer and explanation: A validation rule evaluates a logical condition and can block saving with a clear error. A formula field calculates a value but is not a substitute for rejecting invalid edits. Test edge cases and error-message clarity.
Answer and explanation: Lead conversion associates an account and contact and can create an opportunity depending on the conversion choice and configuration. Review record matching and conversion mappings so the process does not create unnecessary duplicates.
Answer and explanation: Lead assignment rules can route eligible leads to users or queues using ordered rule entries. Test priority and default behavior so the first matching rule does not undermine another routing requirement.
Answer and explanation: Campaign members link campaigns to leads or contacts and store participation status. Define meaningful member statuses and consistent reporting before measuring responses or campaign impact.
Answer and explanation: Case assignment rules can apply ordered criteria to assign cases to users or queues. Confirm trigger conditions and queue membership; assignment is distinct from a customer-facing auto-response.
Answer and explanation: Case escalation rules evaluate qualifying cases and time-based criteria to apply escalation actions. Define business hours and the clock behavior carefully, then test in a sandbox before relying on the schedule.
Answer and explanation: Support processes control relevant case statuses and can be used with record types. Combine them with suitable page layouts, assignments, and permissions; do not solve a process difference only by changing how a page looks.
Answer and explanation: A Task models work to be completed, such as a follow-up call. An Event represents a scheduled calendar activity with a time interval. Choose based on how the team will track the activity and report on completion.
Answer and explanation: A private Chatter group can limit group membership and discussions. That does not replace object and record security: verify both the group’s visibility and permissions to any linked records or files.
Answer and explanation: Examine publisher trust, managed versus unmanaged package behavior, requested permissions, licensing, data access, and the plan to test and remove the package. Install in an appropriate test environment first, especially for packages that modify automation or metadata.
Answer and explanation: The Data Import Wizard may suit supported objects and simpler imports, while Data Loader is commonly chosen for larger or more complex operations. Assess object support, mapping, error recovery, and backup needs before selecting a tool.
Answer and explanation: An External ID field can support matching during an upsert. Define uniqueness and duplicate-handling behavior and test conflicting input. Display names alone are usually a poor integration key.
Answer and explanation: Matching rules define how possible duplicates are identified, while duplicate rules determine the response, such as warning or blocking under configured conditions. Test legitimate near matches so the solution does not hide valid contacts.
Answer and explanation: Choose or configure a report type that includes the primary object records with or without related records, rather than a type that requires matches in both objects. Report type relationships shape which records can appear before filters are applied.
Answer and explanation: Evaluate a dynamic dashboard that runs as the logged-in user. Dashboard and source-report folder access still matter, as do product limits and any other record-level permissions. Testing with different profiles is essential.
Answer and explanation: A before-save record-triggered Flow is designed for fast field updates to the triggering record. Use the appropriate trigger criteria and test interactions with validation rules and other automation before activating.
Answer and explanation: A screen Flow supplies a user interface to collect and validate input. An autolaunched Flow runs without screens and is usually invoked by other logic. Choose based on who interacts with the process and whether human input is needed.
Answer and explanation: Inspect the agent’s configured identity, object permissions, record access, grounding sources, and applicable security controls. Then use the testing and preview capabilities to reproduce the failure in scope. Do not give broad access merely to silence an authorization error.
Answer each question before reading its explanation, then recreate the topic in a Salesforce learning environment. For access questions, test with two users whose permissions differ. For automation questions, draw the flow path and confirm the real order of execution. For reporting questions, inspect how record visibility changes results. Track weak objectives and revisit them using Trailhead and product documentation.
These scenarios are not a substitute for hands-on administration or the issuer’s current preparation guide. Do not rely on memorized answers alone; configuration context matters.
Consult the Salesforce Certified Platform Administrator exam guide and Salesforce Trailhead certification overview for requirements and the current curriculum.