SALESFORCE-PD1 User Interface Practice Test 8 — 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 troubleshooting an issue where a Lightning Web Component is not picking up changes to the internal fields of an object property. What is the cause of this behavior in LWC reactivity?

Accepted Answer

LWC reactivity is shallow, so nested object property mutations require creating a new object reference or using @track.. LWC reactivity is shallow: the framework tracks assignments to the property itself, not mutations to nested fields. Changing obj.field does not trigger re-render because the object reference is unchanged. To make nested changes reactive, reassign the property with a new object (e.g., this.obj = {...this.obj, field: value}) or decorate the property with @track.

Answer

Reactive properties must be declared as constants using const instead of let.

Answer

The component must be wrapped in an Aura container to enable deep object tracking.

Answer

LWC does not support objects as reactive properties under any circumstances.

Question 3

A developer is writing a Visualforce page that uses a custom controller. The page needs to execute an action method as soon as the page loads, without requiring user interaction. Which attribute on <apex:page> should be used?

Accepted Answer

action="{!init}". The `action` attribute on `<apex:page>` specifies a controller method that is executed when the page loads, before rendering, without user interaction. It is the standard Visualforce mechanism for initialization logic, such as loading data or setting up state. The correct syntax is `action="{!init}"`, where `init` is a public method in the custom controller.

Answer

initMethod="{!init}"

Answer

onLoad="{!init}"

Answer

loadAction="{!init}"

Question 4

A developer is implementing navigation in a Lightning Experience app using the NavigationMixin service in a Lightning Web Component. The developer wants to navigate to a standard ListView for the Account object. What is the correct type to specify?

Accepted Answer

type: 'standard__objectPage', attributes: { objectApiName: 'Account', actionName: 'list' }. NavigationMixin.Navigate uses standard page references where type is 'standard__objectPage' and actionName is 'list'.

Answer

type: 'standard__webPage', attributes: { url: '/lightning/o/Account/list' }

Answer

type: 'standard__recordPage', attributes: { objectApiName: 'Account', actionName: 'view' }

Answer

type: 'standard__namedPage', attributes: { pageName: 'accountList' }

Question 5

A developer needs to create a Lightning Web Component configuration file. What is the required file extension and naming convention?

Accepted Answer

componentName.js-meta.xml. The Lightning Web Component configuration file must be named `componentName.js-meta.xml` — the component's base name followed by `.js-meta.xml`. This file defines the component's metadata, including its API version, targets, and exposed properties, and the naming convention is mandatory for the framework to recognize it.

Answer

componentName.cmp-meta.xml

Answer

componentName.xml

Answer

componentName.config.xml

Question 6

A developer is building a Lightning Web Component and wants to iterate over a list of items in the HTML template. Which directive should be used?

Accepted Answer

<template for:each={items} for:item="item">. In LWC templates, iteration is performed with the for:each directive: <template for:each={items} for:item="item">. This is the standard LWC syntax for rendering a list, and it requires a for:item attribute to name the current item (and optionally for:index for the index). It is the only correct directive among the options for LWC.

Answer

Answer

<aura:iteration items="{!v.items}" var="item">

Answer

<apex:repeat value="{!items}" var="item">

Question 7

A developer is creating a Lightning Web Component that needs to interact with Salesforce data using Lightning Data Service. Which TWO wire adapters are natively available in the @salesforce/apex or lightning/ui* modules for basic record operations? (Choose TWO)

Accepted Answer

getRecordUi from 'lightning/uiRecordApi'. Option B, getRecordUi from 'lightning/uiRecordApi', is correct because it is a native Lightning Data Service wire adapter that retrieves record layout, metadata, and field data for one or more records, commonly used with User Interface API responses. Option C, getRecord from 'lightning/uiRecordApi', is also correct because it is the standard Lightning Data Service wire adapter for fetching a single record's fields by record ID and fields, without writing Apex. The other options are not valid native wire adapters: getAccountList from 'lightning/accountApi' does not exist, fetchRecord from 'lightning/recordStore' is not a Salesforce module, and queryDatabase from 'lightning/database' is not a Lightning Data Service adapter.

Answer

getAccountList from 'lightning/accountApi'

Answer

fetchRecord from 'lightning/recordStore'

Answer

queryDatabase from 'lightning/database'

Question 8

A developer is implementing communication in Lightning Web Components. Which TWO mechanisms are valid for passing data or messages between components? (Choose TWO)

Accepted Answer

Dispatching and listening to CustomEvent instances in parent-child hierarchies.. Option B is correct because in Lightning Web Components, a child component can dispatch a CustomEvent (via this.dispatchEvent(new CustomEvent(...))) that bubbles up the DOM, and a parent component can listen for it using an event handler in its template or with addEventListener, making it the standard mechanism for child-to-parent communication. Option E is correct because Lightning Message Service (LMS) provides a publish-subscribe API (lightning/messageService with publish() and subscribe()) that lets components communicate across the DOM—including between unrelated components, across different component trees, and even with Aura components—by publishing to a message channel. Option A is not valid because a component cannot directly reach into a sibling component's properties; siblings have no direct reference to each other and must communicate through a common parent or a message service. Option C is not valid because $A.get('e.force:event') is an Aura framework API for application events, and LWC does not support Aura application events; LWC uses CustomEvent or LMS instead. Option D is not valid because LWC components run in a secure, encapsulated environment (Lightning Web Security/synthetic shadow DOM) and sharing state through global window variables is an anti-pattern that breaks encapsulation and is not a supported communication mechanism.

