* B: Salesforce requires that all Apex code have at least 75% test coverage in production before deployment. This ensures that the system remains reliable.
* C: All triggers must have some test coverage as part of the overall 75% requirement for Apex code.
Why not other options?
* A: Object visibility settings are not a deployment requirement.
* D: Visual Flows do not require test coverage for deployment to production.
References:
* Apex Test Coverage Requirements

* Why Data Export Scheduled Job?
* Salesforce provides an out-of-the-boxData Exportfeature that allows organizations to back up their data, including attachments.
* This feature can be scheduled to run automatically on a monthly basis, fulfilling the requirement.
* Why Not Other Options?
* A. Schedule a Report: Does not export attachments and is limited to reportable data.
* B. Data Loader Command Line: Requires manual setup and scripting, which is unnecessary for this requirement.
* D. Create a Schedulable Apex class: Not suitable, as the Data Export tool is more efficient for full data and attachment backup.
References:Data Export Documentation:https://help.salesforce.com/s/articleView?id=sf.data_export_overview.htm

To add an additional layer of validation for email addresses on Lead records by using automation and possibly an external validation service, the best solution is to use a custom Lightning Web Component (LWC).
Option C: Use a custom Lightning Web Component to make a callout to validate the fields on a third-party system Real-Time Validation: An LWC can perform client-side validation and make callouts to external systems to validate the email address as the user inputs data.
User Experience: Provides immediate feedback to the user, improving data quality at the point of entry.
Limitations: This solution works when data is entered through the UI using the LWC component.
Reference:
Lightning Web Components
Making Callouts from Lightning Components
Why Other Options are Less Optimal or Incorrect:
Option A: Use an Approval Process to enforce the completion of a valid email address using an outbound message action Not Suitable: Approval Processes are not intended for data validation.
Outbound Messages: Used to send data to external systems but do not enforce validation during record creation.
Option B: Submit a REST API Callout with a JSON payload and validate the fields on a third-party system Vague Implementation: Does not specify where or how the callout is made.
Technical Constraints: Making synchronous callouts during record save (e.g., from a trigger) is not permitted.
Option D: Use a before-save Apex trigger on the Lead object to validate the email address and display an error message if it is invalid Callout Limitations: Apex triggers cannot make callouts in a before-save context.
Asynchronous Callouts: Using asynchronous methods (e.g., @future) cannot prevent the record from being saved.
Apex Triggers and Callouts
Future Methods
Conclusion:
Using a custom Lightning Web Component is the best solution to add an additional layer of validation during data entry.
It allows for real-time validation via callouts to a third-party system.
While it doesn't cover records created via other means (API, data import), the existing validation rule would still enforce that an email address is provided.