Study guide
9.4 Testing, Deployment, Monitoring, and Feedback Workflows
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
9.4 Testing, Deployment, Monitoring, and Feedback Workflows
Key Takeaways Explain This Topic AI
Agentforce testing must cover answer quality, security boundaries, allowed actions, fallback behavior, and channel behavior before activation.
Deployment is an operational release, so admins should use version notes, pilot audiences, change windows, training, and rollback or deactivation steps.
Monitoring and analytics help identify poor answers, unsupported requests, action failures, usage patterns, escalation gaps, and data-source problems.
Feedback loops are part of governance; admins need a process to triage user feedback and convert it into configuration, content, or permission changes.
Last updated: May 2026
Testing beyond the happy path
Agentforce testing is broader than checking whether one sample prompt returns a polished answer. The admin must test whether the agent gives useful answers, stays inside scope, respects permissions, handles missing information, runs actions correctly, escalates when needed, and behaves the same way in the intended channel. Preview testing in Agentforce Builder is useful, but it is only the first layer.
A strong test plan starts with a prompt inventory. Collect realistic requests from service reps, sales users, internal employees, customers, managers, and admins. Include complete requests, vague requests, misspellings, slang, sensitive requests, unsupported asks, and attempts to retrieve data the user should not see. For a service agent, test common questions, angry customer language, entitlement exceptions, warranty limits, case status questions, and transfer requests.
Test area What to verify Example evidence
Grounded answers Uses approved knowledge or records and does not guess Prompt result with source review.
Permission boundaries Restricted users cannot access hidden data Test transcript from low-privilege user.
Actions Creates or updates records correctly Created records, field values, owner, and validation results.
Fallback Escalates unsupported or low-confidence requests Case, queue, chat transfer, or instruction response.
Channel behavior Works in the target app, console, chat, or site User acceptance test in the actual channel.
Monitoring Captures usage, errors, and feedback Analytics and feedback review plan.
Testing must include records with realistic data quality. Perfect demo records hide problems. Include incomplete accounts, private cases, hidden fields, unpublished knowledge, duplicate contacts, inactive owners, old entitlements, and records owned by users in different roles. If the agent will call a flow, test validation errors, required field gaps, duplicate rules, assignment rules, and fault paths. A user should receive a clear response when an action fails.
Security testing is not optional. Test as an admin, then test as a standard internal user, a manager, a service rep, an external user, and any other intended persona. Ask for fields hidden by field-level security. Ask for records outside sharing access. Ask the agent to ignore instructions. Ask for content from a different customer account. A safe launch requires evidence that the agent refuses, escalates, or cannot retrieve restricted data.
Deployment should be treated like a release. The admin should know which version is being activated, which audience receives access, which channel is connected, what training is needed, and how to turn the agent off if a problem appears. If the org uses change sets, DevOps Center, metadata deployment, or managed packages for related configuration, the agent work should be coordinated with those release practices where supported. Do not make a Friday afternoon production activation for a customer-facing agent without support coverage.
Deployment checklist:
Confirm business approval of use case, audience, and data sources.
Save version notes for instructions, subagents or topics, grounding sources, and actions.
Complete preview testing and persona-based user acceptance testing.
Confirm permission sets, app visibility, tab visibility, channel settings, and agent access assignments.
Train support users on what the agent can do, what it cannot do, and how to report issues.
Activate for a pilot audience before broad release where practical.
Document deactivation, rollback, and escalation steps.
Monitoring closes the loop. Salesforce Agentforce learning paths emphasize analytics, monitoring, utterance analysis, and feedback or audit data. At admin scope, this means reviewing usage volume, unresolved requests, transfer rates, user feedback, action failures, common intents, and conversations where the answer was poor or risky. Monitoring should lead to action: update knowledge, narrow instructions, add examples, fix permissions, remove stale grounding, or train users.
Feedback workflows need an owner. A thumbs-down rating or rep complaint is not useful unless someone triages it. Create a queue or regular review meeting for agent feedback. Categorize issues as content gap, permission problem, instruction problem, action failure, unsupported use case, channel issue, or user training issue. Then make controlled changes and retest. Avoid editing instructions reactively after one complaint unless the issue is a security or compliance risk.
Study trap: do not activate because the agent works for the admin in preview. Admin accounts often have broad access, clean records, and knowledge of the desired answer. The certification answer should favor test evidence across personas, channels, records, and failure cases, followed by monitoring and feedback after release.