Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.

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.

Identify a location to store archived data and use scheduled batch jobs to migrate and purge the aged data on a nightly basis,

Explanation:

Scheduled batch jobs (A) are the proper archival method because they can systematically identify and move outdated records to a separate storage location (like BigObjects) on a nightly basis. This maintains data accessibility for reporting while improving system performance. Workflows (B) can't handle large data volumes, manual exports (C) aren't automated, and sandboxes (D) aren't designed for archival purposes.

Explanation:

To manage storage and still meet the CEO’s reporting needs, aggregate order revenue per customer annually into a custom object. This retains key business insights like year-over-year revenue without storing every detailed order or line item. Then, safely delete the detailed records to free up storage in Salesforce.

Lighting platform plus

Explanation:

The finance team requires access to a custom object (projects__c) for reporting and adjusting data, but no access to sales objects. The Lightning Platform Plus license provides access to custom objects and apps but limits access to standard Sales or Service Cloud objects. Sales Cloud and Service Cloud licenses grant broader CRM access unnecessary for finance users. The Lightning Platform Starter license is more limited and may not support the number of custom objects or API calls needed. Lightning Platform Plus offers an optimal balance of functionality and cost for users needing focused access to custom business applications.

Use the Consent Management Feature to validate consent provide under the person Account and Contact that is provided by the customer.

Explanation:

Option C (✔️ Best Practice) – Salesforce’s native Consent Management feature (part of Data Protection & Privacy) is designed for GDPR compliance and:
1. Centralizes consent tracking for Person Accounts and Contacts (using the Individual object).
2. Automates validation (e.g., checks ConsentDate and ExpirationDate before emails/calls).
3. Integrates with Marketing Cloud and Service Cloud for enforcement.

Why Not the Others?

Option A (❌ Manual & Risky) – Custom fields work but lack automation (e.g., no expiration checks) and require custom code for validation.
Option B (❌ Redundant) – A custom object duplicates the Individual object’s functionality and adds maintenance overhead.
Option D (❌ Non-Compliant) – Deleting data violates GDPR’s "right to access" (records must be retained for audits).