Study guide
11.1 Final 30-Day Salesforce Admin Review Plan
Salesforce Admin Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Administrator Orientation and Official Source Control
1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow
2 Chapter 2: Configuration, Setup, User Management, and Org Controls
2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab
3 Chapter 3: Security, Access, Identity, and Sharing Model
3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab
4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling
4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab
5 Chapter 5: Sales, Marketing, Service, and Support Applications
5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab
6 Chapter 6: Data and Analytics Management
6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab
7 Chapter 7: Automation, Flow, Approval, and Operational Processes
7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab
8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange
8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab
9 Chapter 9: Agentforce for Platform Administrators
9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab
10 Chapter 10: Integrated Salesforce Admin Scenario Labs
10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy
11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy
11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review
11.1 Final 30-Day Salesforce Admin Review Plan
Key Takeaways Explain This Topic AI
A strong final month uses the current 8-domain Platform Administrator outline, not a generic Admin checklist or older outline.
Prioritize weak domains with hands-on tasks, scenario diagnosis, and closed-reference recall instead of passive rereading.
Data and analytics, configuration, object design, automation, and Agentforce deserve explicit review time because they appear across realistic admin scenarios.
Final review should produce decision rules, Setup navigation fluency, and testable evidence from a Playground or Developer Edition org.
Last updated: October 2026
Building the Final Month Around the Current Outline
The last 30 days are not for collecting more random Salesforce Admin resources. They are for reducing uncertainty against the current 8-domain Platform Administrator outline: Configuration and Setup, Object Manager and Lightning App Builder, Sales and Marketing Applications, Service and Support Applications, Productivity and Collaboration, Data and Analytics Management, Automation, and Agentforce. Keep the search-friendly Salesforce Admin label in your notes, but let the current Trailhead outline control your schedule.
Start with evidence. Create a tracker with one row per domain and columns for confidence, last hands-on practice date, common Setup paths, missed-question themes, and a one-sentence decision rule. If a row says only "read Trailhead," it is not done. The final month should prove that you can diagnose the scenario, name the setup area, choose the least risky admin action, and explain what to test after the change.
Review window Main focus Required evidence
Days 30 to 24 Source control and baseline assessment Current 8-domain map, baseline timed set, weak-domain list.
Days 23 to 17 Configuration, security, objects, and Lightning pages User access drill, object model drill, page layout or Lightning page comparison.
Days 16 to 10 Data, analytics, sales, service, and collaboration Import/export plan, report visibility check, sales and case scenario notes.
Days 9 to 4 Automation, Agentforce, and mixed scenarios Flow decision notes, AI trust checklist, integrated practice sets.
Days 3 to 1 Closed-reference recall and logistics Pacing plan, test-day checklist, maintenance awareness, no new resource sprawl.
Use domain weights to budget time, but do not let them create blind spots. Data and Analytics Management is the largest current domain at 17 percent, and it also connects to security, reports, dashboards, imports, validation, and sharing. Configuration and Setup, Object Manager and Lightning App Builder, and Automation are each substantial enough to deserve repeated hands-on review. Agentforce is 8 percent, which is small enough to be overlooked but large enough to affect the result and the real admin role.
A practical review session has four parts. First, read or review the official topic for 10 to 20 minutes. Second, do a hands-on action in a Trailhead Playground or Developer Edition org. Third, answer original practice scenarios or local practice-bank items without notes. Fourth, write down why each missed or guessed answer was tempting. The correction note should be specific, such as "field-level security controls field visibility, not record row visibility" or "a report type can exclude parent records without children."
Avoid the common final-month error of converting every weakness into flashcards. Flashcards can help with vocabulary, but the exam is scenario-heavy. For example, the useful memory is not just that permission sets grant access. The useful memory is that profiles and permission sets can grant object and field permissions, sharing controls record visibility, permission set groups combine assignments, and a user complaint must be separated into app access, object access, field access, and record access before changing anything.
The final month should also include deliberate Agentforce review at administrator depth. You do not need to become an AI implementation specialist for this credential, but you should know admin-relevant boundaries: use cases, setup implications, permissions, grounding with trusted data, testing before deployment, trust and security review, monitoring, feedback, and when not to use AI. A good exam answer will usually protect data, user expectations, and operational reliability before choosing an impressive AI feature.
Weekly Review Operating Rules
Use Salesforce-approved learning and your own original notes, not alleged live exam questions or answer dumps.
Do at least one hands-on task for every study block, even if the task is only inspecting Setup and explaining what you see.
Time at least two mixed practice sets before test week so pacing is not a new skill on exam day.
Keep a missed-question log organized by root cause, not by emotional reaction.
Stop adding new resources in the final week unless an official source corrects a fact.
Verify current registration details if Salesforce updates the exam guide, registration screen, delivery rules, score, or fees.
Scenario-based review is the closeout skill. If a prompt describes a user who can open a report but sees fewer records than a manager expects, do not jump to report folder access. Ask whether the user can open the report, whether fields are missing, whether filters or report type are excluding rows, whether the running user matters on a dashboard, and whether record sharing hides rows. This same diagnostic pattern works across the guide: isolate the layer, then choose the smallest durable fix.
Use the final three days for consolidation. Rebuild the domain map from memory. Write the Setup paths you know, then check them. Recite the no-reference rule and remove any expectation that notes, browser tabs, Trailhead pages, or personal reference sheets will be available during the exam. Review the official caveats: Salesforce requires certified professionals to complete annual release maintenance modules for their certifications, and missing deadlines can cause expiration. Passing the exam is not the end of being responsible for the credential.