Salesforce Certified Platform Administrator: Complete 2026 Study Guide

Exam facts, release caveat, and maintenance

The exact credential name is Salesforce Certified Platform Administrator. Salesforce Platform Administrator is the display code used on this site. The official guide does not publish an alphanumeric exam code, so none should be invented.

As verified August 21, 2026, the official guide lists 60 scored multiple-choice questions, up to five additional unscored questions, and 105 minutes. The English passing score is listed as 68%, with Japanese at 65%. Delivery is proctored online or at a test center. No prerequisite is required, although the audience description recommends six or more months of Salesforce administrator experience.

Certification does not end after the exam. Salesforce requires a Platform Administrator maintenance badge once per year. The current official schedule lists the Spring '26 badge as available April 23, 2026 and due April 16, 2027. Dates are subject to change. Missing the assigned deadline can cause certification expiration, so rely on the live schedule and Trailblazer profile.

Use a layered administration model

Separate five layers in every scenario. First, the license determines which products and capabilities the user can receive. Second, profiles and permission sets determine object, field, system, and app capability. Third, organization-wide defaults and sharing mechanisms determine which records are visible. Fourth, record types, page layouts, Lightning pages, and apps shape process and presentation. Fifth, automation and agents act within configured execution contexts.

Confusing these layers creates common exam errors. A Lightning component visibility filter does not secure the field through reports or API. A role does not grant object permission. A permission set cannot enable a product absent from the license. A dynamic dashboard respects viewer access but does not grant records. Agent instructions cannot override a missing object permission.

Section 1: Configuration and Setup

Company settings include locale, time zone, currency management, fiscal year, business hours, and defaults. Distinguish business hours from login hours: business hours support service timing, while profile login hours restrict when assigned users may log in. Session settings and identity verification protect authentication; Setup Audit Trail records administrative changes.

Usernames must be globally unique. Users have a locale, language, time zone, profile, role where used, license, and optional feature licenses. Users cannot simply be deleted. Before deactivation, transfer records and examine scheduled jobs, integrations, approvals, dashboards, and other references. Freeze can block login immediately while deactivation dependencies are resolved.

Prefer a small number of baseline profiles and additive permission sets. Permission set groups package job access. Muting permission sets suppress selected permissions in a group. Regularly review assignments because additive access accumulates over time.

Organization-wide defaults establish the record-access baseline. Role hierarchy can open visibility upward. Sharing rules open access to groups of users based on ownership or criteria. Teams, queues, public groups, and manual sharing solve other record collaboration needs. Start restrictive and open only what the requirement supports.

Section 2: Object Manager and Lightning App Builder

Lookup relationships are loosely coupled. Master-detail relationships tie child ownership and sharing to the master, can cascade delete, and support roll-up summary fields. A junction object commonly uses two master-detail relationships to model many-to-many associations. Decide relationship type from lifecycle, ownership, optionality, reparenting, roll-up, and deletion behavior.

Custom fields include text, number, date, picklist, relationship, and formula fields. Formula fields calculate values dynamically. Cross-object formulas traverse relationships. Picklist dependencies constrain available values. Deleting a field can break formulas, validation, flows, reports, layouts, integrations, and historical analysis; review dependencies and export needed data first.

Record types expose different business-process values and page layouts to assigned users. Sales processes govern Opportunity Stage values; support processes govern Case Status values. Lightning App Builder composes pages and component visibility. Page layouts control fields, buttons, actions, and related lists. Quick actions streamline context-specific work. None of these replaces object or field security.

Sections 3–5: Sales, Service, and Productivity

Sales and marketing

Leads represent unqualified prospects. Assignment rules route them to users or queues. Conversion can create an Account, Contact, and optionally an Opportunity, with field mappings and matching choices. Opportunity stages and Path guide the sales process. Collaborative Forecasts aggregates future opportunity value by periods and categories. Campaigns and campaign members track marketing initiatives, leads or contacts, and response statuses.

When a question mentions routing an incoming prospect, think lead assignment. When it mentions stage guidance, think Path. When it asks who responded to an event, think campaigns and campaign members. Treat scoring, forecasting, territories, and Einstein features as licensed capabilities whose exact availability must be verified.

