CRT-450 Salesforce Certified Platform Developer I (SU24) Questions and Answers

When using purely declarative development to build the business logic layer in Salesforce, the following options are available:

Option A: Validation Rules

Explanation: Validation rules are declarative tools that enforce business rules on record data entry, ensuring data integrity.

When comparing Lightning Web Components (LWC) with Visualforce for the View layer in the MVC paradigm, several advantages stand out.

Option A: Self-contained and reusable units of an application

Correct Advantage.

Explanation:

LWCs are built using modular components that encapsulate their own structure, style, and behavior.

Components can be reused across different parts of the application, promoting consistency and reducing development time.

This modularity allows for better maintainability and scalability.

To fire an exception in Apex, the developer must use the throw statement along with an instance of the exception.

Option A: throw new ParityException();

Correct Way.

Explanation:

Creates a new instance of ParityException with no message and throws it.

Syntax is correct for throwing an exception.

Option C: throw new ParityException('parity does not match');

Correct Way.

Explanation:

Creates a new instance of ParityException with a custom message and throws it.

The exception class inherits from Exception, which allows passing a message to the constructor.

Options Not Correct:

Option B: new ParityException('parity does not match');

Incorrect.

Explanation:

This statement creates a new instance of ParityException but does not throw it.

Without the throw keyword, the exception is not fired.

Option D: new ParityException();

Incorrect.

Explanation:

Similar to Option B, this creates a new instance but does not throw it.

The exception will not affect the flow unless it is thrown.

Conclusion:

The two ways the developer can fire the exception are:

Option A: throw new ParityException();

Option C: throw new ParityException('parity does not match');

Both use the throw statement to fire the exception.

In a before insert trigger:

Trigger.old is null.

There is no existing record in the database to reference.

Why Not Other Options:

Option A: Describes Trigger.new.

Option B: The variable is defined but has a null value.

Option D: Trigger.old is not an empty list; it is null.

References:

Trigger Context Variables:

"In insert triggers, Trigger.old is null because the records are new."— Apex Developer Guide: Trigger Context Variables

To script the deployment and unit test execution as part of continuous integration (CI), developers use tools that can be automated and run from the command line or scripts.

Option D: Salesforce CLI

Correct.

Explanation:

The Salesforce CLI (Command-Line Interface) is a powerful command-line tool that allows developers to interact with Salesforce orgs.

It supports scripting of deployments using commands like sfdx force:source:deploy and running unit tests using sfdx force:apex:test:run.

The CLI can be integrated into CI/CD pipelines to automate deployments and testing.

To ensure that only records accessible to the currently logged-in user are displayed when developing an Apex class for custom search functionality launched from a Lightning Web Component (LWC), the developer should use the with sharing keyword.

with sharing Keyword: This keyword enforces the sharing rules of the current user, ensuring that the Apex class respects the user's record-level access permissions. When an Apex class is declared with with sharing, it enforces sharing rules, meaning users can only access records they have permission to see.

"Use the with sharing keyword when declaring a class to enforce the sharing rules that apply to the current user."— Apex Developer Guide: Using the with sharing or without sharing Keywords

Importance in LWCs: Lightning Web Components invoke Apex methods annotated with @AuraEnabled, which execute in system context by default. Without specifying sharing, these methods can access all records, potentially exposing data that the user shouldn't see.

"By default, Apex code runs in system context; that is, the current user's permissions and field-level security do not apply."— Apex Developer Guide: Enforcing Sharing Rules

Why Not inherited sharing: While inherited sharing allows an Apex class to run in the sharing context of the caller, in this scenario, since the LWC does not have an inherent sharing context, using with sharing explicitly ensures sharing rules are enforced.

WITH SECURITY_ENFORCED Clause: This SOQL clause enforces field-level security (FLS) and object-level security (OLS), not record-level sharing rules. Therefore, it does not restrict records based on the user's sharing settings.

"The WITH SECURITY_ENFORCED clause applies object-level and field-level security checks to SOQL queries to ensure that users don't see fields or objects they don't have access to."— SOQL and SOSL Reference: WITH SECURITY_ENFORCED Clause

Conclusion: By declaring the Apex class with with sharing, the developer ensures that only records the user has access to are returned, aligning with the requirement.

The requirement is for service agents to gather many pieces of information when processing damaged or stolen credit cards.

Option A: Screen-based Flow

Correct Answer.

Explanation:

A Screen Flow allows developers to build guided, interactive forms that collect information from users.

Flows can have multiple screens, validation rules, and branching logic.

They can be created declaratively without code, making them efficient to implement.

Benefits:

