Study guide
11.2 Trailhead Playground Hands-On Drill 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.2 Trailhead Playground Hands-On Drill Plan
Key Takeaways Explain This Topic AI
Hands-on review should mirror administrator workflows: inspect evidence, make a scoped change, test with representative users, and document the result.
A Trailhead Playground or Developer Edition org is the safest place to practice Setup navigation, security diagnosis, object changes, reports, flows, and Agentforce concepts.
Drills should cover both successful configuration and failure analysis, such as missing access, bad data, overbroad automation, or report visibility surprises.
The goal is not to memorize clicks but to build a repeatable admin diagnostic routine under closed-reference conditions.
Last updated: May 2026
Practicing Like an Administrator
A hands-on drill is different from clicking through a Trailhead step and forgetting it. In final review, every Playground session should answer four questions: what business problem am I solving, where in Setup would I inspect it, what change would I make, and how would I prove the result is correct. This turns the Trailhead Playground or Developer Edition org into a controlled lab instead of a badge-completion space.
Use one practice org consistently if possible. Create a simple naming convention for test users, permission sets, fields, flows, reports, and dashboards. Add a date or initials if multiple learners use similar material. The goal is not production-grade change management, but the habit matters. Platform administrators work in environments where unclear names and undocumented test changes become support debt.
Drill area Hands-on task What to explain afterward
User access Create or inspect a user, profile, permission set, and permission set assignment Which layer grants app, object, field, and record access.
Object Manager Add a custom field, page layout change, or compact layout change Who sees it, where it appears, and what data quality risk exists.
Lightning App Builder Compare an app page, record page, and home page Which audience each page serves and how activation matters.
Data management Build an import checklist and test a small CSV if safe in the lab How IDs, validation, duplicates, and rollback exports affect the job.
Reports Create a report with filters, grouping, and a folder Why rows or fields may differ by user.
Flow Inspect or build a small record-triggered or screen flow Entry conditions, user impact, testing, and fault handling.
Agentforce Review available setup concepts and trusted AI learning Use case, permissions, grounding, testing, monitoring, and when not to use AI.
Start each drill with inspection before configuration. For access problems, do not immediately assign a broad permission. Inspect the user record, profile, permission sets, permission set groups if present, role, public groups, queues, sharing settings, and field-level security. For report problems, inspect the report type, filters, folder access, dashboard running user if relevant, and sharing. This evidence-first pattern is the difference between an admin who fixes the symptom and an admin who understands the system.
Use a "make it fail" step. Create a test user who lacks access to a field, then observe what changes when you grant field permission. Build a report that excludes records because the report type requires a child object, then change the report approach. Create a validation rule in a lab, test an invalid save, and then ask how that same rule would affect Data Loader, integrations, and flows. Failure drills expose exam traps better than perfect demos.
- Hands-On Drill Workflow
- Name the scenario in one sentence, such as "sales user cannot edit a custom field on accounts."
Identify the possible layers before opening Setup.
Inspect current metadata and record evidence.
Make the smallest lab change that should solve the scenario.
Test as the affected user or with the most realistic available substitute.
Record the Setup path, result, side effect, and rollback step.
Close references and explain the solution from memory.
Data drills deserve extra care because the current outline gives Data and Analytics Management the highest weight. In a lab, prepare a tiny CSV with clean rows and flawed rows. Practice mapping fields, spotting required fields, checking picklist values, and thinking about duplicate rules before import. Even if you do not run a risky operation, write the plan: export first, include record IDs, test a sample, review success and error files, and preserve the mapping. The exam often rewards the planning control more than the button name.
Reports and dashboards should be practiced with visibility in mind. Build a simple report, save it to a folder, and ask which users can open the folder, see the records, and see the fields. Then consider a dashboard. Who is the running user, and what does the viewer actually see? If a manager wants a dashboard but individual users should not see all underlying records, the answer must respect analytics security and business intent.
Automation drills should teach caution. A Flow can solve many admin problems, but a final-review candidate should know when not to automate. If a requirement is unclear, the data is unreliable, or users need a policy decision first, automation can multiply errors. Practice reading entry criteria, record-trigger timing, update targets, fault paths, and testing plans. For the exam, the strongest answer often uses Flow when repeatable logic is needed, but it also includes testing and governance.
Agentforce practice may be more conceptual depending on what is available in the org. Keep it at Platform Administrator depth. Review use cases, permission and data access implications, prompt or agent configuration boundaries, grounding in approved data, testing tools, deployment readiness, channels, monitoring, feedback, and audit information. Also practice saying no. If the use case requires exposing sensitive data without a clear access model, or if deterministic workflow is required, AI may not be the right first choice.
End each Playground session with cleanup notes. Which metadata did you create? Which users or permissions did you alter? Which reports or flows would confuse future practice if left unnamed? In production, cleanup and documentation protect the org. In final review, they protect your mental model. You should be able to return a week later, understand what you built, and repeat the diagnostic lesson without relying on open notes during the exam.