Study guide

10.5 Flow Automation and Change Control 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.5 Flow Automation and Change Control Integrated Lab

Key Takeaways Explain This Topic AI

Flow automation should begin with a business event, entry criteria, user impact, data requirements, and a rollback or disable plan.

Admins should choose screen flows, record-triggered flows, scheduled paths, approval processes, and workflow alternatives based on the work pattern, not preference.

Testing must include happy paths, negative paths, bulk behavior, permissions, validation rules, and downstream reporting effects.

Change control requires sandbox build, documentation, user acceptance, deployment planning, activation timing, and post-release monitoring.

Last updated: May 2026

Lab scenario: automate a customer handoff

A company wants a consistent handoff when an opportunity is marked Closed Won. The sales rep should confirm implementation details, a customer onboarding case should be created, the account should be flagged as a customer, and the account owner should receive a task for the kickoff call. The admin must decide what belongs in automation, what belongs in user confirmation, and how to release the change without disrupting current sales work.

Start with process discovery. Ask what event starts the process, who owns the result, which records are created or updated, what fields are required, what exceptions exist, and what reports should change. In this lab, the event is an Opportunity stage change to Closed Won. The handoff case needs Account, Contact, Priority, Product Area, and Description. The account update sets Customer Status to Active Customer. The task reminds the owner to schedule a kickoff call. Exceptions might include renewals, internal test deals, partner-led implementations, or opportunities without a primary contact.

Automation choice Best fit Setup path Lab caution

Screen flow User needs guided input before save or action completion Setup > Flows and Lightning page or action Users may skip optional fields unless designed well

Record-triggered flow Work should happen automatically when a record changes Setup > Flows Entry criteria and recursion prevention matter

Scheduled path Work should happen after a delay or time condition Setup > Flows Time-based behavior must be tested with date changes

Approval process Formal submit, approve, reject workflow is needed Setup > Approval Processes Not every review process needs approvals

Validation rule Save should be blocked until a condition is met Object Manager > Validation Rules Blocking can break imports and integrations

Choose the design. One option is a record-triggered flow on Opportunity that runs when Stage changes to Closed Won and required fields are present. It creates a Case, updates the Account, and creates a Task. A second option is a screen flow launched from an action, where the rep confirms onboarding details and the flow performs the handoff. The screen flow gives better user confirmation, while the record-triggered flow is more automatic. For this lab, build a record-triggered flow with strict entry criteria and a validation rule that prevents Closed Won when core handoff fields are missing.

Build in a sandbox or Trailhead Playground. Go to Setup > Flows , create a record-triggered flow on Opportunity, and trigger it when a record is updated. Entry criteria should include Stage equals Closed Won and a condition that detects the relevant change so the flow does not create duplicate cases on every later edit. Use Get Records to find related data only if needed. Use Create Records for the onboarding Case and Task. Use Update Records for the Account. Label every element clearly. Add a description explaining the business owner and release date.

Expected observations in a successful test: when a valid opportunity moves from Negotiation to Closed Won, one onboarding case is created, one kickoff task is created, the account customer status changes, and reports can identify the new case. When the opportunity is edited later without changing stage, no duplicate case appears. When required handoff fields are missing, the validation rule blocks the stage change with a clear message. When a user lacks access to a field or object, the flow behavior should be understood and documented based on how the flow runs.

Test failure modes deliberately. Try closing an opportunity without a primary contact. Try a bulk update of several opportunities. Try an opportunity linked to an account that is already an active customer. Try a user who can close opportunities but cannot create cases if your design depends on user context. Try a duplicate stage update. Try a Data Loader update. Try a deactivated owner or missing queue. A lab that only proves the happy path is not enough for administrator readiness. Automation failures usually appear at boundaries.

Think about order of execution and side effects. Validation rules, duplicate rules, flows, assignment rules, escalation rules, and other automation can interact. Creating a case may trigger case assignment rules or additional flows. Updating an account may trigger account automation. Sending notifications may surprise users if test data looks real. Use debug tools and Flow error emails, but do not rely on error emails as the support process. Create a place to record automation owner, purpose, entry criteria, fields touched, related objects, expected volume, and emergency deactivation steps.

Move through change control. Document the requirement, configuration changes, test cases, user acceptance evidence, deployment components, activation timing, and communication plan. Use change sets, DevOps Center, source-driven deployment, or the repo's approved method depending on the org. Deploy inactive where possible, then activate during the release window after dependencies are present. Confirm profiles, permission sets, fields, validation rules, record-triggered flow activation, and report changes all moved. After release, monitor Flow error emails, sample records, dashboards, and user feedback.

Review prompts before the quiz:

Why might a screen flow be better than a record-triggered flow for some handoffs?

How would you prevent duplicate onboarding cases after later opportunity edits?

Which bulk and permission tests should be included before activation?

What release evidence would you keep for the change advisory record?

What is your emergency plan if the flow blocks revenue operations after release?