Efficient Development: No need for code.

User-Friendly: Provides a step-by-step interface.

Maintainable: Easy to update as requirements change.

Unit tests in Salesforce are designed to test Apex code functionality and can execute certain operations within the testing context.

Option C: Generate a Visualforce PDF with getContentAsPDF

Explanation: In unit tests, you can generate a PDF from a Visualforce page using the getContentAsPDF() method. This is allowed within test methods and is a valid operation for unit testing.

To back up all data and attachments in a Salesforce org, the standard approach is to use the Data Export Service.

Option B: Define a Data Export scheduled

Correct Answer.

Explanation:

The Data Export Service allows administrators to schedule a weekly or monthly export of all data and attachments.

The exported data can be downloaded as a set of CSV files and attachments in zip format.

When saving records using a custom controller in a Visualforce page, validation rule violations can occur. To display these validation error messages to the user, the developer should use the component.

Option A: Include <apex:messages> on the Visualforce page.

Correct Approach.

Explanation:

The component displays all messages that were generated for all components on the page, including validation rule violations.

When a DML operation is performed, any validation errors are automatically added to the ApexPages message collection.

Including in the page ensures that these messages are displayed to the user.

Example:

To update the flow to create a Contact and store the Contact’s ID on the Opportunity:

Option D: Add a new Create Records element.

Explanation: The flow needs to create a new Contact record using the Create Records element. After creating the Contact, you can store the Contact's ID in a variable and then update the Opportunity with the Contact’s ID.

Steps:

Add Create Records Element: Configure it to create a Contact and store the newly created Contact's ID in a variable.

Update Opportunity: Use the existing Update Records element or add a new one to update the Opportunity with the Contact's ID.

In the Aura framework, application events propagate through the component hierarchy in specific phases. The two main phases are:

Option A: Bubble

Correct Phase.

Explanation:

In the bubble phase, the event propagates upward from the source component to the root component.

Components can handle the event during this phase by registering an event handler with phase="bubble".

To send Opportunity values via an HTTP REST callout when a user presses a custom button in Lightning Experience:

Option B: Create a custom Visualforce quick action

Explanation:

A Visualforce page with a custom controller can perform the callout.

The Visualforce page can be added as a quick action on the Opportunity page.

When deciding between SOQL (Salesforce Object Query Language) and SOSL (Salesforce Object Search Language), developers must consider the use case and limitations of each.

Option A: SOSL is faster for text searches.

Correct Statement.

Explanation:

SOSL is optimized for searching text, especially across multiple objects and fields.

It uses full-text search indexes and can quickly find records that match search terms.

Ideal for scenarios where you need to search for a string across many fields.

To replace a JavaScript button from Salesforce Classic that creates records with prepopulated values in Lightning Experience, the developer can use:

Option A: Quick Actions

Quick Actions (Specifically, Object-Specific Actions):

Quick Actions allow users to perform actions, such as creating or updating records, from a record page or global context.

Prepopulating Fields:

You can predefine field values in Quick Actions using predefined values or by utilizing Lightning Component actions.

Option A: An External ID field can be used to reference an ID from another external system.

True.

Explanation:

External IDs are custom fields that have the External ID attribute selected.

They are used to store unique identifiers from external systems, allowing Salesforce to match and integrate data based on external IDs.

To efficiently generate a baseline set of data for unit tests that can be shared across multiple test methods, you should:

Option A: Use @TestSetup with a void method.

@TestSetup Annotation:

The @TestSetup method runs once before any test methods in the test class and is used to create common test data.

Data created in @TestSetup is available to all test methods within the test class.

Example:

@IsTest

private class MyTestClass {

@TestSetup

static void setupData() {

// Create Accounts, Contacts, Products, Assets

// This data is available to all test methods

}

@IsTest

static void testCase1() {

// Test logic here

}

@IsTest

static void testCase2() {

// Test logic here

}

}

The error message 'Maximum trigger depth exceeded' occurs when a trigger invokes itself recursively more than the allowed limit.

Option C: The trigger is getting executed multiple times.

Correct Answer.

Explanation:

This error indicates that the trigger is recursively calling itself.

This can happen if the trigger performs an update or insert operation that causes the same trigger to fire again, leading to an infinite loop.

Salesforce enforces a limit on the recursion depth to prevent stack overflows.

When creating a Visualforce page that uses a standard controller and a controller extension for a custom object named Notice__c, the correct syntax is:

Option D: apex

standardController="Notice__c" extensions="myControllerExtension"

Correct Syntax.

standardController attribute specifies the standard controller for the custom object Notice__c.

