SALESFORCE-PD1 Practice Test 19 — 15 Questions

Question 1

A developer needs to include a third-party style sheet in a Lightning Web Component. What is the standard way to load CSS styles that are stored as a static resource?

Accepted Answer

import { loadStyle } from 'lightning/platformResourceLoader';. The platformResourceLoader module provides the loadStyle function, which loads a CSS file from a static resource into a Lightning Web Component. This is the standard way to include third-party stylesheets stored as static resources.

Answer

Declaring the stylesheet in the component's metadata configuration file under <stylesheets>.

Answer

import stylesheet from '@salesforce/resourceUrl/myCSS';

Answer

Using a standard <link> tag pointing directly to the static resource URL in the HTML template.

Question 2

A developer is styling a Lightning Web Component using the Salesforce Lightning Design System (SLDS). To ensure the component adheres to the standard styling guidelines for spacing, what should the developer use?

Accepted Answer

SLDS standard spacing utility classes.. SLDS provides a documented set of spacing utility classes (e.g., slds-m-around_medium, slds-p-horizontal_small) that enforce the design system's standardized spacing scale. Using these utilities guarantees visual consistency across components and future-proofs the UI against SLDS token changes. This is the officially recommended approach for adhering to SLDS styling guidelines.

Answer

Inline styles directly in the HTML template.

Answer

Standard HTML blockquote tags with custom margin properties.

Answer

Hardcoded pixel values in the component's CSS file.

Question 3

A developer encounters a 'System.AsyncException: Maximum queueable jobs added to the queue' error. What caused this exception?

Accepted Answer

Exceeding the maximum number of 50 queued jobs in a single transaction.. Exceeding the limit of 50 queued jobs added to the flex queue in a single transaction triggers this AsyncException.

Answer

Running more than 500 batch jobs simultaneously.

Answer

Exceeding the daily asynchronous Apex limit of 250,000.

Answer

Making more than 100 callouts in a future method.

Question 4

What is the primary purpose of the Salesforce CLI in a CI/CD pipeline?

Accepted Answer

To automate metadata deployment and package management.. The Salesforce CLI is the fundamental tool for programmatically interacting with Salesforce Orgs in automation.

Answer

To provide a visual interface for Change Sets.

Answer

To run unit tests manually.

Answer

To debug Apex in a GUI.

Question 5

A developer is reviewing a Lightning Web Component that makes calls to an Apex controller. Which THREE best practices should be followed when designing the Apex methods for LWC consumption? (Choose THREE)

Accepted Answer

Use primitive data types or simple serializable wrapper classes for parameters and return values.. Option A is correct because Apex methods exposed to Lightning Web Components via @AuraEnabled must use primitive types or simple serializable wrapper classes for parameters and return values, since complex or non-serializable types cannot be properly marshalled across the client-server boundary. Option B is correct because Apex does not automatically enforce object and field-level security (FLS) for @AuraEnabled methods, so developers must explicitly enforce CRUD/FLS using WITH SECURITY_ENFORCED, Security.stripInaccessible, or Schema describe calls to prevent unauthorized data exposure. Option D is correct because annotating read-only methods with @AuraEnabled(cacheable=true) enables client-side caching in the Lightning Data Service, reduces server round trips, and improves component performance for idempotent data retrieval. Option C is incorrect because marking methods as global is unnecessary and overly permissive; @AuraEnabled methods only need to be public (or global in specific managed-package contexts) and global does not grant unrestricted LWC access. Option E is incorrect because passing entire sObjects with complex parent relationships without validation risks serialization failures, exceeds payload limits, and bypasses security and data integrity checks.

Answer

Mark all Apex controller methods as global to allow unrestricted LWC access.

Answer

Pass entire sobject records with complex parent relationships directly from client-side JavaScript without validation.

Question 6

A developer is writing a Queueable class that needs to make a callout and also perform a DML operation afterward in the same transaction. Which interface must be added to the Queueable class definition?

Accepted Answer

Database.AllowsCallouts. To make HTTP callouts in Queueable Apex, the class must implement the Database.AllowsCallouts interface.

Answer

Schedulable

Answer

Database.Batchable<SObject>

Answer

InstallHandler

Question 7

Which THREE strategies are recommended for improving the performance of Lightning Web Components rendering large lists of data? Choose 3 answers.

Accepted Answer

