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

Lightning Web Components (LWC) can access various Salesforce resources.

Option B: SVG resources

Accessible.

Explanation:

LWCs can include SVG files to define custom icons for the component.

The SVG file is placed in the component bundle with the name componentName.svg.

When a developer is alerted to an issue with a custom Apex trigger causing records to be duplicated, the most appropriate debugging approach is to add System.debug statements to the code.

Option A: Add System.debug statements to the code to track the execution flow and identify the issue

Trace Execution Flow: System.debug statements help log the values of variables and the execution path.

Identify Logic Errors: By examining the debug logs, the developer can pinpoint where the duplication is occurring.

Minimal Impact: Adding debug statements is a minimal code change and does not alter the functionality.

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 make a Lightning Web Component (LWC) available in Salesforce Classic, you can embed it in a Visualforce page using Lightning Out.

Option D: Use the Lightning Out JavaScript library to embed the Lightning Web Component in a Visualforce page and add to the page layout.

Lightning Out allows LWCs to be embedded in Visualforce pages.

The Visualforce page can then be included in Salesforce Classic interfaces.

Why Not Other Options:

Option A: Visualforce components cannot directly contain LWCs.

Option B: Wrapping an LWC in an Aura component and surfacing it as a Visualforce tab doesn't make it available on page layouts.

Option C: You cannot invoke an LWC from a Visualforce page using an Apex method call.

References:

Lightning Out for Visualforce:

"Lightning Out is a feature that extends Lightning components to any web page. Use it to embed Lightning web components in a Visualforce page."— Lightning Web Components Dev Guide: Use Lightning Web Components in Visualforce Pages

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.

To override the Account's standard Edit button in Lightning Experience:

Option A: Lightning component

Explanation: In Lightning Experience, you can override standard buttons with Lightning components by implementing the appropriate interface.

Implementation:

The Lightning component must implement lightning:actionOverride interface.

Option A: Specifying loading order

True.

Explanation:

The tag allows you to specify the order in which scripts are loaded by the sequence in the scripts attribute.

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.

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.

Option A: Developer and Developer Pro sandboxes have different storage limits.

True.

Explanation:

Developer Sandbox:

Provides 200 MB of data storage and 200 MB of file storage.

Developer Pro Sandbox:

Provides 1 GB of data storage and 1 GB of file storage.

The storage limits affect how much data you can import into these environments.

To ensure that the Food_Preference__c picklist field has a value every time a record is created or updated, marking the field as Required on the field definition is the optimal solution.

Option C: Mark the field as Required on the field definition

Universal Enforcement: Setting the field as required at the field level ensures that it must have a value regardless of how the record is created or updated (UI, API, data import).

Data Integrity: Prevents records from being saved without a value in the picklist field, maintaining data consistency.

No Additional Code: Achieves the requirement declaratively without the need for Apex code.

When a batch Apex job is timing out and not completing, the first step in troubleshooting is to check the job's status and logs in the Asynchronous Job Monitoring page. This page provides information about all asynchronous Apex jobs, including batch Apex, scheduled Apex, future methods, and queueable Apex.

Option D: Check the asynchronous job monitoring page to view the job status and logs.

Correct Approach.

Explanation:

The Asynchronous Job Monitoring page (also known as the Apex Jobs page) in Salesforce Setup allows developers to see the status of all asynchronous Apex jobs.

By checking this page, the developer can see whether the batch job is still running, failed, or completed.

If the job has failed, the page provides error messages that can help identify the cause of the failure.

This is the first step to determine what is happening with the batch job.

To update the Timezone__c field on Account based on the Postal Code and values from PostalCodeToTimezone__c:

Option B: Account Trigger

Explanation:

An Apex trigger can query the PostalCodeToTimezone__c object and update the Timezone__c field when the Postal Code is changed.

Scenario:

Universal Containers (UC) wants to allow multiple Accounts to share a default pickup address.

