Developers PDI Syllabus Exam Questions Answers

Page: 13 / 12

Question 52

Universal Containers wants to ensure that all new leads created in the system have a valid email address. They have already created a validation rule to enforce this requirement, but want to add an additional

layer of validation using automation.

What would be the best solution for this requirement?

Options:

Use an Approval Process to enforce the completion of a valid email address using an outbound message action,

Submit a REST API Callout with a JSON payload and validate the fields on a third party system

Use a custom Lightning Web component to make a callout to validate the fields on a third party system.

Use a before-save Apex trigger on the Lead object to validate the email address and display an error message if it is invalid

Answer:

Explanation:

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.

[:, 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., Reference: Approval Processes, 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., Reference: Apex Callouts and Triggers, 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., Reference:, 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., ]

Page: 13 / 12