extensions attribute specifies the name of the Apex class myControllerExtension that extends the functionality of the standard controller.

In Salesforce, triggers are executed in response to specific database events on standard objects (such as Account or Contact) and custom objects. The following actions can cause triggers to fire:

Option A: Cascading delete operations

Explanation: When a record is deleted, and it has child records in a master-detail relationship, the child records are automatically deleted (cascade delete). This action fires the before delete and after delete triggers on the child records.

Option A: The Apex governor limits are reset for each iteration of the execute() method.

True.

Explanation:

In Batch Apex, each execution of the execute() method is a separate transaction.

Governor limits are reset at the start of each transaction.

To check the code coverage of a class after running all tests, a developer can use the Developer Console.

Option B: View the code coverage percentage for the class using the Overall Code Coverage panel in the Developer Console Tests tab.

Correct Method.

Explanation:

In the Developer Console, navigate to the Tests tab.

After running tests, the Overall Code Coverage panel displays code coverage statistics.

You can see the coverage percentage for individual classes.

When designing a new application on the Salesforce platform that needs to support multiple tenants effectively (i.e., multiple customers or users), the developer should consider the Model-View-Controller (MVC) framework.

Option B: Model-View-Controller (MVC)

Correct Design Framework.

Explanation:

MVC is a software architectural pattern for implementing user interfaces.

Model: Represents the data and business logic.

View: Represents the presentation layer.

Controller: Handles user input and interactions.

Salesforce's platform follows the MVC pattern, which helps in separating concerns, ensuring scalability, and maintainability.

As of Winter '20 (API version 47.0), Salesforce introduced the ability to test Autolaunched Flows with test coverage.

However, as of the current knowledge cutoff (2023-09), there is no direct way within the Salesforce UI to check the test coverage of autolaunched flows before deploying them via change sets.

To check the test coverage of flows, developers can use the Tooling API to query for test coverage.

Option A: Use SOQL and the Tooling API.

Correct Answer.

Explanation:

Developers can use the Tooling API to query for Flow test coverage information.

By executing a SOQL query on FlowTestCoverage and FlowVersionView objects via the Tooling API, developers can retrieve coverage data.

This allows checking flow test coverage programmatically before deployment.

Executing Anonymous Apex code is useful for running ad-hoc operations or administrative tasks in Salesforce.

Option A: To run a batch Apex class to update all Contacts

Valid Use Case.

Explanation:

Anonymous Apex can be used to initiate a batch Apex job.

The developer can write code in the Execute Anonymous window to instantiate and execute the batch class.

Example:

Database.executeBatch(new UpdateContactsBatchClass());

There are several ways to execute tests in a Salesforce org:

Option A: Setup Menu

Valid Method.

Explanation:

Tests can be run from the Salesforce Setup menu under Apex Test Execution.

Allows selecting and running test classes and methods.

To implement a process where every time an Opportunity is created, a follow-up Task should be created and assigned to the Opportunity Owner, the most efficient method is to use a Record-Triggered Flow on the Opportunity object.

Option B: Record-triggered flow on Opportunity

Declarative Solution: Salesforce Flows provide a powerful, declarative way to automate business processes without writing code.

Triggering Event: The flow is configured to trigger when a new Opportunity record is created.

Create Task Record: The flow includes an element to create a new Task record.

Set the Assigned To field to the Opportunity Owner.

Populate other Task fields as necessary (e.g., Subject, Due Date).

Efficiency: Flows are more efficient than Apex triggers for simple automation and are easier to maintain.

Best Practice: Salesforce recommends using Flows over Workflow Rules and Process Builders for new automations.

For integrating automated tests into a Continuous Integration (CI) process, the Universal Containers development team should use the Salesforce CLI.

Option C: Salesforce CLI

Salesforce CLI (Command Line Interface) is a powerful command-line tool that allows developers to script and automate various Salesforce tasks, including running tests, deploying code, and retrieving metadata.

Automated Testing:

Developers can use the sfdx force:apex:test:run command to run Apex tests and include it in their CI scripts.

Example Command:

sfdx force:apex:test:run --testlevel RunLocalTests --resultformat human --outputdir test-results

Defining the Order Number field as an External ID and marking it as Unique ensures:

External ID:

Allows the field to be used for matching during data import.

Helps in upsert operations.

Unique:

Ensures no duplicate Order Numbers exist.

Maintains data integrity.

Why Not Other Options:

Option A: Direct Lookup is not a valid field type for this scenario.

Option B: Lookup fields create relationships, not suitable here.

Option D: Indirect Lookup is used with external objects.

References:

External IDs:

