Use a trigger on the opportunity object

Use a trigger on the account object

Use roll-up summary fields and a formula field

Use a roll-up summary field with the average function

Use the isDeletable() method of the DescribeSObjectResult Class

Use the canDelete() method of the DescribeSObjectResult Class

Use the Deletable() method of the SObjectResult Class

Use the canDelete() method of the SObjectResult Class

The field values in Estimated_value__c from CampaignMember object are converted into the currency of the current user, and the Total_estimated_value__c is shown using the currency of the current user on the Campaign.

The field values in Estimated_value__c from CampaignMember object are summed up, and the Total_estimated_value__c field is shown as a Number field on the Campaign.

The field values in Estimated_value__c are converted into the currency of the majority of the CampaignMember records, and the Total_estimated_value__c is shown using that currency.

The field values in Estimated_value__c from CampaignMember object are converted into the currency of the Campaign, and the Total_estimated_value__c is shown using the currency of the Campaign.

‘Salesforce’

3.14159

TRUE

"Salesforce"

No update DML over list of Contacts

SOQL query is located inside the for loop code.

Condition is invalid and will always be null.

Variable 'con' is not declared.

Use Database.EachResult Class

Use Database.SuccessResult Class

Use Database.SaveResult Class

Use Database.ErrorResult Class

Currency

Text

ID

Enum

Blob

System Validation Rules, Workflow Rules, All Validation Rules, Before Triggers, After Triggers, Assignment Rules, Commit

System Validation Rules, Before Triggers, All Validation Rules, Duplicate Rules, After Triggers, Assignment Rules, Workflow Rules, Commit

System Validation Rules, Before Triggers, All Validation Rules, Workflow Rules, After Triggers, Assignment Rules, Commit

System Validation Rules, User Defined Validation Rules, Before Triggers, Workflow Rules, After Triggers, Workflow Rules, Assignment Rules, Commit

List<Account> accList = new Account[]{};

List<Account> new = ‘accList’;

Account[] accList = new Account[]{};

List<Account> accList = new List<Account>();

continue;

end;

break;

skip;

A savepoint will be generated

There is no impact on DML statements

DML statements will be saved up to the exception point

DML statements will be rolled back

SOQL for loop can be used to avoid the limit on heap size

SOQL for loop can only be used to execute code once per sObject record

Using a SOQL for loop, it is possible to perform a DML operation on a list of sObjects at a time

A SOQL for loop can process records in batches of 500

String a = new String(‘sampleString’);

Map<Id, Account> = [SELECT Id, Name FROM Account];

Account acc = new Account();

List<Contact> conList = new [SELECT Id FROM Contact];

Use the [with sharing] keyword in Apex classes

Use the [without sharing] keyword in Apex classes

Use the [shareable] keyword in Apex classes

Use the [non shareable] keyword in Apex classes

Semicolon and comma characters can be used to add filters for the multi-select picklist field to the SOQL query

Picklist values can be specified with AND / OR logic

Picklist values can only be specified with AND logic

Picklist values can only be specified with OR logic

Custom setting data can be accessed by formula fields, validation rules, Apex and Visualforce pages

Custom setting data cannot be queried using SOQL

Custom setting data needs to be queried once using SOQL and then it is stored in the cache

There are two types of custom setting data, hierarchy and list

Developers cannot change the data type of a custom field if it is referenced in Apex.

Developers cannot change the data type of a custom field that is referenced by a Visualforce page.

The file field type in Salesforce Knowledge can be changed as long as it is not referenced in a Apex Class.

The option to change the data type of a custom field is not available for all data types.

Custom Buttons can only be used with custom objects

Custom Buttons can only be added to custom page layouts

Custom Buttons will work with standard or custom objects

Custom Buttons can be added to standard page layouts

By accessing the content from Chatter files

By uploading the content as a Static Resource

By uploading the content to the documents tab

By accessing the content from a third-party CDN

Use ApexPages.currentPage().getAnchor() to get the parameter value then make a query to the record using the ID in the controller's constructor.

Use ApexPages.currentPage().getHeaders() to get the parameter value then make a query to the record using the ID in the controller's constructor.

Use ApexPages.currentPage().getParameters() to get the parameter value then make a query to the record using the ID in the controller's constructor.

Use ApexPages.currentPage().getContent() to get the parameter value then make a query to the record using the ID in the controller's constructor.

<apex:outputTable>

<apex:pageBlockTable>

<apex:dataTable>

<apex:table>

There is no limit to the size of the view state

The view state is used to store the layout of a Visualforce page

The view state is used to store state across multiple pages, such as in a wizard

The view state is used to store state across multiple user sessions

<apex:output>

<apex:getsite>

<apex:include>

<apex:iframe>

Delete

View

Edit

Create

<script>

<apex:includeScript>

<javascript>

<apex:js>

It uses ODS as its data format

It has an event-driven architecture

It automatically upgrades all pre-existing Visualforce pages and components

It is device-aware and supports cross-browser compatibility