Provide a unique, stable 'key' attribute (such as record Id) on each iterated element in for:each loops.. Option B is correct because giving each iterated element a unique, stable key (e.g., the record Id) in for:each loops lets the Lightning Web Components engine's diffing algorithm track items across re-renders and reuse DOM nodes instead of destroying and recreating them, which dramatically reduces rendering work. Option C is correct because pagination, virtual scrolling, or lazy loading limits the number of rows actually rendered in the DOM at any time, so the browser only paints a small window of records rather than the entire dataset, keeping render and layout times low. Option D is correct because getter properties referenced in a template are re-evaluated on every render cycle, so placing heavy computation or data transformation there multiplies the cost across all rows; moving that logic to one-time initialization or cached properties avoids repeated expensive work. Option A is not recommended because synchronous imperative Apex calls block the client thread and, when invoked inside iterators, can fire one call per row, causing severe latency and governor-limit pressure. Option E is incorrect because rendering all 10,000 records at once in a single flat DOM tree creates an enormous DOM, causing slow initial render, sluggish scrolling, and high memory usage, which is exactly the anti-pattern these strategies are meant to avoid.

Answer

Use synchronous imperative Apex calls inside template iterators.

Answer

Render all 10,000 records at once in a single flat DOM tree without pagination.

Question 8

A developer is designing a Lightning Web Component that needs to be conditionally displayed in different Salesforce containers. Which TWO targets are valid entries in the component's js-meta.xml configuration file? (Choose TWO)

Accepted Answer

lightning__HomePage. Option B, lightning__HomePage, is a valid target because it allows the Lightning Web Component to be exposed on the Home page in Lightning Experience, which is one of the supported containers for conditional display. Option E, lightning__RecordPage, is also valid because it lets the component be placed on record pages, another standard Lightning Experience container. The other options are not valid targets: lightning__CustomField, lightning__ApprovalProcess, and lightning__ApexClass are not recognized js-meta.xml targets for exposing an LWC in a Salesforce container. Therefore, only B and E are correct.

Answer

lightning__CustomField

Answer

lightning__ApprovalProcess

Answer

lightning__ApexClass

Question 9

Which THREE of the following items can be viewed in a debug log?

Accepted Answer

Database DML operations. Option A (Database DML operations) is correct because debug logs capture DML statements such as INSERT, UPDATE, DELETE, and UPSERT executed during a transaction, including the affected object and record IDs. Option B (Apex method execution) is correct because debug logs record Apex execution events, including method entry/exit, SOQL/DML statements, and system debug output from Apex classes and triggers. Option E (Workflow rule evaluation) is correct because debug logs include workflow and process automation events, showing when workflow rules are evaluated and whether their criteria are met. Option C (User login credentials) is not included because debug logs never record passwords or authentication secrets, and login activity is tracked through Login History rather than debug logs. Option D (Browser cache contents) is not included because debug logs capture server-side Salesforce execution events, not client-side browser data such as cached files or cookies.

Answer

User login credentials

Answer

Browser cache contents

Question 10

Which TWO statements are true regarding the differences between Aura components and Lightning Web Components (LWC)? (Choose TWO)

Accepted Answer

Lightning Web Components take advantage of native web standards built directly into modern browsers.. Option C is correct because LWC is built on native web standards such as standard JavaScript, HTML templates, and Web Components APIs, so it leverages capabilities already present in modern browsers rather than relying on a proprietary framework layer. Option E is correct because LWC runs on the browser's native engine features (for example, standard DOM APIs and native Shadow DOM), which reduces framework overhead and generally yields better performance than Aura's framework abstractions. Options A, B, and D are not correct: LWC components do contain HTML markup in their templates, LWC is not restricted to desktop (it supports mobile and Salesforce mobile app experiences), and Aura does not use standard Shadow DOM encapsulation—it relies on its own framework-managed encapsulation rather than native Shadow DOM.

Answer

LWC components cannot contain HTML markup tags.

Answer

Aura components are required for all modern mobile app development while LWC is restricted to desktop only.

Answer

Aura components use standard Shadow DOM encapsulation without component-specific framework abstractions.

Question 11

Which TWO actions should a developer take when handling errors returned by an imperative Apex call in a Lightning Web Component? Choose 2 answers.

Accepted Answer

Extract the error message from the error object structure (e.g., error.body.message).. Option B is correct because when an imperative Apex call fails, the promise rejects with a JavaScript error object whose useful details live in nested properties such as error.body.message (and error.body.pageErrors or error.body.fieldErrors), so the developer must extract the message from that structure to surface a meaningful error. Option D is correct because imperative Apex calls return a Promise, so errors must be handled by chaining a .catch() handler or by wrapping the call in try/catch when using async/await; otherwise the rejection is unhandled. Option A is wrong because ApexPages.addMessage() is a server-side Apex method for Visualforce pages, not for Lightning Web Components. Option C is wrong because Apex is not Java and rethrowing as an unhandled Java exception is neither possible nor a valid LWC error-handling pattern. Option E is wrong because window.alert() is a blocking browser dialog and is not the recommended way to present errors in a Lightning Web Component, which should use lightning-toast or inline UI instead.