"An external ID is a custom field that has the External ID attribute, meaning that it contains unique record identifiers from a system outside of Salesforce."— Salesforce Help: External ID Fields

To allow partial success when inserting a list of records, the developer should use the Database class methods with the allOrNone parameter set to false.

Option B: Database.insert(records, false)

Correct Answer.

Explanation:

The Database.insert() method allows for partial processing.

By setting the second parameter (allOrNone) to false, the operation will attempt to insert all records.

If some records fail, the successful ones will be committed, and the errors can be examined from the result.

Usage:

Database.SaveResult[] results = Database.insert(records, false);

for (Database.SaveResult sr : results) {

if (sr.isSuccess()) {

// Record inserted successfully

} else {

// Handle errors

for (Database.Error err : sr.getErrors()) {

System.debug(err.getMessage());

}

}

}

To check whether the current user has permission to delete an Account, the developer should use the Schema.sObjectType methods.

Option D: Schema.sObjectType.Account.isDeletable()

Correct Method.

Explanation:

The Schema.sObjectType.Account provides describe information about the Account object.

The isDeletable() method returns a Boolean indicating whether the current user has permission to delete records of this type.

Usage:

if (Schema.sObjectType.Account.isDeletable()) {

// User has permission to delete Accounts

delete accountRec;

} else {

// Handle lack of permission

}

Options Not Applicable:

Option A: Account.isDeletable()

No such static method on the Account object.

Option B: accountRec.sObjectType.isDeletable()

sObjectType returns a token; to get describe results, you need to call getDescribe().

Option C: accountRec.isDeletable()

There is no instance method isDeletable() on sObject records.

Conclusion:

To ensure proper permission checks, the developer should use Schema.sObjectType.Account.isDeletable(), which is Option D.

To build a responsive application capable of responding to touch events and executed on stateful clients, the developer should use technologies that support modern web standards, responsive design, and touch interactions. The two technologies that meet these requirements are Aura Components and Lightning Web Components.

Option A: Aura Components

Explanation: Aura Components are part of the Lightning Component Framework and are designed to build dynamic web applications for mobile and desktop devices. They support responsive design and can handle touch events, making them suitable for building applications that run on stateful clients.

When deploying Apex code to production, Salesforce requires that all Apex triggers have at least 1% code coverage and the overall code coverage must be at least 75%.

In this scenario:

The developer has a test class that covers 95% of the helper class.

The deployment fails because the trigger has 0% coverage.

The error message indicates that the trigger needs at least 1% coverage.

Solution:

Option A: Create a test class and methods to cover the Apex trigger.

Correct Action.

Explanation:

Write a test class that specifically tests the trigger's functionality.

Ensure that the trigger is executed within the test context.

This will increase the trigger's code coverage above the required 1%.

When importing an Apex method into a Lightning Web Component (LWC), the correct syntax is:

import methodName from '@salesforce/apex/ClassName.methodName';

Option D: import updateAccounts from '@salesforce/apex/AccountController.updateaccounts';

Correct Syntax.

Explanation:

import updateAccounts:

Specifies the JavaScript function name to reference in the LWC.

from '@salesforce/apex/AccountController.updateaccounts';:

Indicates that we are importing from an Apex class named AccountController, and the method is updateaccounts.

Case Sensitivity:

The class and method names are case-sensitive and should match the Apex code.

In Aura Components, application events are fired by invoking the fire() method on the event instance.

Option D: fire()

Correct.

Explanation:

To fire an application event, you first get the event instance using cmp.getEvent("eventName") and then call fire() on it.

Example:

var appEvent = $A.get("e.namespace:eventName");

appEvent.setParams({ "param1" : value1 });

appEvent.fire();

To embed a Flow into an Aura component, you use the lightning:flow component.

Option A: lightning

Correct Answer.

The lightning:flow component allows you to embed a Flow in an Aura component.

Example Usage:

The accurate statements about debug logs are:

Option A: System debug logs are retained for 24 hours.

Explanation: Salesforce retains debug logs for 24 hours after they are generated.

Option D: Use Test.getStandardPricebookId() to get the standard price book ID.

Correct Answer.

Explanation:

The Test.getStandardPricebookId() method returns the ID of the standard price book, which can be used in test classes without using SeeAllData=true.

This allows the test to access and use the standard price book in a controlled manner.

Option C: Update the PrimaryId__c field definition to mark it as an External Id.

Correct Answer.

Explanation:

Marking PrimaryId__c as an External ID allows data loading tools to match records based on this field.

This facilitates upserting data and ensures that the CSV data correctly maps to existing records.