They have created a custom object called Global Address.

Requirement:

Create an efficient model to link multiple Accounts to a single Global Address.

Solution:

To associate multiple Accounts with a single Global Address, we need to create a lookup relationship from Account to Global Address.

Option D: Add a lookup field on the Account object to the Global Address object.

Correct Approach.

Explanation:

Adding a Lookup Field on the Account object that references the Global Address object allows multiple Accounts to reference the same Global Address.

This setup models a many-to-one relationship:

Many Accounts can have the same Global Address as their pickup address.

Benefits:

Data Normalization: Reduces data redundancy by storing the address once.

Ease of Maintenance: Updating the Global Address updates it for all associated Accounts.

A polymorphic lookup field is a special type of lookup relationship field that can reference multiple object types.

Option C: The WhatId field on the standard Event object

Correct Answer.

Explanation:

The WhatId field on Event (and Task) can refer to multiple types of objects, such as Account, Opportunity, Custom Objects, etc.

This makes WhatId a polymorphic lookup field.

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.

To notify the parent component from a child component when a button is clicked:

Option C: Create a custom event

Explanation: In Lightning Web Components, child components communicate with parent components by dispatching custom events.

Child Component:

// ChildComponent.js

handleClick() {

const nextEvent = new CustomEvent('next');

this.dispatchEvent(nextEvent);

}

Parent Component:

javascript

Copy code

// ParentComponent.js

handleNext() {

// Navigate to the next page

}

Declarative Development refers to building applications using Salesforce's point-and-click tools without writing code. It has several characteristics:

Option C: Declarative development does not require Apex test classes.

True.

Declarative tools like Flows, Process Builder, and Validation Rules do not require Apex test classes because they are configured via the UI and not through code.

Universal Containers wants to prevent Opportunities from being edited once they reach the Closed/Won stage. To achieve this, the developer can use the following strategies:

Option A: Use a validation rule.

Correct Approach.

Explanation:

A validation rule can be created on the Opportunity object to prevent users from editing records when the Stage is Closed/Won.

The validation rule would evaluate whether the record's StageName is 'Closed Won' and, if so, display an error message when a user attempts to edit and save the record.

Example Validation Rule:

AND(

ISPICKVAL(StageName, 'Closed Won'),

ISCHANGED(ANYFIELD) // Replace ANYFIELD with specific fields if needed

)

Benefits:

Declarative Solution: No code required.

Consistent Enforcement: Applies across all user interfaces and API.

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.

To allow moving existing OrderItem records to a new Order record in a master-detail relationship:

Option B: Select the Allow reparenting option on the master-detail relationship.

Explanation: Enabling "Allow reparenting" on the master-detail field allows child records (OrderItem) to be reparented to a different master record (Order).

Steps:

Go to the master-detail field on OrderItem.

Edit the field and select "Allow reparenting".

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.

The first step in the Salesforce order of execution:

Option D: The original record is loaded from the database.

This is Step 1 in the order of execution.

Why Not Other Options:

Option A: Overwriting old values happens after loading the record.

Option B: JavaScript validation occurs on the client side before server processing.

Option C: System validation for field lengths happens after loading the record.

References:

Order of Execution:

"1. Loads the original record from the database or initializes the record for an upsert statement."— Apex Developer Guide: Triggers and Order of Execution

Understanding the Issue:

The provided code attempts to update a list of Account records:

public static void insertAccounts(List theseAccounts) {

for(Account thisAccount : theseAccounts) {

if(thisAccount.website == null) {

thisAccount.website = 'https://www.demo.com ';

}

}

update theseAccounts;

}

Problem: A DML exception is thrown when the update statement executes.

Possible Causes:

Some records in theseAccounts may have validation rule failures.

There may be null records within the theseAccounts list.

There could be fields that violate data integrity constraints.

Option Analysis:

Option A: Implement Change Data Capture