Answer

Call ApexPages.addMessage() to display the error on screen.

Answer

Rethrow the error as an unhandled Java exception.

Answer

Use standard window.alert() for all error messaging.

Question 12

A developer is troubleshooting lifecycle hooks and rendering behavior in a Lightning Web Component. Which THREE statements are correct regarding LWC lifecycle execution order? (Choose THREE)

Accepted Answer

The constructor() is invoked before the component is inserted into the DOM.. Option A is correct because the constructor() lifecycle hook runs first, during component instantiation, before the element is attached to the DOM, making it the right place for initializing state but not for DOM access. Option C is correct because connectedCallback() fires when the component is inserted into the DOM, which is why it is used for DOM manipulation, subscribing to events, or fetching data. Option D is correct because disconnectedCallback() fires when the component is removed from the DOM, making it the appropriate hook for cleanup such as unsubscribing from events or clearing timers. Option B is incorrect because renderedCallback() runs after every render of the component, not just once, so it can execute multiple times as reactive properties change. Option E is incorrect because renderedCallback() runs after the component is connected and rendered, so it cannot execute before connectedCallback().

Answer

renderedCallback() only executes once during the lifetime of the component.

Answer

renderedCallback() is invoked before connectedCallback().

Question 13

Which TWO tools are effective for monitoring asynchronous Apex jobs?

Accepted Answer

Setup > Apex Jobs. Setup > Apex Jobs (option C) is correct because this Salesforce setup page lists asynchronous Apex jobs—such as Batch Apex, Queueable, future methods, and scheduled jobs—along with their status, submitted time, and completion details, making it a primary monitoring tool. Querying the AsyncApexJob object (option D) is correct because it exposes the same job records via SOQL/SOQL-based tooling, allowing developers to filter by Status, JobType, CreatedDate, and other fields for programmatic or custom monitoring. Option A (Setup > Security) is incorrect because it covers security policies like password and session settings, not job monitoring. Option B (Setup > Debug Logs) is incorrect because debug logs capture execution details for troubleshooting, not the overall status of asynchronous jobs. Option E (Setup > Flows) is incorrect because it manages Flow automation, not Apex asynchronous job execution.

Answer

Setup > Security

Answer

Setup > Debug Logs

Answer

Setup > Flows

Question 14

A developer is implementing error handling for an imperative Apex call in a Lightning Web Component. Which THREE properties or techniques are standard for catching and inspecting errors returned from Apex promises? (Choose THREE)

Accepted Answer

Using a .catch(error => { ... }) block on the returned promise.. Option A is correct because imperative Apex calls return a JavaScript Promise, and attaching a .catch(error => { ... }) handler is the standard way to intercept and inspect a rejected promise when using .then() chaining. Option B is correct because async/await syntax wraps the promise so that a thrown Apex error surfaces as an exception inside a try/catch block, which is the recommended pattern for imperative Apex in LWC. Option E is correct because Apex errors are surfaced to the client as an error object whose body.message property contains the specific message thrown by the Apex method (for example, from AuraHandledException or a DML exception). Option C is incorrect because error.stackTrace is a client-side JavaScript stack trace and cannot roll back server-side database transactions; DML rollback happens automatically on the server when an Apex transaction fails. Option D is incorrect because there is no error.retry() method on Apex error objects, and re-executing a failed database transaction is not an automatic client-side behavior.

Answer

Reading error.stackTrace to automatically rollback database transactions on the client.

Answer

Calling error.retry() to automatically re-execute the failed database transaction.

Question 15

Which TWO primitive data types are natively supported in Apex? Choose 2 options.

Accepted Answer

Integer. Option D (Integer) is correct because Apex natively supports Integer as a 32-bit signed whole-number primitive type, declared directly as 'Integer i = 5;'. Option E (Boolean) is correct because Apex natively supports Boolean as a primitive type holding only true or false, declared as 'Boolean b = true;'. The unmarked options do not belong: Apex has no 'Char' primitive (single characters are handled with the String type), 'Structure' is not an Apex data type (it is a C/C++-style construct), and 'Array' is not a primitive in Apex—ordered collections are created as Lists (e.g., 'List<Integer>'), which are objects rather than primitives.

Answer

Char

Answer

Structure

Answer

Array