A company has 20,000 rows in the Account object and 2 million rows in the Sales_Data_c object that is related to Account. All of the records in the Sales_Data_c object have a field that contains the string 'Le.' Which statement will throw a "Too many query rows" exception? Choose 2 answers

• A.List< Account> result = [SELECT Id, (SELECT Id FROM Sales_Data_r) FROM Account]
• B.List< AggregateResult> result = [SELECT count(Id) total FROM Sales_Data_c];
• C.List< List< sObject>> result= [FIND 'Le' IN ALL FIELDS RETURNING Sales_Data_c(Id)];
• D.List< sObject> result = Database.query('SELECT Id FROM Sales_Data_c LIMIT 50000');

Comment: *

Name: *

Email: *

Verification: *

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 2 answers

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

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.Remove the last line updating accountList as it is not needed.
• C.Use a Map to cache the results of the Region__c query by Id.
• D.Move the Region__c query to outside the loop.

Comment: *

Name: *

Email: *

Verification: *

An Apex Trigger creates a Contract record every time an Opportunity record is marked as Closed and Won.
This trigger is working great, except (due to a recent acquisition) historical Opportunity records need to be loaded into the Salesforce instance. When a test batch of records are loaded, the Apex Trigger creates Contract records. A developer is tasked with preventing Contract records from being created when mass loading the Opportunities, but the daily users still need to have the Contract records created. What is the most extendable way to update the Apex Trigger to accomplish this?

• A.add the Profile Id of the user who does the data loading to the Trigger so the Trigger won't fire for this user.
• B.Use a List Custom Setting to disable the Trigger for the user who does the data loading.
• C.Add a Validation Rule to the Contract to prevent Contract creation by the user who does the data loading.
• D.Use a Hierarchy Custom Setting to disable the Trigger for the user who does the data loading.

Comment: *

Name: *

Email: *

Verification: *

A developer is building a Visualforce page that interacts with external services. Which interface should the developer implement to test this functionality? Choose 2 answers

• A.HTTPCalloutMock
• B.HTTPResponseMock
• C.StaticResourceCalloutMock
• D.HTTPRequestMock

Comment: *

Name: *

Email: *

Verification: *