Developer I Pack 02

before insert

before update

after insert

after update

Reference a test utility class in each test class.

Use the SeeAllData=true annotation in each test class.

Create a Test Setup method for each test class.

Define variables for test records in each test class.

Call "acct.getSObjectType()".

Call "Account.getSObjectType()".

Call "Account.SObjectType".

Call "acct.SObjectType".

throw (MissingFieldValueException, 'Problem occurred');

throw new MissingFieldValueException('Problem occurred');

throw new MissingFieldValueException();

throw Exception(new MissingFieldValueException());

4

2

8

10

Parallel blocks can reuse the same variable name

A sub-block can reuse a parent block's variable name if it is static.

A variable can be declared at any point in a block.

A variable must be declared before it can be referenced in a block.

A sub-block can reuse a parent block's variable name if it is not static.

Text

Blob

Object

String

Creating a lookup filter

Adding an error to a field in a before trigger.

Sending an email alert using a workflow rule

Handling an exception in Apex.

Adding a validation rule

LastName

Name

AccountId

FirstName

The Test Suite Run panel of the Developer Console

The Apex classes setup page

The Apex Test Execution page

The Tests tab of the Developer Console

Use SOQL syntax to find the related Accounts Name field.

Use the {!contact.Account.Name} merge field syntax.

Use an additional standard controller for Accounts.

Use additional Apex logic within the controller to query for the Name field.

An Apex method in an extension that returns a list of Cases

An Apex method that executes SOQL to retrieve a list of Cases

A Visualforce page that displays information about Case records by iterating over a list of Cases.

Validation rules for a page layout that includes a related list of Cases

List<List<Account>, List<Opportunity»

Map<sObject, sObject>

Map<Id, sObject>

List<List<sObject»

1, 2

10, 2

100, 150

150, 100

Create a lookup relationship to indicate that a person has an employer.

Create a master-detail relationship to indicate that a person has an employer.

Create a junction object to relate many people to many employers through master-detail relationships.

Create a junction object to relate many people to many employers through lookup relationships.

String gryName = String.escapeSingleQuotes(name); String gryString = 'SELECT Id FROM Contact WHERE Name LIKE \'%' + gryName + 1%\"; List<Contact> queryResult = Database.query(qryString);

String qryName = '%' + String.enforceSecurityChecks(name) + '%'; String qryString = 'SELECT Id FROM Contact WHERE Name LIKE :qryName; List<Contact> queryResult = Database.query(qryString);

String qryName = '%' + name + '%'; String qryString = 'SELECT Id FROM Contact WHERE Name LIKE :qryName; List<Contact> queryResult = Database.query(qryString);

String gryString = 'SELECT Id FROM Contact WHERE Name LIKE \'%' + name + '%\"; List<Contact> queryResult = Database.query(qryString);

Use the Database class to handle DML operations.

Use Maps to reference related records.

Use SOQL Aggregate queries to retrieve child records.

Use Lists for all DML operations.

Create master-detail relationships in the Contact object to both the Property and Offer custom objects.

Create a lookup relationship in the Property custom object to the Offer custom object.

Create a master-detail relationship in the Offer custom object to the Property custom object.

Create a lookup relationship in the Offer custom object to the Property custom object.

It provides an event-driven architecture for better decoupling between components.

It allows faster PDF generation with Lightning components

it simplifies complexity when building pages, but not applications.

It promotes faster development using out-of-the-box components that are suitable for desktop and mobile devices.

Undefined

0

null

0.0

Add the SeeAllData annotation to the test class.

Add the TestVisible annotation to recordCount.

Change recordCount from private to public.

Add the TestVisible annotation to the MyController class

Database.upsert (myAccounts, Foreign_Key_c);

Database.upsert(myAccounts).Foreign_Key c;

Upsert myAccounts(Foreign_Key c);

Upsert myAccounts Foreign_Key_c;

The field is being populated by a workflow field update.

A DML exception is occurring during the save order of execution.

The field is being populated by a before trigger.

The user belongs to a permission set that suppresses the validation rule.

Setup a trace flag for the user, and define a logging level and time period for the trace.

Ask the user for access to their account credentials, log in as the user and debug the issue.

Create Apex code that logs code actions into a custom object.

It is not possible to setup debug logs for users other than yourself.

after insert

after update

before update

before insert

A change set deployment with the delete option checked

An ant migration tool deployment with a destructiveChanges XML file and the components to delete in the package.xml file

