Dev 1 - 31 onwards

39. You have been requested to generate a simple PDF displaying line items for an Opportunity. How can you best achieve this?

• Search for an App on the AppExchange

• Create a Visualforce page with ‘renderAs=”pdf”’

• Create a Lightning Web Component and call the renderAsPdf() method

• Use a third party API

Answer explanation

Visualforce pages are the only on-platform technology that can be used to render PDFs, and since the PDF to be generated here is simple,

utilising this functionality is the best approach.

For more complex PDFs, utilising an AppExchange app would be preferred since it wouldn’t require developers to build something from scratch,

and instead would only require installing an App.

What is the value of “foo” after this following code has been executed?

• 10

• 20

• 30

• 40

Answer explanation

Switch statements allow a developer to test whether an expression matches one of several different values in a branch, and perform some code based on the matching branch.

In the question, the switch operation compares an Enum value against several options. Since the value operation is AFTER_INSERT, the switch statement evaluates each branch until it matches the AFTER_INSERT value, which executes the code block, which sets foo to equal 30.

What would the value of the instance variable “foo” be after the third execution of the following batch class?

• 1

• 2

• 3

• 4

Answer explanation

The instance variable is initially initialised as 1 during the constructor of the batch class. This is then incremented by 1 for each execute method

run. Since this batch class also implements Database.Stateful, the instance variables of this class are preserved after each execute method call,

hence why the output value is 4.

What are the valid target source pairs for a changeset deployment? (Choose 2)

• Developer org – Production Org

• Developer org – Sandbox

• Sandbox – Sandbox

• Sandbox – Production Org

Answer explanation

Changesets are only available within a production org and its sandboxes. The purpose of them is to allow development and testing to be done in

a metadata clone of a production org, and for those changes to be migrated into production when ready.

Since developer orgs are not tied to a production instance and are instead standalone, they do not feature changesets and so cannot be the

target nor the source of a changeset deployment

How can a developer execute an anonymous block of Apex code? (Choose 3)

• Use the “Execute Anonymous” functionality of the Developer Console

• Use the “Execute Anonymous” functionality within the Setup area

• Utilise the REST API “executeAnonymous” endpoint

• Use the Salesforce CLI “force:apex:execute” command

• Use the Salesforce CLI “force:apex:execute:anonymous” command

• Write a class with the @Anonymous annotation

• • Use the “Execute Anonymous” functionality of the Developer Console

• • Use the “Execute Anonymous” functionality within the Setup area

• • Utilise the REST API “executeAnonymous” endpoint

• • Use the Salesforce CLI “force:apex:execute” command

• • Use the Salesforce CLI “force:apex:execute:anonymous” command

Answer explanation

Anonymous Apex code can be executed both on platform and off platform. On platform this is done directly in the Developer Console, utilising the Developer Console’s inbuilt functionality.

When we wish to run code off platform, there are several ways this can be achieved. One of the easiest is to utilise the Salesforce CLI commands, as these can run code directly from either a terminal, or from code stored within a file. Lastly we can utilise either the SOAP or the REST APIs to send code to Salesforce to be executed.

You have an @AuraEnabled method which accepts an SObject from a Lightning Component which will be inserted, how can you easily sanitise

the user’s input?

• There is no need, @AuraEnabled method automatically enforce FLS

• Use the Database.insertSecure() method

• Use the DescribeSObjectResult to check the user permissions for each populated field on the SObject

• Use the Security.stripInaccessible() method

Answer explanation

The Security class methods are designed explicitly for easily enforcing the FLS of the current user by stripping anything which is not accessible in

the defined context.

While checking each field’s accessibility using the DescribeSObjectResult for the SObject is a valid approach, it is far more verbose and requires

a lot more code to achieve the same results as utilising the Security.stripInaccessible() methods.

How can a developer declaratively access a specific custom metadata type (MyCustomMetadataType__mdt) record within Apex?

• MyCustomMetadataType__mdt.getRecord(‘Record_Name’);

• CustomMetadata.get(‘MyCustomMetadataType__mdt’).get(‘Record_Name’);

• MyCustomMetadataType__mdt.getInstance(‘Record_Name’);

• MyCustomMetadataType__mdt.(‘Record_Name’);

Answer explanation

Each custom metadata type comes with its own SObject type in Apex. This type contains additional methods which can be used to declaratively

obtain records from a custom metadata type by developer name or record Id. These methods are similar to those found on custom settings.

You have been tasked with importing data from a legacy CRM system into a new Salesforce org. The legacy CRM system had database tables

analogous to the Account, Contact and Opportunity objects within Salesforce. How could you best ensure the relationships are preserved during

this data migration?

• Add fields flagged as external Ids for each of the objects to be imported, populated with its legacy CRM Id, use the Data Loader tool,

  and set the relationship fields to match these external Ids

• Add fields flagged as external Ids for each of the objects to be imported, populated with its legacy CRM Id, write a script to re-establish

  relationships after import

• Add a field to each object for its legacy CRM Id, after importing each object, export them and use a VLOOKUP function in Excel to

  match the Ids

• Add a field to each object for its legacy CRM Id, write an Apex trigger that on insert matches the record to its parent

Answer explanation

External Ids allow flagging a field as an Id which is used within an external system. This allows the field to be utilised in Upsert calls, where

instead of specifying the Salesforce Id for a relationship field, the external Id can be used instead. The external Id is then used to find the record

within Salesforce and the relationship field value gets replaced with its Salesforce Id instead. This type of operation is supported by the Data

Loader tool.

Utilising manual methods of doing this match introduces the risk of human error when re-establishing the relationships.

Which of the following uses the correct naming convention to be used for naming CustomEvent fired from Lightning Web Components using

dispatch event?

• onMyAction

• myAction

• my action

• my_action

Answer explanation

The naming scheme for events within Lightning Web Components follows the DOM event standard. This means that all event names must not

use uppercase letters, have no spaces, and use underscores to separate words.

A developer creates an Apex trigger which calls a method within another class. A test has been written which directly calls the method within the

class and provides 100% code coverage. There are no other Apex classes present within the org. What would be the result of deploying a

changeset with this trigger and classes into production with running all tests?

• The deployment succeeds due to code coverage being above 75%

• The deployment succeeds due to the total number of lines covered by tests in the deployment being above 75%

• The deployment fails because the Apex trigger has 0% code coverage

• The deployment fails as the not every component in the deployment has 75% code coverage

Answer explanation

When doing a deployment into production, there must be an average of 75% code coverage for all Apex code within the org. Alongside this, Apex

triggers being deployed must have at least 1 line being covered (i.e. they must have been called by at least one test class).

When running deployments, there is the option to run a subset of tests which changes the code coverage behaviour. When running the default

testing mode, all tests are executed and the total coverage in an org must meet 75%. However, when running a specified set of tests, every item

in the deployment must average 75% instead.