A Developer Edition

A Partial Copy Sandbox

A Developer Pro Sandbox

A Partner Developer Edition

Developer Edition to Developer Edition

Developer Edition to Production.

Developer Sandbox to Production.

Sandbox to Sandbox.

Testing cannot be completed in a developer edition

APEX Code must have sufficient code coverage

Development must be done in a developer edition or sandbox

It is a best practice to test in a dedicated testing environment with large sets of data

Annotate the test class or method with [seeAllData=false]

Annotate the test class or method with [seeAllData=true]

Annotate the test method with [withSharing=false]

Annotate the test method with [withSharing=true]

Creating common test utility classes

De-annotating @isTest on methods

Using one common test class

Making the test methods Public

Test.isTest() and Test.isnotTest()

Test.runAs() and Test.getLimits()

Test.startTest() and Test.stopTest()

Test.setFixedSearchResults()

Custom Setting data

Profiles

Custom Objects

Users

Record Types

Use SeeAllData=true.

Use System.debug() method to verify test results.

Use @future annotation.

Use System.assert() methods to verify test results.

Individual test methods can also be specified.

Running selected or specified tests is only available in Metadata API.

If the code coverage of an Apex component in the deployment is less than 75%, the deployment fails.

Code coverage is computed for each class and trigger individually and is different than the overall coverage percentage.

Defining a test suite

Defining a test set

Defining a master test class

Reducing the number of test classes

To exchange apps with other developers

To exchange ideas and tips with other developers

To extend standard Salesforce functionality

To add industry specific functionality to Salesforce

Different page layouts can be assigned for each record type

Different picklist values can be defined for each record type

Different fields can be defined for each record type

Different users can be assigned to each record type

Salesforce delivers polyglot persistence transparently

It is not possible to index application data as each tenant stores different types of data in the same application table

Queries need to be selective in terms of the number of records returned

The custom domain feature ensures that different customers do not access each other's data

Person Accounts have the same fields as a business account

Person Accounts do not have an account hierarchy

Once Person Accounts are enabled they cannot be disabled

If Person Accounts are enabled, when creating an account, the type of account to create needs to be selected

Using the Related Account field

Using the Parent Account field

Using the View Hierarchy link

Using the Generate Relationship function

Number x;

Currency abc;

Boolean y;

Map<ID, String> sampleMap;

String a,b,c;

SELECT Id, LastName FROM Contact WHERE LastName LIKE ‘Ab_’

SELECT Id, LastName FROM Contact WHERE LastName := ‘Ab%’

SELECT Id, LastName FROM Contact WHERE LastName IN (‘Ab’)

SELECT Id, LastName FROM Contact WHERE LastName LIKE ‘Ab%’

Integer totalCost;

Decimal totalCost;

Numeric totalCost;

Long totalCost;

Picklist

Checkbox

Text

Number

Use the SOQL.execute(string) with a query specified in the string

Use the Database.search(string) with a query specified in the string

Use the Database.execute(string) with a query specified in the string

Use the Database.query(string) with a query specified in the string

describeObjects()

getGlobalSObjects()

getGlobalDescribe()

describeSObjects()

ORDER by

OFFSET n

RETURNING

LIMIT n

Picklists

Required fields

Escalation rules

Validation rules

insert accountList;

System.debug(‘The following account has been updated’ + ‘acc.Id ‘);

if(acc.NumberOfEmployees > 5000){

Opportunity getOpp = [SELECT Id, AccountId FROM Opportunity WHERE AccountId =: acc.Id];

A limit exception will be caught and one account will be inserted

150 accounts will be inserted

No accounts will be inserted

201 accounts will be inserted

Use a controller extension

Use the Opportunity StandardController

Use a custom controller and replicate the opportunity detail page

Use the StandardListController

No update DML over list of Contacts

SOQL query is located inside the for loop code.

Condition is invalid and will always be null.

Variable 'con' is not declared.

<apex:page controller="Opportunity" recordListVar="opportunities">

<apex:page controller="Opportunity" recordSetVar="opportunities">

<apex:page standardController="Opportunity" recordSetVar="opportunities">

<apex:page standardController="Opportunity" getAllRecordsVar="opportunities">

A map of sObjects that match the search term

A list of Contacts that match the search term

A list of lists of sObjects and their records that match the search term

A map of Accounts or Contacts that match the search term

An exception will be thrown.

It will save all changes made from the Apex controller class.

It will save all changes made from the Apex class.

It will rollback all changes made up to the error.

Using .addError method on errors that may occur in DML on Apex Triggers.

Sending an email that may add to the catch-block of a try-catch construct

Adding a @future method to create a record on a custom object that could catch the error details.

Using ApexPages.message class to create an error message for display on a Visualforce page.

The custom object can be on the master or detail side of the relationship

The standard object can be on the master or detail side of the relationship

The standard object is always the master

The object on the detail side will inherit the security and sharing settings of the master object

Hierarchy

Picklist

Lookup

Master Detail