Service and support

Cases represent customer issues. Queues hold work. Case assignment rules route cases. Auto-response rules acknowledge submitters. Escalation rules respond when time and criteria exceed service expectations, often using business hours. Support processes define status values and combine with record types for distinct service workflows.

Einstein for Service can support classification, summaries, or assistance depending on current licensing and configuration. AI does not remove the need for clean case data, permissions, monitoring, human review, and escalation.

Productivity and collaboration

Tasks represent work to complete; events represent scheduled time. Chatter groups can be public, private, or unlisted according to supported behavior. Mobile experiences depend on Lightning pages, compact layouts, actions, navigation, and visibility. Lightning apps group navigation and utility experiences.

Before installing an AppExchange package, review publisher trust, managed or unmanaged package behavior, permissions, data access, dependencies, licensing, support, upgrades, and uninstall impact. Test in a sandbox. A marketplace listing is not approval to grant administrator access.

Section 6: Data and Analytics Management

The Data Import Wizard provides guided import for supported objects and moderate volumes within current limits. Data Loader supports larger and repeatable operations, exports, upsert, and authorized delete capabilities. Upsert matches a Salesforce ID or external ID, updates matches, and inserts nonmatches. Stable external IDs make migrations rerunnable.

Before any mass operation, define selection criteria, export a backup, test in a sandbox, review automation and relationships, suppress unintended email or integration effects, run a bounded batch, reconcile, and preserve error files. Hard delete bypasses the Recycle Bin and deserves stricter authorization.

Matching rules define how records are compared. Duplicate rules determine whether matching records are allowed, warned, or blocked. Validation rules block an invalid save according to a formula. Write actionable messages and test user edits, imports, integrations, and automation because execution contexts differ.

Report types define which object relationships and fields are reportable. A with-or-without relationship preserves primary records lacking children. Row-level formulas calculate per row; summary formulas calculate at group or grand-total levels. Bucket fields classify report results without changing stored records. Joined reports combine blocks but can be harder to maintain.

Sharing determines report rows. Folder sharing controls access to the report or dashboard artifact. Dashboards have a running context. Dynamic dashboards show data according to the logged-in viewer and are subject to current edition limits. Dashboard filters reduce duplication, while subscriptions and refreshes operationalize delivery.

Section 7: Automation

Select automation by event and interaction. Before-save record-triggered flows efficiently change fields on the triggering record. After-save flows create or update related records and perform actions requiring the saved record. Screen flows guide users. Autolaunched flows package reusable logic. Schedule-triggered flows process eligible records at defined times.

Use precise entry conditions and change detection. Bulkify data operations by avoiding record queries and writes inside unnecessary loops. Add fault paths and operational ownership. Build idempotent logic so retries or repeated events do not create duplicate records.

Order of execution explains why validation rules, flows, assignment rules, and other automation can interact. A later update can cause another save cycle. Test the entire transaction rather than one flow in isolation.

Approval processes are designed for human review with entry criteria, assigned approvers, submission behavior, record locking, approval and rejection actions, recall, delegation, and final actions. Keep automated candidate creation separate from human authority when the policy requires an accountable decision.

Section 8: Agentforce

Agentforce is appropriate for bounded conversational tasks using approved topics, instructions, knowledge, and actions. It should not replace deterministic validation, approvals, or security where those provide stronger guarantees. Define supported intents, prohibited behavior, uncertainty responses, and escalation before building.

Security is layered. The user needs agent access and the underlying object, field, record, flow, Apex, prompt, or action permissions as appropriate. Investigate effective access and execution context when an action fails. Do not solve authorization errors by granting blanket administrator rights.

Agent Builder instructions should be specific, testable, and grounded in approved information. Use conversation preview for representative questions, paraphrases, ambiguous requests, unsupported topics, injection-like attempts, missing permission, invalid action input, and fault behavior. Confirm actions before high-impact changes and start with reversible operations.

