A company notices that their unit tests in a test class with many methods to create many records for prerequisite reference data are slow.
What can a developer to do address the issue?

• A.Move the prerequisite reference data setup to a TestDataFactory and call that from each test method.
• B.Move the prerequisite reference data setup to a @testSetup method in the test class.
• C.Move the prerequisite reference data setup to a static method in the test class and call that from each test method.
• D.Move the prerequisite reference data setup to the constructor for the test class.

Comment: *

Name: *

Email: *

Verification: *

UC Loans is a small company with a part time Salesforce administrator. UC Loans wants to create a Loan__c record whenever an Opportunity is won.
What is the optimal solution for UC Loans to accomplish this?

• A.Quick Action
• B.Workflow Rule
• C.Process Builder
• D.Apex Trigger

Comment: *

Name: *

Email: *

Verification: *

Recently a Salesforce org's integration failed because it exceeded the number of allowed API calls in a 24-hour period. The integration handles a near real-time, complex insertion of data into Salesforce.
The flow of data is as follows:
* The integration looks up Contact records with a given email address and, if found, the integration adds a Task to the first matching Contact it finds.
* If a match is not found, the integration looks up Lead records with a given email address and, if found, the integration adds a Task to the first matching Lead it finds.
* If a match is not found, the integration will create a Lead and a Task for that newly created Lead.
What is one way in which the integration can stay near real-time, but not exceed the number of allowed API calls in a 24-hour period?

• A.Create several Apex InboundEmailHandlers to accept calls from the third-party system, thus bypassing the APT limits.
• B.Use the REST API as well as the SOAP API to effectively double the API calls allowed in a 24-hour period.
• C.Write a custom Apex web service that, given an email address, does all of the logic the integration code was doing.
• D.Create an Inbound Message that, using Flow, can do all of the logic the integration code was doing.

Comment: *

Name: *

Email: *

Verification: *

An org has a Process Builder process on Opportunity that sets a custom field,CommissionBaseAmount__c, when an Opportunity is edited and the Opportunity's Amount changes.
A developer recently deployed an Opportunity before update trigger that uses the CommissionBaseAmount__c and complex logic to calculate a value for a custom field CommissionAmount_c, when an Opportunity stage changes to Closed/Won.
Users report that when they change the Opportunity to Closed/Won and also change the Amount during the same save, the C:rr.i;5icnA.T.cur.t c is incorrect.
Which two actions should the developer take to correct this problem? Choose 2 answers

• A.Call the process from the trigger.
• B.Use a static Boolean variable in the trigger.
• C.Uncheck the recursion checkbox on the process.
• D.Call the trigger from the process.

Comment: *

Name: *

Email: *

Verification: *

trigger AssignOwnerByRegion on Account ( before insert, before update )
{
List<Account> accountList = new List<Account>();
for( Account anAccount : trigger.new )
{
Region__c theRegion = [
SELECT Id, Name, Region Manager__c
FROM Region__c
WHERE Name = :anAccount.Region_Name__c
];
anAccount.OwnerId = theRegion.Region_Manager__c;
accountList.add( anAccount );
}
update accountList;
}
Consider the above trigger intended to assign the Account to the manager of the Account's region.
Which two changes should a developer make in this trigger to adhere to best practices? (Choose two.)

• A.Use a Map accountMap instead of List accountList.
• B.Move the Region__c query to outside the loop.
• C.Use a Map to cache the results of the Region__c query by Id.
• D.Remove the last line updating accountList as it is not needed.

Comment: *

Name: *

Email: *

Verification: *