Study guide

10.6 Agentforce and Adoption Integrated Lab

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

10.6 Agentforce and Adoption Integrated Lab

Key Takeaways Explain This Topic AI

Agentforce scenarios should start with a specific user problem, trusted data sources, access boundaries, testing plan, and human ownership.

Admins need to understand agent use cases, permissions, grounding, testing, deployment channels, monitoring, feedback, and when AI is the wrong tool.

Adoption work includes app design, guidance, training, feedback loops, dashboards, and safe iteration after release.

AI features must respect security, privacy, record access, data quality, and business policy rather than bypassing them.

Last updated: May 2026

Lab scenario: pilot an agent-assisted support experience

A support organization wants to reduce repetitive case triage and help agents answer common product questions. Leadership asks the admin to pilot Agentforce for internal support agents, not for direct customer self-service yet. The agent should summarize case context, suggest next steps from approved knowledge, and help draft internal notes. It should not close cases, promise refunds, expose restricted account data, or answer from unapproved sources. The admin must combine AI readiness with adoption planning.

Start with the use case, not the tool. Define the user, task, data source, allowed action, blocked action, success signal, and owner. For this lab, the user is a service agent. The task is to understand a new case and find approved guidance. The data source is the case, related account fields the agent can already see, and approved knowledge or data libraries configured for the pilot. The allowed actions are summarization and suggestion. The blocked actions include changing financial fields, sending customer messages automatically, or using unapproved policy content.

Planning area Admin question Expected observation Failure mode to watch

Use case What task should the agent help with? The pilot has a narrow support workflow The agent is asked to solve every service problem

Access Which users and permissions are required? Only pilot agents can use the feature Broad access is granted before testing

Grounding Which approved data can inform responses? Suggestions reference trusted case and knowledge context The agent uses stale, incomplete, or unauthorized content

Testing How will outputs be reviewed? Test cases include safe, unsafe, and ambiguous prompts Only successful demos are tested

Deployment Which channel will users use? The agent is available in the intended workspace Users cannot find it or use it outside process

Monitoring How will quality and risk be tracked? Feedback, audit, and usage reports inform iteration Problems are discovered only through complaints

Review setup responsibilities. Agentforce capabilities can involve Agentforce Builder, agents, topics or instructions, actions, grounding with data, testing tools, deployment channels, monitoring, analytics, and feedback or audit data. An admin-level study guide should not require deep developer implementation, but the admin should know the boundaries. Configuration must respect licenses, permissions, data access, and trust settings. If the feature is not available in a practice org, create a written configuration plan and test matrix instead of inventing behavior.

Use permissions carefully. Give access only to the pilot group through permission sets or permission set groups when the org supports them. Confirm that the agent cannot reveal records or fields the user should not see. AI assistance does not remove the need for object permissions, field-level security, sharing rules, and data classification. If a service agent cannot view Opportunity Amount, the agent should not become a back door to that value. Test with users who have different access levels and document the result.

Prepare grounding content. Approved Knowledge articles, well-maintained data libraries, relevant case fields, and trustworthy account context are better than broad unreviewed content. Clean up outdated articles before using them. Add owners and review dates to knowledge where the process supports it. If articles conflict, the agent may produce confusing suggestions. Expected observation: suggestions align with current policy and show enough context for an agent to verify. Failure mode: users trust a fluent answer even when the source content is stale or incomplete.

Build a test matrix. Include a normal billing question, a technical question with an approved article, a case with missing details, a customer asking for a refund outside policy, a prompt that requests restricted account data, and a prompt that asks the agent to close the case. For each test, record expected behavior, actual behavior, source context, user access, and reviewer notes. The best pilot treats AI outputs as recommendations that trained users evaluate. Do not measure success only by whether the text sounds polished.

Decide what not to automate. If an action has legal, financial, safety, compliance, or customer trust implications, require human review unless the organization has formally approved automation. In this lab, the agent can draft an internal note but cannot send a customer email automatically. It can suggest a knowledge article but cannot guarantee a resolution. It can summarize a case but cannot hide uncertainty. A useful admin phrase is: the agent assists the accountable user; it does not replace policy ownership.

Connect the pilot to adoption. Place the agent where agents already work, such as the service console or approved workspace channel. Add concise in-app guidance through Path, Dynamic Forms, utility items, or training links where appropriate, but avoid filling the page with explanatory text. Train supervisors first so they know how to coach agents. Create feedback categories such as helpful, incomplete, wrong source, missing permission, risky suggestion, and not relevant. Track usage, feedback, handle time, case reopen rates, and knowledge article gaps if the org has those measures.

Review prompts before the quiz:

What is the narrow pilot use case, and what actions are explicitly blocked?

Which fields or records should the agent never expose to this pilot group?

Which approved knowledge or data library content needs cleanup before testing?

What unsafe or ambiguous prompts belong in the test matrix?

How will feedback turn into configuration changes, article updates, or training?