Third-party prompts, actions, and agent templates require publisher, permission, data use, dependency, licensing, support, change, and uninstall review. Pilot narrowly, monitor feedback, regression-test configuration changes, and maintain an immediate suspend and retirement path.

Eight-week preparation plan

Week 1: Configure company settings, users, licenses, profiles, permission sets, groups, login controls, and audit review in a disposable org.

Week 2: Build private sharing with roles, queues, groups, and sharing rules. Test object, field, and record access independently.

Week 3: Create custom objects, lookup and master-detail relationships, a junction object, formulas, record types, processes, layouts, quick actions, and Lightning pages.

Week 4: Practice leads, conversion, opportunities, Path, campaigns, forecasts, case queues, assignment, auto-response, escalation, tasks, events, Chatter, mobile, and package evaluation.

Week 5: Stage Import Wizard and Data Loader exercises with external IDs, duplicate rules, validation, backups, errors, and reconciliation.

Week 6: Build custom report types, row and summary formulas, joined reports, dashboards, filters, subscriptions, and dynamic dashboard persona tests.

Week 7: Implement before-save, after-save, screen, autolaunched, and schedule-triggered flows. Test bulk, faults, recursion, order of execution, and approval paths.

Week 8: Build a bounded Agentforce pilot with approved synthetic knowledge, a confirmation-gated action, permissions, preview tests, suspension, and cleanup. Recheck the live guide and maintenance schedule.

Projects that prove applied administration

The secure sales and service org foundation creates personas, access, relationships, record types, Lightning pages, lead and case routing, mobile collaboration, audit evidence, and deactivation tests.

The data quality, analytics, and Flow lab performs reversible migration, external-ID upsert, duplicate and validation controls, role-aware reports and dashboards, five Flow patterns, approvals, failure injection, and recovery.

The governed Agentforce pilot defines topics and instructions, secures synthetic knowledge and CRM records, exposes a confirmation-gated draft-case flow, benchmarks conversations, pilots narrowly, responds to incidents, and retires every asset.

Scenario strategy and common traps

Identify the layer first. A request for more records is sharing, not a profile. A request for one extra object permission is a permission set, not Public Read/Write. Different statuses and layouts suggest record types and processes. A data-quality block suggests a validation rule. A guided wizard suggests a screen flow. A related record after save suggests an after-save flow. A human exception decision suggests approval.

Reject answers that solve one user's access by making the org public, solve a missing license by adding a permission set, secure a field only by hiding it on a page, mass-delete without backup, or fix an agent by granting administrator. Prefer least privilege, reversible changes, explicit ownership, test personas, and documented release behavior.

• Profiles for every exception: use additive permission sets and groups.
• Roles confused with permissions: roles primarily affect record visibility, not object capability.
• Page layouts treated as security: enforce field-level security separately.
• Unreconciled imports: source must equal successes plus errors.
• Flows without entry criteria: excessive execution and recursion follow.
• Reports tested only as admin: real users may see fewer rows or fields.
• Agent instructions treated as authorization: underlying security remains decisive.
• Ignoring maintenance: missing the annual badge can expire the credential.

Readiness checklist

You are approaching readiness when you can administer users and licenses; distinguish profiles, permission sets, roles, and sharing; model relationships; configure record types and Lightning experiences; route leads and cases; use collaboration and mobile features; choose import tools; prevent duplicates and invalid data; build reports and dashboards; select Flow types; reason about order of execution; implement approvals; troubleshoot Agentforce permissions and behavior; and explain annual maintenance.

Use the five-phase roadmap, answer the 50 original questions, review the 40 flashcards, and complete all three projects. Practice performance does not guarantee a passing result.

Official references

• Salesforce Certified Platform Administrator exam guide
• Salesforce certification maintenance schedule
• Prepare for the Administrator credential trailmix
• View and manage users
• Organization-wide sharing defaults
• Relationship considerations
• Data Loader
• Custom report types
• Flow types
• Approval processes
• Agentforce documentation

Continue learning

• Five-phase Platform Administrator roadmap
• 50 original practice questions
• 40 flashcards
• Three hands-on projects
• Salesforce Agentforce Specialist roadmap
• PrepKloud editorial policy

Frequently asked questions