1.4 Domain Weights, Agentforce, and Study Prioritization

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.4 Domain Weights, Agentforce, and Study Prioritization

Key Takeaways Explain This Topic AI

The current Platform Administrator outline has eight domains, with Data and Analytics Management highest at 17 percent and Agentforce included at 8 percent.

Weights guide time allocation, but no domain should be ignored because scenario questions often combine setup, security, data, automation, and applications.

Agentforce preparation should stay at administrator depth: use cases, permissions, setup implications, grounding, testing, trust, deployment, monitoring, and support boundaries.

The local practice bank categories should be used as reinforcement after official study, not as a replacement for Salesforce-approved sources.

Last updated: October 2026

Weight the Domains, Then Integrate Them

The current Salesforce exam guide lists eight domains: Configuration and Setup at 15 percent, Object Manager and Lightning App Builder at 15 percent, Sales and Marketing Applications at 10 percent, Service and Support Applications at 10 percent, Productivity and Collaboration at 10 percent, Data and Analytics Management at 17 percent, Automation at 15 percent, and Agentforce at 8 percent. This is the study map for this guide. It replaces the older outline that applied before December 15, 2025.

Weights help you budget time. Data and Analytics Management deserves extra attention because it is the largest listed domain at 17 percent. Configuration and Setup, Object Manager and Lightning App Builder, and Automation each carry 15 percent, which makes them core pillars. The 10 percent application and productivity domains still matter because they create the business context where setup, data, reports, and automation are tested. Agentforce at 8 percent is smaller, but explicit; skipping it is a current-outline mistake.

Domain Weight Study priority Scenario connection
Data and Analytics Management 17% Highest single domain Imports, reports, dashboards, backup, sharing impact
Configuration and Setup 15% Core Users, company settings, security setup, app access
Object Manager and Lightning App Builder 15% Core Objects, fields, page layouts, record pages
Automation 15% Core Flow, approvals, business process enforcement
Sales and Marketing Applications 10% Important Leads, opportunities, campaigns, productivity context
Service and Support Applications 10% Important Cases, support processes, queues, service productivity
Productivity and Collaboration 10% Important Tools that help users work and communicate
Agentforce 8% Explicit current topic AI use cases, trust, testing, operations boundaries

Do not translate weights into isolation. A realistic scenario may ask why a sales manager cannot see pipeline data. The issue might involve role hierarchy, sharing rules, report filters, report folder access, dashboard running user, opportunity ownership, forecast configuration, or field-level security. That scenario touches Configuration and Setup, Sales Applications, Data and Analytics, and sometimes Object Manager. The exam habit is to locate the failure layer, not to guess the domain label.

Agentforce requires the same integrated thinking. Salesforce Trailhead content for Agentforce includes agent basics, trusted agentic AI, planning, Agentforce Builder basics, grounding with data, data libraries, testing, deployment, channel connection, monitoring, analytics, and feedback or audit data. For this administrator guide, stay at platform administrator depth.

You should understand when an AI agent can support service or productivity, which users should have access, what data can ground responses, how testing and monitoring reduce risk, and when not to use AI because the process needs deterministic approval, legal review, sensitive data controls, or human judgment.

Scenario: service leadership wants an Agentforce-powered support experience to answer common customer questions. An administrator should not simply enable a feature and hope. The admin should ask what channels are in scope, which knowledge or data libraries ground responses, how permissions limit access, how outputs will be tested, what escalation path exists when confidence is low, what feedback or audit data will be reviewed, and which owner monitors performance. This is not deep AI engineering; it is responsible platform operations.

Study allocation model

Spend the first pass on official Trailhead prep for all eight domains.

Add extra hands-on cycles for Data and Analytics, Configuration and Setup, Object Manager, and Automation.

Use application domains to practice full business scenarios rather than isolated feature lists.

Include Agentforce in every weekly review so it does not become a final-week scramble.

After official study, use the local practice bank categories to reveal weak spots and retest them in a Playground.

The local practice bank has 200 items distributed across categories such as configuration setup, object manager, automation, data analytics, service support, sales marketing, productivity, and Agentforce AI. Treat that bank as reinforcement. It is not an official source, and it should not be treated as a source of live exam content. Use it the way a professional uses test cases: identify a weak behavior, return to official material and hands-on configuration, then retest.

A practical schedule might divide a 20-hour first pass by weights, then add integrated labs. Spend more time on the 15 to 17 percent domains, but reserve blocks for every domain. For example, after studying Object Manager, build a custom object, add fields, configure a page layout, create a report type if appropriate, and consider how users receive access. After studying automation, build a Flow in a test org, examine entry conditions, and think about data side effects. After studying Agentforce, outline an AI use case and list controls before configuration.

Exam traps often arise when candidates treat feature names as answers. A permission set is not automatically the solution to every access problem. A dashboard folder does not automatically grant access to underlying records. A validation rule does not clean existing bad data by itself. An AI agent does not remove the need for testing, monitoring, or permission design. Weights help you decide where to spend hours; scenario judgment decides whether those hours turn into correct answers.