Study guide

1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

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

1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

Key Takeaways Explain This Topic AI

Hands-on practice in a Trailhead Playground or Developer Edition org should accompany every official study topic.

Use Setup navigation, configuration changes, test records, reports, dashboards, and Flow experiments to turn outline labels into administrator skill.

Practice-bank work should follow a learn, configure, test, explain, and retest loop rather than isolated question drilling.

Agentforce labs should emphasize admin boundaries: access, grounding, testing, trust, monitoring, feedback, and escalation.

Last updated: May 2026

Build a Lab, Then Study Like an Administrator

The official prep guidance points candidates toward Trailhead and Salesforce-approved learning, and this guide adds hands-on Trailhead Playground or Developer Edition practice. A Playground or Developer Edition org is where the outline becomes visible. You can open Setup, inspect Object Manager, create users, compare profiles and permission sets, build fields, test validation, import sample data, create reports, configure dashboards, build a simple Flow, and explore available Agentforce setup areas. Reading tells you what a feature is; the lab teaches what breaks when it is configured poorly.

A good lab is intentionally modest. Do not try to recreate a full enterprise org on day one. Create a small business scenario, such as a services company that tracks accounts, contacts, opportunities, cases, and internal onboarding tasks. Add a few users with different roles. Create test records owned by different users. Build one custom object only when a standard object does not fit the scenario. Then test visibility, page layout, reporting, and automation from more than one user perspective. This produces exam-relevant contrast.

Lab asset What to practice Scenario question it prepares you to answer

Trailhead Playground Guided module exercises and safe Setup exploration Can I perform the feature, not just name it

  • Developer Edition org Longer independent experiments Can I design a small admin solution end to end
  • Test users Permission and sharing comparison Is this an access issue or a record visibility issue

Sample records Data quality and reporting behavior Do filters, ownership, validation, and required fields behave as expected

Practice bank tracker Weak-domain diagnosis Which official topic should I revisit next

For Configuration and Setup, start with organization settings, users, profiles, permission sets, roles, public groups, queues if available, and app access. Do not merely click through. Ask what the setting controls, who is affected, and how you would test the result. If you grant object access through a permission set, log in or use an appropriate test method to confirm the user can perform the intended action and no more. Least privilege is a recurring administrator principle.

For Object Manager and Lightning App Builder, build the habit of separating data model, page experience, and security. A field can exist on an object, appear or not appear on a page layout, and still be hidden by field-level security. A Lightning record page can organize components, but it does not replace object permissions. A custom object may solve a business need, but it also creates reporting, relationship, ownership, sharing, and lifecycle responsibilities. The exam often tests these boundaries.

For Data and Analytics Management, practice with imports, updates, transfers, mass actions, exports, backups, validation tools, reports, report types, dashboards, and sharing effects on report visibility. Use small data sets and intentionally create errors. Try importing a record that violates a validation rule. Build a report where one user sees more rows than another. Create a dashboard and inspect how the running user affects what viewers see. These controlled failures teach diagnosis.

Learn, configure, test, explain, retest loop

Learn the official concept in Trailhead or Salesforce documentation.

Configure a small version in a Playground or Developer Edition org.

Test with records and users that reveal security, data, and automation effects.

Explain the result in plain language without notes.

Answer local practice-bank items for that category.

For every miss, return to the official source and repeat a targeted lab.

For Automation, keep experiments narrow. Build a record-triggered Flow only after defining the entry condition, data changes, user impact, and test records. Avoid treating automation as a magic replacement for process clarity. If a requirement is really about preventing invalid input, a validation rule may be cleaner. If it requires collecting approvals, an approval process or Flow-supported process may fit. If it requires a one-time data cleanup, automation may be the wrong tool. The administrator judgment is choosing the maintainable mechanism.

For Agentforce, keep labs and notes at Platform Administrator depth. Identify a realistic use case, define which users and channels are in scope, list what data grounds responses, decide what should remain out of scope, test expected and risky prompts, review monitoring or analytics concepts, and plan escalation or feedback handling. Do not treat AI as a universal answer. Some workflows require deterministic approvals, audited human decisions, or strict data boundaries. The admin role is to operate responsibly inside trust and security limits.

The practice bank should never become the whole study plan. The local bank has categories and item counts that roughly match the current outline, including Agentforce AI. Use it after hands-on and official review. A missed item is a signal, not a verdict. Classify the miss: wrong source fact, weak Setup navigation, confused security layer, data/reporting misunderstanding, automation tradeoff, application feature gap, or AI governance gap. Then fix the underlying skill in the org.

End each study session with a two-minute administrator memo. Write the domain studied, the Setup path used, the configuration changed, the test performed, the failure observed, and the rule you would apply in a business scenario. This creates durable recall while staying within exam-security boundaries. Over time, those memos become your personal source-controlled guide: no copied exam questions, no guarantees, just official concepts tested against real platform behavior.