Universal Containers has defined a new Data Quality Plan for their Salesforce data and wants to know how they can enforce it throughout the organization. Which two approaches should an architect recommend to enforce this new plan? Choose 2 answers
A.
Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.
B.
Use Workflow, Validation Rules, and Force.com code (Apex) to enforce critical business processes.
C.
Schedule reports that will automatically catch duplicates and merge or delete the records every week.
D.
Store all data in an external system and set up an integration to Salesforce for view - only access.
A.
Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.
B.
Use Workflow, Validation Rules, and Force.com code (Apex) to enforce critical business processes.
A comprehensive data quality strategy requires both proactive enforcement and ongoing monitoring. Validation rules, workflows, and Apex (B) provide real-time enforcement of data standards at point of entry, preventing bad data from being saved. Weekly dashboards (A) create management visibility and accountability for data quality. Option C is reactive rather than preventive and risks improper automated merges. Option D is too extreme as it prevents data modification in Salesforce. The combination of validation rules and dashboards creates a complete solution: validation rules enforce minimum standards for data completeness and accuracy, while dashboards highlight exceptions and trends for continuous improvement. This approach scales with the organization and can be progressively enhanced as data quality initiatives mature. The technical enforcement ensures immediate compliance with critical rules, while the managerial oversight addresses cultural adoption and edge cases. Together they form a sustainable framework for maintaining high-quality data without relying entirely on manual processes or after-the-fact cleanup operations.