Dev 1 full dump

There are two before save triggers defined for the Contact object, which one of them runs first?

• The trigger which was created first

• The trigger which was created last

• Both execute together

• The order is random

Answer explanation

When multiple triggers are defined on an object, the order in which they are executed cannot be guaranteed or relied upon. Instead, it is a best

practice to ensure only a single trigger is defined on an object which hands off to other classes to perform business logic.

As a developer, you wish to utilise scratch orgs to streamline the development process within your team. What are the requirements to do this?

• Enable Dev Hub

• Have a user with permissions to create Scratch Orgs

• Have the Salesforce CLI setup

• Have the Salesforce CLI setup

• All of the options

Answer explanation

To utilise scratch orgs, the Dev Hub must be enabled in an org to allow scratch orgs to be created. Each developer wishing to create scratch orgs

from that Dev Hub must have a user with the correct permissions to manage scratch orgs and access the scratch org objects in that org. Using

the Salesforce CLI this user can login into the Dev Hub and be used to request the creation of scratch orgs.

How can data for a record be easily accessed in Lightning Components?

• Utilize the standard Lightning Component Controller

• Write an @AuraEnabled Apex methods to return the data

• Utilize the Lightning Data Service

• Use fetch requests within the component to call the Salesforce APIs

Answer explanation

When building components that work on individual records, the Lightning Data Service provides a performant and cached mechanism for loading

and updating record data that gets propagated throughout all components utilising the service.

This offers advantages over performing Apex calls to achieve simple record data since it increases performance and allows changes in other

areas of the UI (for example for the standard record details component) to propagate to other components.

A custom field on Opportunity is assigned the number data type, with 18 digits and 0 decimal places. Which primitive data type would this be

assigned in Apex?

• Decimal

• Long

• Double

• Integer

Answer explanation

All data stored within a number field (or number returning formula) is represented as a Double when accessed within Apex.

Which of the following snippets can be used to obtain the Stage picklist values on the Opportunity object?

• Opportunity.StageName.getDescribe().getPicklistValues();

• Opportunity.StageName.getMetadata().getPicklistMetadata();

• Opportunity.StageName.getDescribe().getPicklistDescribe ();

• Opportunity.StageName.getDescribe().getPicklistOptions();

Answer explanation

To access field metadata within Apex we use the FieldDescribeResult for the field we are interested in, this can be accessed declaratively as in

the answer to this question, or programmatically as shown below.

Which of the following statements should be added to the following for loop to exit the loop – on line 10 – when a matching record is first found?

• break;

• exit;

• continue;

• goto start;

Answer explanation

To exit out of a for loop early we can use the “break” statement which stops any code after it, and any additional items which would have been

looped over from being run.

The “continue” statement is used when we wish to exit the current loop iteration early and progress onto the next one.

An integration is to be built which inserts Leads into your company’s Salesforce instance in bulk from its website daily. Some of the records are

spam and do not contain valid field data. Which of the following statements would facilitate this?

• insert leads false;

• Database.insert(leads, false);

• Database.insert(leads, true);

• Database.insertPartial (leads, false);

• None of the above

Answer explanation

When we wish to configure the DML operation, or handle failed records, we must use the Database class methods. When we specify false for the

allOrNone parameter, instead of an exception being thrown when any record encounters an error during save, a List<Database.SaveResult> is

returned instead of an exception being thrown.

As a developer you have been tasked with creating a simple record form to create Cases on a private community page, how could you best

achieve this?

• Use a Lightning Component with a Lightning Record Form to display the form

• Write a custom component to display the required fields

• Build a Visualforce page which utilizes the standard case controller

• Imbed Web-to-Case into the page

Answer explanation

To easily create record forms, a lightning-record-form component is the best choice. This component can be used to rapidly create forms based

on a list of fields or layouts for an object choice, which can allow admins to maintain the forms without requiring developer intervention.

What tools can be used to develop Lightning Web Components?

• The Developer Console

• The Salesforce Eclipse IDE

• VSCode and the Salesforce Extension Pack

• The Salesforce CLI

Answer explanation

Outside of reviewing code from inbound changesets, there is no way to view Lightning Web Components on the platform. Instead, we must utilise

an external tool to view the source code for these. The Salesforce extension pack for VSCode is one such tool for this. While the extension pack

utilises the Salesforce CLI for a lot of its operations, the CLI on it’s own isn’t capable of reviewing the source code for LWCs and is instead used

to communicate with the Salesforce servers (e.g. deploying and retrieving the LWCs), but not for writing the code directly.

Which of the following is true about roll-up summary fields?

• They can be used across both Master-Detail and Lookup relationships, on the parent side

• They can be used on Master-Detail relationships, on both the parent and child side

• They can be used across both Master-Detail and Lookup relationships, on both the parent and child side

• They can be used across Master-Detail relationships, on the parent side

Answer explanation

Roll-up summary fields are a feature of Master-Detail relationship that allow the Master record to calculate details about all of it’s detail records,

e.g. a count of the number of Detail records belonging to a Master record.