A developer created a Lightning web component that uses a lightning-record-edit-form to collect information about Leads. Users complain that they only see one error message at a time about their input when trying to save a Lead record. Which best practice should the developer use to perform the validations on more than one field, thus allowing more than one error message to be displayed simultaneously?

• A. Custom validation rules
• B. Client-side validation
• C. Apex REST
• D. Next Best Action

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Universal Containers uses a custom Lightning page to provide a mechanism to perform a step-by-step wizard search for Accounts. One of the steps in the wizard is to allow the user to input text into a text field, ERP_Number__c, that is then used in a query to find matching Accounts.
Java
erpNumber = erpNumber + '%';
List<Account> accounts = [SELECT Id, Name FROM Account WHERE ERP_Number__c LIKE :
erpNumber];
A developer receives the exception 'SOQL query not selective enough'. Which step should be taken to resolve the issue?

• A. Change the query to use a SOSL statement instead of SOQL.
• B. Mark the ERP_Number__c field as required.
• C. Mark the ERP_Number__c field as an external ID.
• D. Move the SOQL query to within an asynchronous process.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Universal Containers needs to integrate with their own, existing, internal custom web application. The web application accepts JSON payloads, resizes product images, and sends the resized images back to Salesforce.
What should the developer use to implement this integration?

• A. A platform event that makes a callout to the web application1516
• B. An Apex trigger that calls an @future method that allows callouts910
• C. A flow with an outbound message that contains a session ID1314
• D. A flow that calls an @future method that allows callouts1112

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

The Account object has a field, Audit_Code__c, that is used to specify what type of auditing the Account needs and a Lookup to User, Auditor__c, that is the assigned auditor. When an Account is initially created, the user specifies the Audit_Code__c. Each User in the org has a unique text field, Audit_Code__c, that is used to automatically assign the correct user to the Account's Auditor__c field.
Trigger:
Java
trigger AccountTrigger on Account (before insert) {
AuditAssigner.setAuditor(Trigger.new);
}
Apex Class:
Java
public class AuditAssigner {
public static void setAuditor(List<Account> accounts) {
for (User u : [SELECT Id, Audit_Code__c FROM User]) {
for (Account a : accounts) {
if (u.Audit_Code__c == a.Audit_Code__c) {
a.Auditor__c = u.Id;
}
}
}
}
}
What should be changed to most optimize the code's efficiency?

• A. Build a Map<String, List<Account>> of audit code to accounts.
• B. Add a WHERE clause to the SOQL query to filter on audit codes.
• C. Build a Map<Id, List<String>> of Account Id to audit codes.
• D. Add an initial SOQL query to get all distinct audit codes.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

How should a developer verify that a specific Account record is being tested in a test class for a Visualforce controller?

• A. Insert the Account into Salesforce, then use System.setParentRecordId().get() to set the Account ID.
• B. Insert the Account in the test class, instantiate the page reference, then use ApexPages.currentPage().
  getParameters().put() to set the Account ID.
• C. Instantiate the page reference, insert the Account, then use System.setParentRecordId().get() to set the Account ID.
• D. Instantiate the page reference, insert the Account, then use seeAllData=true to view the Account.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).