Explanation: Change Data Capture (CDC) is used to capture changes to Salesforce records and send notifications.

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.

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

Option A: Data Import Wizard does not support Opportunities.

Explanation: The Data Import Wizard supports importing data for certain standard objects (Accounts, Contacts, Leads, Solutions, Campaign Members, and Person Accounts) and custom objects. It does not support importing data into all standard objects like Opportunities.

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();

Option A: Roll-up summary fields can cause the parent record to go through Save.

True.

When a child record changes, roll-up summary fields on the parent object are recalculated.

This causes the parent record to save, which can trigger triggers on the parent object.

To send an outbound message when a record meets specific criteria without using Apex code, we can use features that support outbound message actions.

Option B: Approval Process can be used to check the record criteria and send an outbound message without Apex code.

Correct Feature.

Explanation:

An Approval Process can include outbound message actions.

When a record enters a specific step of the approval process, an outbound message can be sent.

Criteria can be defined to determine when the approval process starts.

Option C: In a test setup method, test data is inserted once and made available for all test methods in the test class.

True.

The @testSetup method runs once before any test methods in the class.

Test data created in this method is available to all test methods, promoting code reuse and efficiency.

Option D: VS Code

Correct Answer.

Explanation:

Visual Studio Code with the Salesforce Extension Pack is the recommended IDE for developing and fixing Lightning Web Components.

It provides features like syntax highlighting, IntelliSense, debugging, and seamless deployment to a sandbox.

To perform DML operations that insert new records and update existing records in a list of Order__c records using the external ID field Order_Number__c, you should use:

Option D: upsert orders Order_Number__c;

Upsert Statement:

The upsert DML operation either inserts or updates records based on whether they already exist.

By specifying the external ID field (Order_Number__c), Salesforce will match existing records based on this field.

Syntax:

upsert orders Order_Number__c;

orders is the list of Order__c records.

Order_Number__c is the external ID field used for matching.

Change Sets are a point-and-click tool for migrating metadata between related Salesforce orgs, such as from a sandbox to a production org.

Option C: Deployment is done in a one-way, single transaction.

Correct.

Explanation:

Change sets are deployed in a one-way direction from the source org to the destination org.

The deployment occurs in a single transaction. If any component fails to deploy, the entire deployment is rolled back.

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());

To improve runtime performance by caching Apex call results on the client, the developer should decorate the server-side method with @AuraEnabled(cacheable=true).

@AuraEnabled(cacheable=true) Annotation:

When applied to an Apex method, it enables the method's results to be cached on the client, improving performance for subsequent calls.

This is especially effective in Lightning Web Components (LWC) and can also be used in Aura components.

"To cache method results, annotate the method with @AuraEnabled(cacheable=true). Methods annotated with cacheable=true are called cached methods."— Lightning Web Components Developer Guide: Call Apex Methods

Why Not Other Options:

A. Call the setStorable() method on the action in the JavaScript client-side code: This approach is used in Aura components but is less efficient and not considered best practice compared to using cacheable=true.

"For improved performance, use @AuraEnabled(cacheable=true) instead of action.setStorable()."— Aura Components Developer Guide: Calling Server-Side Actions

B. Set a cookie in the browser for use upon return to the page: Managing cookies for caching Apex results is not efficient and can lead to security and scalability issues.

C. Decorate the server-side method with @AuraEnabled(storable=true): There is no storable=true parameter for @AuraEnabled. The correct parameter is cacheable=true.

Best Practices:

Use @AuraEnabled(cacheable=true): This is the recommended way to cache Apex method results in Lightning components.

"Apex methods annotated with @AuraEnabled(cacheable=true) are cached on the client and shared across components."— Lightning Web Components Developer Guide: Apex Methods Cache

Conclusion: By decorating the Apex method with @AuraEnabled(cacheable=true), the developer enables client-side caching of the method's results, improving runtime performance in an efficient and recommended way.