A change set deployment with a destructiveChanges XML file

An ant migration tool deployment with a destructiveChanges XML file and an empty package.xml file

ApexPages.StandardSetController controller = new ApexPages.StandardSetController(Database.getQueryLocator('SELECT Id FROM Account'));

ApexPages.StandardController controller = new ApexPages.StandardController([SELECT Id FROM Account]);

ApexPages.StandardController controller = new ApexPages.StandardController(Database.getQueryLocator('SELECT Id FROM ACCOUNT'));

ApexPages.StandardSetController controller = new ApexPages.StandardSetController(Database.query('SELECT Id FROM Account'));

ApexPages.StandardSetController controller = new ApexPages.StandardSetController(Database.getQueryLocator([SELECT Id FROM Account]));

Products and Pricebooks are visible in a test even if a class is annotated @isTest (SeeAnData=false) .

A method annotated @isTest (SeeAllData=false) in a class annotated @isTest (SeeAllData=true) has access to all org data.

A method annotated @isTest (SeeAllData=true) in a class annotated @isTest (SeeAllData=faise) has access to all org data.

Profiles are visible in a test even if a class is annotated @isTest (SeeAllData=false) .

A class containing test methods counts toward the Apex code limit regardless of any @isTest annotation.

Use a Validation Rule on a total score field on the candidate record that prevents a recommended field from being true if the total score is less than 15.

Use a Workflow Rule to calculate the sum of the review scores and send an email to the hiring manager when the total is 15 or better.

Use Visual Workflow to set a recommended field on the candidate whenever the cumulative review score is 15 or better.

Use a Rollup Summary field to calculates the sum of the review scores, and store this in a total score field on the candidate.

controller="Account"

extensions="AccountController"

standardController="Account"

action="AccountId"

An Apex trigger that uses an Aggregate Query to calculate the hours for a given timecard and stores it in a custom field

A Visualforce page that calculates the total number of hours for a timecard and displays it on the page

Process Builder process that updates a field on the timecard when a timecard entry is created

A Roll-Up Summary field on the Timecard Object that calculates the total hours from timecard entries for that timecard

When a record of a master object in a Lookup Relationship is deleted, the detail records are always deleted.

When a record of a master object in a Master-Detail Relationship is deleted, the detail records are kept and not deleted.

A Lookup Relationship is a required field on an object.

A Master-Detail Relationship detail record inherits the sharing and security of its master record.

Use the getRecordTypeInfosByDeveloperName() method in the DescribeSObjectResult class.

Make an outbound web services call to the SOAP API.

Execute a SOQL query on the RecordType object.

Hardcode the ID as a constant in an Apex class.

The helper class creates a savepoint and continues.

All changes in the transaction are rolled back.

All changes made by the custom controller are saved.

The custom controller calls the helper class method again.

It uses a junction object and lookup relationships to allow many User records to be related to many other User records.

It uses a junction object and master-detail relationships to allow many User records to be related to many other User records.

It uses a master-detail relationship to allow one User record to be related to another User record.

It uses a special lookup relationship to allow one User record to be related to another User record.

Create a test page that provides coverage of the custom controller.

Create a test page that provides coverage of the Visualforce page.

Create a test class that provides coverage of the Visualforce page.

Create a test class that provides coverage of the custom controller.

Boolean

List of sObjects

String

Integer

Single sObject

pageReference

override

standardController

controller

Simplifies addition of context-specific logic

Allows functional code to be tested by a test class

Increases trigger governor limits

Reduces trigger execution time

Create a Visualforce page that uses a controller class that is declared without sharing.

Type code into the Developer Console and execute it directly.

Type code into the Execute Anonymous tab in the Force.com IDE and click Execute.

Use the SOAP API to make a call to execute anonymous code.

Create and execute a test method that does not specify a ruzias () call.

includes a subset of metadata

requires a sandbox template

supports more frequent refreshes

provides more data record storage

The code runs with the permissions of the logged in user.

The code runs with the permissions of the user specified in the runAs () statement.

The code runs in system mode having access to all objects and fields.

Successful DML operations are automatically committed.

All DML operations are automatically rolled back.

Changes are being made to the Account during Criteria Based Sharing evaluation.

Changes are being made to the Account during an unrelated parallel save operation.

Changes to Opportunities are causing cross-object workflow field updates to be made on the Account.

Changes to Opportunities are causing roll-up summary fields to update on the Account.

