Study guide
15.2 Data Management Strategy, Data Quality & Integration Governance
Salesforce Accredited Agentforce 360 for Public Sector Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Overview, Architecture & Constituent Data Modeling
1.1 AP-222 Exam Blueprint, Passing Standards & Credential Overview 1.2 Public Sector Solutions Layered Architecture & Industry Common Layer 1.3 Person Accounts & Constituent Data Modeling
2 Chapter 2: Licenses, Permits, and Inspections (LPI) — Intake & Issuance
2.1 Regulatory Authorization Types & Application Intake 2.2 Business License & Permit Issuance, Conditions & Status Tracking 2.3 Application Reviews, Multi-Department Approvals & Renewals
3 Chapter 3: Inspections, Code Enforcement, and Compliance
3.1 Inspection Types, Action Plan Templates & Onsite Visit Execution 3.2 Regulatory Codes, Assessment Indicators & In-Field Checklists 3.3 Regulatory Code Violations, Enforcement Actions & Remediation Workflows
4 Chapter 4: Grants Management & Grantmaking Lifecycle
4.1 Funding Programs, Funding Opportunities (NOFOs) & Public Discovery 4.2 Grant Application Intake, Review Workspaces & Multi-Stage Scoring 4.3 Funding Awards, Disbursement Schedules & Post-Award Reporting
5 Chapter 5: Benefits Management & Assistance Programs
5.1 Benefit Programs, Benefit Schedules & Beneficiary Data Architecture 5.2 Discovery Framework Assessments & Question Versioning 5.3 Rules-Based Eligibility Determination & Recertification Lifecycle
6 Chapter 6: Employee Experience & Emergency Response Management
6.1 Public Sector Employee Experience & Workforce Operations 6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch 6.3 Rapid Resource Allocation, Volunteer Coordination & Contact Tracing
7 Chapter 7: Document Processing, Intelligent Automation & Reporting
7.1 Document Checklist Items, Content Management & Upload Portals 7.2 Intelligent Document Automation (IDA), the Document Workspace & the IDA vs. IDA/IFR Decision 7.3 Intelligent Document Reader (OCR with Amazon Textract) & eSignature Integration 7.4 OmniStudio Document Generation & Dynamic PDF Production 7.5 Public Sector Operational Reporting, Compliance Dashboards & CRM Analytics
8 Chapter 8: OmniStudio for Public Sector — Guided Intake & 360 Views
8.1 OmniScript Architecture, Step Design & Conditional Branching 8.2 Data Prefill Patterns, Context Passing & Save-for-Later 8.3 FlexCard Architecture, Constituent 360 Layouts & Action Frameworks
9 Chapter 9: OmniStudio Integration & Server-Side Processing
9.1 Data Mappers (DataRaptors) — Turbo Extract, Extract, Transform & Load 9.2 Integration Procedures — Action Chaining, Batching & Error Handling 9.3 External API Integrations, HTTP Actions & Named Credentials
10 Chapter 10: Business Rules Engine (BRE) & Dynamic Fee Calculation
10.1 Expression Sets — Calculation Steps, Formulas & Versioning 10.2 Decision Tables & Decision Matrices for Policy Decisioning 10.3 Dynamic Fee Schedules, Calculation Procedures & Regulatory Pricing
11 Chapter 11: Experience Cloud Citizen Portals & Service Console
11.1 Public Sector Experience Cloud Site Templates & Citizen Self-Service 11.2 Guest vs. Authenticated User Journeys & Identity Verification 11.3 Multilingual Localization, Custom Labels & Translation Workbench 11.4 Public Sector Service Console, Workspace Tabs & Omni-Channel Routing
12 Chapter 12: Security, Compliance, Government Cloud & Best Practices
12.1 Data Security, Org-Wide Defaults (OWD) & Sharing Architecture 12.2 Government Cloud Tiers, FedRAMP & DoD Compliance 12.3 Salesforce Shield, Field Audit Trail & Platform Encryption 12.4 Declarative-First Strategy, Process Library & Deployment with IDX Workbench
13 Chapter 13: Agentforce & AI Innovation for Public Sector
13.1 Agentforce Architecture, Agent Builder & Public Sector Agents 13.2 Topic Definitions, Instructions, Actions & CRM/Data Cloud Grounding 13.3 Einstein Trust Layer, Guardrails & Responsible AI Governance
14 Chapter 14: Discovery, Requirements & Solution Design
14.1 Documenting Business Needs, Agency Value & Vision for Desired Outcomes 14.2 Discovery & Design Approaches and Solution Documentation 14.3 Mapping Business Processes, Personas & Requirements
15 Chapter 15: Org Setup, Data Management & Integration Governance
15.1 Setting Up an Org for Agentforce Public Sector 15.2 Data Management Strategy, Data Quality & Integration Governance
15.2 Data Management Strategy, Data Quality & Integration Governance
Key Takeaways Explain This Topic AI
The Domain 3 objective asks for a data management strategy and process that ensures high data quality and seamless integration — quality and integration are one objective because in government they fail together.
Every integrated field needs a declared system of record; the most damaging integration defects come from two systems both believing they own a value.
Duplicate constituents are the signature public sector data-quality failure: they split a person's benefit, permit, and case history and can produce contradictory statutory determinations.
Use matching and duplicate rules on Person Accounts, validation at the point of entry in OmniScripts, and required-field discipline before considering downstream cleanup.
Choose the integration pattern from the requirement's latency and volume: Data Mappers and Integration Procedures for Salesforce-side orchestration, named credentials for authenticated callouts, platform events or change data capture for event propagation, and bulk or middleware patterns for high-volume batch.
Last updated: September 2026
15.2 Data Management Strategy, Data Quality & Integration Governance
Exam Focus: The official objective is "Given a set of business data requirements, design data management strategy and process to ensure high data quality and a seamless integration." Salesforce bundles quality and integration into one objective deliberately: in government they are the same failure. A duplicate constituent record created by an unmatched inbound integration is simultaneously a data-quality defect and an integration defect, and its consequence is a person receiving two determinations, or none.
Why Data Quality Is a Legal Matter Here
Commercial dirty data costs a wasted mailing. Government dirty data produces a wrong determination on a legal entitlement. Consider the consequences of a single duplicated constituent:
The household appears twice, so means-tested eligibility is computed against half the income and a benefit is overpaid — creating a recovery action against a vulnerable person.
An enforcement history splits, so a repeat violator presents as a first-time offender and receives the wrong penalty tier.
A records request or appeal returns an incomplete file, which is itself a compliance failure.
Reporting to a federal funder understates or double-counts served individuals, putting the appropriation at risk.
That is why the strategy has to be preventive. Cleanup projects treat symptoms; the objective asks for a process that keeps quality high.
Element 1: Declare the System of Record, Field by Field
The foundational artifact is a table naming, for every shared field, which system owns it and which merely displays it.
- Data element System of record Salesforce role Sync pattern
- Constituent identity and demographics Salesforce (Person Account) Master Outbound to downstream systems
Verified income for eligibility State wage verification service Read-only reference On-demand callout at determination
- Property parcel and zoning County GIS / assessor system Read-only reference Scheduled refresh
- Permit application status Salesforce Master Published outbound
Payment and receipt Treasury / financial system Reference, with a Salesforce transaction reference Event or batch reconciliation
Statutory determination and its rationale Salesforce (Business Rules Engine output) Master and evidence Retained per records schedule
Two rules follow, and both are testable:
A field has exactly one master. "Both systems can update it" is not a design; it is a defect scheduled for later.
Reference data is read-only in Salesforce. If the assessor system owns parcel data, users must not be able to edit it in Salesforce — otherwise the two diverge and nobody can say which is right.
Element 2: Migration Strategy for Legacy Government Data
Agencies migrate from mainframes, county systems, and spreadsheets, carrying decades of history under a records schedule that forbids simply discarding it.
Decision Guidance
What to migrate Active cases and the history required by the records schedule and by open appeals — not everything by default
What to archive Closed records beyond operational need, retained in an accessible archive rather than loaded into the org
Cleanse where At source or in staging, before load. Loading dirty data and cleaning it afterwards means cleaning it under production change control
Deduplicate when During migration, using the same matching rules that will run in production — so the rules are proven before go-live
Verify how Reconciliation counts and sampled record-level comparison, signed off by the business owner, not by the migration team alone
Rehearse At least one full-volume rehearsal in a sandbox with a timed rollback plan; for a big-bang cutover this is mandatory
Element 3: Prevent Duplicates at the Front Door
Public Sector Solutions constituent data lives on Person Accounts , and duplicate prevention has to be designed for them explicitly.
Matching rules define what "the same person" means for this agency. Name plus date of birth plus partial identifier is typical; name alone is not, because government populations contain many exact name collisions.
Duplicate rules decide what happens on a match: block, or alert and allow with a reason. In benefits intake, blocking is usually right; in emergency response intake, alert-and-allow is right, because a responder cannot be stopped mid-crisis.
Inbound integrations must run through the same matching logic. The most common source of duplicates is not a person typing; it is an interface inserting records that never checked for an existing match. Give integrations an idempotent upsert keyed on a stable external identifier.
External identifiers matter more than they look. A unique external ID field on the constituent record is what makes upsert safe and re-runnable, and re-runnability is what saves an integration outage from becoming a duplication event.
Validate at the point of entry
Quality is cheapest at the moment of capture:
OmniScript validation on the constituent-facing form — format, ranges, and cross-field consistency — so the person fixes it while they are still there;
required fields and validation rules on the object for staff-entered data;
picklists over free text for anything that will be reported on or used in a rule, because a rule cannot reason over free text;
Document Checklist Items to make completeness explicit rather than discovered late.
Element 4: Choose and Govern the Integration Pattern
Select from the requirement's latency and volume, not from familiarity.
Requirement signal Pattern
Look up an external value during a guided form or determination Integration Procedure with an HTTP action over a named credential
- Shape data between Salesforce and an external payload Data Mappers (Extract, Turbo Extract, Transform, Load)
- Notify other systems when something happens Platform events or change data capture
- Nightly reference refresh (parcels, provider registries) Scheduled batch integration
- High-volume historical or bulk load Bulk API, staged and reconciled
Several systems, complex routing and transformation Middleware such as MuleSoft, so orchestration is not scattered across orgs
Governance rules that keep integrations from degrading data quality:
Authenticate through named credentials , never through credentials embedded in code or custom settings.
Make every inbound interface idempotent — a replayed message must not create a second record.
Handle errors visibly. A silently failing nightly interface produces a slow, invisible divergence that is discovered by an auditor. Integration Procedure error handling should record the failure somewhere a human is accountable for.
Log what was received. For determinations that can be appealed, the agency must be able to show the value it relied on at the time , not the value the external system holds today.
Respect the Government Cloud boundary. An integration leaving a Government Cloud org must be assessed against the data classification, not assumed to inherit the org's authorization.
- 💡 Real-World AP-222 Exam Scenarios & Case Analysis
- Scenario 1: Duplicate Households in a Benefits Program
A state benefits agency finds that 9% of its constituent records are duplicates. Investigation shows most were created by a nightly interface from a legacy county intake system that inserts a record for every household it sends. Two households have received duplicate benefits, triggering recovery actions.
What is the strategy?
Treat this as an integration defect first : convert the nightly insert to an idempotent upsert keyed on a stable external identifier so a re-sent household updates rather than duplicates.
Define matching rules for Person Accounts that reflect how the agency identifies people — not name alone — and enforce duplicate rules in the intake path.
Run a deduplication remediation using those same rules, with merge decisions reviewed where a benefit determination is affected, because merging records that carry legal determinations is not a purely technical operation.
Declare the system of record for household composition so the county system and Salesforce stop competing for it.
Scenario 2: Eligibility Against External Wage Data
An eligibility determination must use verified wages from a state wage verification service. Wages change; determinations are appealable for 60 days.
How should this be designed?
The wage service is the system of record ; wages are read-only in Salesforce, so a caseworker cannot edit them into agreement with a claim.
Retrieve at determination time with an Integration Procedure HTTP action over a named credential — a stale nightly copy would produce determinations against data the agency cannot defend.
Persist the retrieved value and its retrieval timestamp with the determination. When the appeal arrives 45 days later, the agency must show the figure it actually relied on, not today's figure.
Run the determination in Business Rules Engine so the rule version and the decision output are inspectable alongside the input.
Scenario 3: Mainframe Retirement With Thirty Years of Records
A licensing agency is retiring a mainframe holding 30 years of licence history. The records schedule requires retention of some categories for the life of the licensee. The project team proposes loading everything into Salesforce.
What should the architect advise?
Migrate active licences and the history needed for operations, open appeals, and the records schedule ; archive the remainder in an accessible archive rather than inflating the org with records nobody queries.
Cleanse in staging , not after load, so corrections happen outside production change control.
Deduplicate during migration with the production matching rules , which proves those rules on real data before go-live.
Reconcile with counts and sampled record-level comparison, signed off by the business owner, and rehearse the load at full volume with a timed rollback before cutover.