Answer

Directly assigning properties on child components from sibling components.

Answer

Using application events via $A.get('e.force:event') in LWC.

Answer

Modifying global window variables shared across component scopes.

Question 9

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 10

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 11

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 12

A developer is creating an Aura component that interacts with Salesforce data. Which TWO tags or features are valid in the Aura framework? (Choose TWO)

Accepted Answer

. Option A is correct because is a core Aura framework tag used to iterate over a collection such as v.items, rendering the body once per element with the specified var attribute. Option C is correct because is the standard Aura tag for declaring a component attribute, with name and type (e.g., String) being valid attributes. Option B is not valid Aura syntax; for:each and for:item are Lightning Web Components template directives, not Aura tags. Option D is not valid; lwc:databind is not an Aura or LWC feature, and Aura uses {!v.val} expressions without such a tag. Option E is not valid in an Aura component because import { LightningElement } from 'lwc' is the LWC base class import, used in JavaScript files of Lightning Web Components, not Aura.

Answer

Answer

<lwc:databind property="{!v.val}" />

Answer

import { LightningElement } from 'lwc';

Question 13

Which TWO features are provided out-of-the-box by Visualforce when building standard user interfaces? (Choose TWO)

Accepted Answer

Automatic enforcement of CRUD and FLS when using standard controllers.. Option C is correct because Visualforce standard controllers and standard list controllers automatically enforce object-level CRUD permissions and field-level security (FLS) for the running user, so developers get secure data access without writing manual permission checks. Option E is correct because Visualforce automatically maintains the view state (the encrypted, serialized page state stored in the __VIEWSTATE hidden field) across postbacks, preserving form input and component state during form submission and page navigation. Options A, B, and D are not Visualforce out-of-the-box features: Visualforce does not provide client-side reactive shadow DOM encapsulation, it does not compile TypeScript into native browser bytecode (it renders HTML/CSS/JS server-side), and it does not offer real-time bidirectional WebSocket synchronization across browser tabs.

Answer

Client-side reactive shadow DOM encapsulation.

Answer

Automatic compilation of TypeScript into native browser bytecode.

Answer

Real-time bidirectional WebSocket synchronization across all connected browser tabs.

Question 14

Which TWO tools or environments are officially supported for developing Lightning Web Components? (Choose TWO)

Accepted Answer

Visual Studio Code with the Salesforce Extension Pack. Option B is correct because Salesforce officially supports developing Lightning Web Components in Visual Studio Code using the Salesforce Extension Pack, which provides LWC-specific tooling such as syntax highlighting, code completion, and the ability to deploy and retrieve components to and from an org. Option D is correct because the Salesforce CLI (sfdx/sf) is the officially supported command-line environment for scaffolding, building, testing, and deploying LWC source, and it underpins the VS Code extensions and CI/CD workflows. The remaining options do not belong: Microsoft FrontPage 2003 (A), Eclipse with the legacy Force.com IDE v1 plugin (C), and Dreamweaver MX with custom snippets (E) are obsolete or unrelated web-authoring tools that have no official Salesforce support for LWC development.

Answer

Microsoft FrontPage 2003

Answer

Eclipse IDE with the Force.com IDE v1 plugin

Answer

Dreamweaver MX with custom snippet extensions

Question 15

A developer is working with component styling and design tokens in Lightning Web Components. Which TWO practices apply when working with SLDS styling in LWC? (Choose TWO)

Accepted Answer

Prefer standard SLDS utility classes over custom hardcoded CSS rules for padding and margins.. Option B is correct because SLDS provides utility classes (such as slds-m-around_medium and slds-p-horizontal_small) that implement the design system's spacing scale consistently, so using them instead of hardcoded padding/margin values keeps components aligned with SLDS and themeable. Option E is correct because LWC exposes SLDS design tokens as CSS custom properties (for example var(--lwc-spacingMedium) or var(--lwc-colorBrand)), letting styles reference the design system's values and adapt to theming rather than duplicating literal values. Option A is wrong because sprinkling !important everywhere is an anti-pattern that fights LWC's style encapsulation and makes styles brittle; encapsulation is handled by scoping, not by !important. Option C is wrong because global stylesheets loaded via <link> in static resources are not the recommended way to style LWC components, which rely on component-scoped CSS files. Option D is wrong because shadow DOM styles cannot be overridden from a parent component's CSS without using supported styling hooks (::part or CSS custom properties), so directly reaching into shadow DOM is not a valid practice.

Answer

Use the !important declaration on every CSS rule to bypass Salesforce CSS encapsulation.

Answer

Write global CSS stylesheets in static resources and include them in every component using standard HTML <link> tags.

Answer

Override component-internal shadow DOM styles from a parent component's CSS file without styling hooks.