Lesson 15 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 6 · Data and Analytics Management · 13% of exam

6.1 Data quality, validation, duplicates, enrichment, and archiving

4 min read Updated Nov 17, 2026

Exam objective

Explain tools and best practices for assessing, improving, and enriching data quality, including data types, validation, duplicate management, enrichment, and archiving.

Data quality is fitness for a business purpose, not simply the absence of blank fields. Define which fields are authoritative, how values are collected, acceptable formats, and who owns exceptions. Choose field types that match the meaning: currency for monetary values, dates for calendar dates, picklists for controlled categories, and lookup fields for references to other records. A poorly chosen type can make validation, reporting, calculations, and integrations harder. Check whether a field's values must remain stable for historical reporting or downstream systems.

Validation rules enforce record-level conditions at save time. Use them for requirements that can be expressed in a formula, such as requiring a reason when a status changes to a specific value. Write an error message that says what the user must do. Consider which profiles, record types, and integration users are affected; a rule that is appropriate for the UI can block a valid integration update if its logic ignores channel or status context. Test both valid and invalid cases, including imports and automated updates.

Duplicate management uses matching rules to identify likely duplicates and duplicate rules to alert users or block creation depending on configuration. Matching criteria should reflect identity risk and business policy. A loose rule can create false positives, while an overly strict rule misses duplicates. Decide how users should compare records and whether merge operations preserve the required relationships and field values. For integrations, use stable external IDs and upsert patterns to prevent repeated inserts. Duplicate rules are not a replacement for data stewardship or source-system governance.

Data enrichment can append verified information from internal or external sources. Before enrichment, confirm permitted use, consent, freshness, source reliability, and the matching key. Track source and updated date where the business needs to explain a value. Avoid overwriting user-entered data without a precedence policy. If records are enriched in batch, monitor exceptions and changes to validation behavior. Enrichment should improve a defined business process, not create more fields with unclear ownership.

Archiving reduces the amount of active data and can support retention requirements or performance goals. Decide which records are eligible, how long they must be retained, whether they must remain searchable, and what related records or reports depend on them. Salesforce Big Objects and external storage patterns support specific high-volume or retention needs, but they have distinct query, indexing, transaction, and user-interface characteristics. A simple delete is not archiving if legal or operational retention is required. Confirm restore and audit needs before moving data. Assessment methods include duplicate reports, completeness reports, field history where configured, exception dashboards, and periodic sampling. Identify a quality metric and owner, such as percentage of accounts with verified industry or proportion of contacts with valid consent status. Fix upstream entry and integration causes before running repeated cleanup jobs. For a one-time cleanup, backup data, define matching and merge rules, rehearse on a sandbox, and review samples with business owners before applying changes at scale.

Exam focus: select validation for enforceable value conditions, matching and duplicate rules for likely duplicate detection, and external IDs for reliable upserts. Distinguish enrichment from data cleansing and archiving. Consider integration effects and preserve a restore path for bulk updates. A requirement to improve data should include ownership and measurement, not just a one-off import.

A validation rule or duplicate block can stop legitimate automation and integrations. Test the full set of save paths and provide a controlled exception mechanism only when policy allows it.

Establish a correction loop after measurement. A dashboard can show that addresses are incomplete, but the organization still needs a responsible queue, source, and process for fixing them. Separate systemic cleanup from manual exceptions and measure both. Maintain a change log for large updates and reconcile record counts. If values are legally or commercially significant, preserve provenance and avoid overwriting a verified source without approval. Review whether archives remain accessible to users who need them and how retained data will be securely deleted when the retention period ends.

Practical scenario

A contact import contains duplicate people and inconsistent country codes. First normalize the source values and agree on a canonical country list; use matching rules to flag probable duplicates and an external ID to upsert records from the source system. Rehearse merges and relationship preservation in a sandbox. Add validation only after the data and integration paths are ready, then monitor exceptions with a quality report.

Extra concept

Data lifecycle is an extra design dimension: creation, update, enrichment, retention, archive, and deletion all need an owner and policy. An operationally clean CRM can still violate a retention requirement if archived copies are kept indefinitely without a documented basis.

Key takeaways

  • Use validation for save-time rules and duplicate management for likely matches.
  • Use stable external IDs to support reliable integrations and upserts.
  • Define ownership, retention, and restore expectations before cleanup or archiving.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.data_quality.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.duplicate_rules.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_import_wizard.htm&type=5

Check your knowledge

Answer exam-style Data and Analytics Management questions with answers and explanations.

Practice Data and Analytics Management
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator II simulator: same number of questions, same time limit.

Get Complete Access