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 is 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 a Validation Rule to the Contract to prevent Contract creation by the user who does the data loading.
• B.Use a List Custom Setting to disable the Trigger for the user who does the data loading.
• C.Add the Profile Id of the user who does the data loading to the Trigger so the Trigger won't fire for this user.
• D.Use a Hierarchy Custom Setting to disable the Trigger for the user who does the data loading.

Comment: *

Name: *

Email: *

Verification: *

A company's support process dictates that any time a Case is closed with a Status of 'Could not fix,' an Engineering Review custom object record should be created and populated with information from the Case, the Contact, and any of the Products associated with the Case. What is the correct way to automate this using an Apex trigger?

• A.An after update trigger that creates the Engineering Review record and inserts it
• B.A before update trigger that creates the Engineering Review record and inserts it
• C.A before update trigger that creates the Engineering Review record and inserts it
• D.An after upsert trigger that creates the Engineering Review record and inserts it

Comment: *

Name: *

Email: *

Verification: *

The Bulk API...

• A.Provides a powerful, convenient, and simple REST-based web services interface for interacting with Salesforce. Its advantages include ease of integration and development, and it's an excellent choice of technology for use with mobile applications and web projects
• B.Is used to to retrieve, deploy, create, update, or delete customizations for your org. The most common use is to migrate changes from a sandbox or testing org to your production environment
• C.Is used to to create, retrieve, update or delete records, such as accounts, leads, and custom objects, and allows you to allows you to maintain passwords, perform searches, and much more
• D.Is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to query, queryAll, insert, update, upsert, or delete many records asynchronously by submitting batches

Comment: *

Name: *

Email: *

Verification: *

Salesforce users consistently receive a "Maximum trigger depth exceeded" error when saving m Account.
How can a developer fix this error?

• A.Split the trigger logic into two separate triggers.
• B.Convert trigger to use the Cfuture annotation, and chain any subsequent trigger invocations to the Account object.
• C.Modify the trigger to use the isMultiThread=true annotation.
• D.Use a helper class to set a Boolean to TRUE the first time a trigger is fired, and then; modify the trigger to only fire when modify the trigger to only fire when the Boolean is FALSE.

Comment: *

Name: *

Email: *

Verification: *

Which statement is true about Apex web service methods? Choose 3 answers

• A.Web service methods can be exposed having a custom Apex class as parameter datatype.
• B.Web service methods cannot be deprecated in managed package code.
• C.Web service methods can only be added to Apex triggers that are declared global.
• D.Web service methods can be overloaded with methods of the same name in the same class.
• E.Web service methods can only be added to Apex classes that are declared global.

Comment: *

Name: *

Email: *

Verification: *