The SOAP API...

• A.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
• B.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
• C.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
• D.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

Comment: *

Name: *

Email: *

Verification: *

Which object can a developer use to programmatically determine who is following a specific User record in Chatter?

• A.EntitySubscription
• B.FollowHistory
• C.FollowSubscription
• D.Entityfiistory

Comment: *

Name: *

Email: *

Verification: *

A developer writes the following Apex trigger so that when a Case is closed, a single Survey record is created for that Case. The issue is that multiple Survey_c records are being created per Case.

What could be the cause of this issue?

• A.A workflow rule is firing with a Field Update action
• B.A workflow rule is firing with a Create Task action
• C.A user is editing the record multiple times
• D.A user is creating the record as Closed

Comment: *

Name: *

Email: *

Verification: *

An Apex trigger creates a Contract record every time an Opportunity record is marked as Closed end 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 a Validation Rule to the Contract to prevent Contract creation by the user who loads the data.
• B.Use a Hierarchy Custom Setting to skip executing the logic inside the trigger for the user who loads the data.
• C.Add the Profile ID of the user who loads the data to the trigger so the trigger will not fire for this user.
• D.Use a List Custom Setting to disable the trigger for the user who loads the data.

Comment: *

Name: *

Email: *

Verification: *

A company recently deployed a Visualforce page with a custom controller that has a data grid of information about Opportunities in the org. Users report that they receive a "Maximum view state size limit" error message under certain conditions.
According to Visualforce best practice, which three actions should the developer take to reduce the view state? (Choose three.)

• A.Use the transient keyword in the Apex controller for variables that do not maintain state
• B.Refine any SOQL queries to return only data relevant to the page
• C.Use filters and pagination to reduce the amount of data
• D.Use the final keyword in the controller for variables that will not change
• E.Use the private keyword in the controller for variables

Comment: *

Name: *

Email: *

Verification: *