for (variable : list_or_set) {... }

while (condition) {...}

for (init_stmt; exit_condition; increment_stmt) { ...}

do {... } while (condition)

The trigger fails if the Task Subject is blank.

A new Task is created for each Task in Trigger.new.

The trigger enters an infinite loop and eventually fails.

Multiple Tasks are created for each Task in Trigger.new.

Match an External Id Text field to a column in the imported file.

Match an Auto-Number field to a column in the imported file.

Match the Name field to a column in the imported file.

Match the Id field to a column in the imported file.

Use a custom controller.

Use a custom controller with extensions.

Use a standard controller with extensions.

Do not specify a controller.

Use a standard controller.

Set the attribute enableLightning to "true" in the definition.

Replace the third-party JavaScript library with native Visualforce tags.

Configure the User Interface options in the Setup menu to enable Legacy Mode for Visualforce.

Incorporate Salesforce Lightning Design System CSS stylesheets into the JavaScript applications.

5

50

500

5000

Resource usage and limits

Database changes

User login events

HTTP callouts to external systems

Actions triggered by time-based workflow

Static Resources

Documents

HttpCalloutMocks

WebServiceTests

To avoid Apex code coverage requirements for the code between these lines

To start and stop anonymous block execution when executing anonymous Apex code.

To indicate test code so that it does not impact Apex line count governor limits

To create an additional set of governor limits during the execution of a single test class.

public MyContactListController(ApexPages.StandardController stdController) { Account a = (Account) stdController.getRecord(); contacts = a.Contacts;
}

public MyContactListController(ApexPages.StandardSetController stdSetController) f contacts = (List<Contact>) stdSetController.getRecords();
}

public MyContactListController(List<sObject> records) f contacts = (List<Contact>) records;
}

public MyContactListController() { contacts = new List<Contact>();
}

Cross-object formulas can reference fields from master-detail or lookup relationships.

Cross-object formulas can reference fields from objects that are up to 10 relationships away.

Cross-object formulas can expose data the user does not have access to in a record.

Cross-object formulas can reference child fields to perform an average.

Cross-object formulas can be referenced in roll-up summary fields.

Elapsed CPU time

Number of new records created

Number of classes called

Elapsed SOQL query time

Use a Map <Id, Contact> for allContacts.

Add a GROUP BY clause to the Contact SOQL.

Put the Account loop inside the Contact loop.

Create an Apex helper class for the SOQL.

Roll-up summary field on the Opportunity object

Cross-object formula field on the Account object

Roll-up summary field on the Account object

Cross-object formula field on the Opportunity object

controller.js

superRender.js

renderer.js

helper.js

Approvals

Flow Builder

Process Builder

Workflows

Use SOQL to get all Cases

Use DescribeSObjectResult of the Case object.

Use Case.getRecordTypes().

Use DescribeFieldResult of the Case.RecordType field.

before update

after insert

before insert

after update

Integer

Decimal

Double

Currency

JavaScript that is used to make a menu item display itself.

StandardController system methods that are referenced by Visualforce.

Custom Apex and JavaScript code that is used to manipulate data.

A static resource that contains CSS and images.

Update the original object using an update DML operation.

Delete the original object using a delete DML operation.

Change field values using the Trigger.new context variable.

Display a custom error message in the application interface.

Use @IsTest(SeeAllData=true) and delete the existing standard Pricebook.

Use @TestVisible to allow the test method to see the standard Pricebook.

Use Test.getStandardPricebbokId()to get the standard Pricebook ID.

Use Test.loaddata() and a Static Resource to load a standard Pricebook

By using a helper class that can be invoked from multiple triggers.

By using the Database class to handle DML transactions.

By using Maps to hold data from query results.

By performing DML transactions on lists of sObjects

11, 150

150, 2

150, 11

2, 150

Workbench

Salesforce setup

Change Sets

Developer Console

Custom Controller

List Controller

Controller Extension

Standard Controller

Edit the managed package’s unit test

Select “Fast Deploy” to run only the tests that are in the change set

Select “Run local tests” to run only the tests that are in the change set

Select “Run local tests” to run all tests in the org that are not in the managed package

Changing territory assignments of accounts and opportunities

Updating record using bulk API

Converting leads to person account

An Apex batch process that changes field values

1,150

2,200

1,100

2,150

More frequent refreshes

Only includes necessary meta data

Use of change sets

Limited to 5 GB of data