CCNA User Interface Questions

This snippet correctly uses the NavigationMixin.Navigate method with a page reference object. The type 'standard__recordPage' is used to navigate to a record page, and the attributes specify the recordId, objectApiName, and actionName. This is the standard way to navigate to a record page in LWC using NavigationMixin.

Lightning Out is the supported way to render an LWC inside a Visualforce page. A dependency app exposes the component, the VF page uses $Lightning.use and $Lightning.createComponent to instantiate it, attributes pass the parameter in, and an event handler registered during creation receives events the LWC fires. This accurately matches the required inbound parameter and outbound event pattern for VF-to-LWC integration.

NavigationMixin adds a navigate method to the component. Passing a page reference with type standard__recordPage and the recordId attribute directs the user to the record's page in Lightning Experience. This is the supported way to perform client-side navigation from an LWC without a full page reload, and it works across Lightning Experience and the Salesforce mobile app.

The ShowToastEvent module is imported from lightning/platformShowToastEvent. Creating a new instance with title, message, and variant properties and dispatching it via this.dispatchEvent displays a toast in Lightning Experience and the Salesforce mobile app. This is the standard, supported way to show toasts from an LWC.

NavigationMixin from lightning/navigation provides client-side navigation in LWC. Extending the class with it and calling this[NavigationMixin.Navigate] with a page reference of type standard__recordPage and the record's Id navigates to the record detail page without a full page reload. This is the documented, supported pattern for this exact requirement.

In LWC, the main JavaScript file of a component must have the exact same name as the folder it resides in. If the folder is named 'utils', the framework expects a file named 'utils.js'. If the file is named differently, the 'c/utils' import path will fail to resolve during the compilation process.

When an Aura parent supplies attributes to a Lightning Web Component, those values are applied after the component is constructed, so reading the @api property inside the constructor returns undefined. The developer should read the value in a lifecycle hook such as connectedCallback or renderedCallback, or use a setter, to observe the value reliably.

The @AuraEnabled decorator is used on Apex methods to expose them to Lightning Web Components and Aura components. When applied to a static method, it makes the method available for invocation from the client-side JavaScript. For LWC, the method must be static and can be called using the wire service or imperatively. This is the standard way to call Apex from LWC. Without @AuraEnabled, the method cannot be called from the component.

Methods marked with @AuraEnabled(cacheable=true) are executed in a read-only context and are subject to restrictions that prevent DML and callouts. Attempting a callout from a cacheable method throws an error. Removing cacheable=true or separating the callout into a non-cacheable method allows the callout to execute, though it loses the client-side caching benefit.

The getRecord wire adapter is built on Lightning Data Service, which maintains a client-side cache. If any other component updates the Opportunity record using LDS, the wire service automatically triggers a refresh for all components observing that record, ensuring data consistency across the UI without requiring custom refresh logic.

To invoke a public method on a Lightning Web Component from an Aura component, you use the call() method on the found element with the method name as a string. This is the documented interop pattern. Arguments would be passed as a second parameter object if the LWC method accepted them.

Debouncing delays the Apex call until a period of inactivity has passed after the last keystroke. This reduces the number of calls to one per pause, which is the standard technique for limiting server calls in LWC. It is the correct approach because it controls the timing of imperative Apex calls.

Virtual scrolling keeps the DOM lightweight by rendering just a fraction of the total dataset at any given time, preventing browser lag and memory exhaustion when handling tens of thousands of records in a single table.

relatedListId is required to specify the API name of the related list, such as 'Contacts' for the Contacts related list on Account. This tells the adapter which related list to query. Without it, the adapter does not know which child relationship to traverse. The developer must provide the correct related list API name to retrieve the Contacts.

The transient keyword prevents a variable from being included in the Visualforce view state. This is highly effective for large collections or temporary data that only needs to exist during the current request. By reducing the view state size, the developer decreases the payload sent over the network.

The standard__recordPage page reference navigates to a record's detail page and accepts recordId and actionName attributes. Setting actionName to 'view' opens the record in view mode. After creating the record, the developer can pass the returned record ID to this page reference to navigate the user directly to the new record, which is the standard pattern for post-creation navigation.

The @api decorator exposes a class member as part of the component's public API. When a method is decorated with @api, the Lightning Web Component framework registers it so that parents, including Aura components, can invoke it through the element reference. Without this decorator the method remains private and is not addressable from outside the component, regardless of how the parent tries to call it.

The @salesforce/i18n module provides access to locale-specific settings such as currency codes, date formats, and time zones. By importing these values, developers can use standard JavaScript Intl objects or framework utilities to format data correctly for every user, regardless of their geographical location or language settings.

lightning/i18n exposes formatNumber, which formats values according to the running user's Salesforce locale. This keeps the displayed total aligned with the user's language and region settings and matches how Salesforce formats numbers elsewhere. Using it avoids browser-locale drift and keeps formatting consistent across the org's users regardless of their OS or browser settings.

Imperative Apex calls return a Promise, so .then() receives the resolved wrapper, letting the developer check the success Boolean before showing the success toast. .catch() receives server-side Apex exceptions, enabling a distinct error toast. This separation correctly distinguishes a business-level failure (success false) from a runtime exception, satisfying the requirement that the toast appears only when the save truly succeeded.

The getRecord wire adapter from lightning/uiRecordApi subscribes to the Lightning Data Service record stream. When wired with @wire using the recordId, any record change made elsewhere on the page or by other components invalidates the cache and re-delivers data, so the component refreshes automatically. This is the documented pattern for displaying record fields reactively without writing Apex.

Setting `composed: true` allows the event to cross shadow DOM boundaries, while `bubbles: true` propagates it up through the containment hierarchy. Together they satisfy the stem's requirement that the event traverse shadow boundaries without stopping, reaching the parent component regardless of nesting depth.

When a Lightning Web Component is placed on a record page, the platform automatically populates the @api recordId property with the id of the record being viewed. No query or Apex is needed. This is the documented, supported way to obtain the current record id in an LWC.

This import correctly brings the ShowToastEvent class from the lightning/platformShowToastEvent module. In LWC, the module name is 'lightning/platformShowToastEvent' and the named export is ShowToastEvent. Using this import, the developer can create a new ShowToastEvent with parameters like title, message, and variant, then dispatch it via this.dispatchEvent. This is the standard way to show toast notifications in Lightning Experience.

@api is the decorator that makes a property or method part of the component's public API. A parent can set an @api property either declaratively as an attribute in the template or imperatively on the element reference in JavaScript. This is the documented mechanism for exposing data and behavior from a child to its parent, so it directly satisfies the reusable-component requirement.

This configuration correctly identifies the Record Page as a valid target for the component. By further specifying the Account and Contact objects within the targetConfig section, the developer ensures that the component only appears in the App Builder palette when those specific record types are being edited.

Lightning Web Components display toasts by dispatching a ShowToastEvent, which is imported from the lightning/platformShowToastEvent module. This module is the standard, supported way to show a toast from an LWC, and it works consistently in Lightning Experience on desktop and in the Salesforce mobile app, which matches the cross-platform requirement in this scenario.

In Lightning Web Components, event handlers are bound using the onclick attribute without parentheses or the event object. The framework automatically passes the event as the first argument to the handler. The handler can then access event.target. This is the standard and correct syntax for binding a click handler in LWC.

@api exposes a property as public, allowing parent components—including Aura components—to set it via an attribute in markup or programmatically. When an Aura component nests an LWC, the attribute name maps to the public property. This is the documented way to pass data from Aura to LWC and is required for the record ID to be available in the child.

Combining bubbles and composed properties ensures the event travels up the DOM and successfully exits the shadow DOM boundary. This is the standard approach for bubbling events to ancestors that are not direct parents, allowing the event to reach the document root or any listener registered on higher-level components.

The browser's postMessage API is the standard way for an iframe and its host to exchange data across origins. Listening for the message event on window and verifying event.origin against the trusted external domain prevents malicious pages from injecting forged messages. This is the secure, supported pattern for cross-origin communication with an embedded external application.

In Lightning Web Components, public properties and methods are exposed by decorating them with @api. When an Aura component contains an LWC, the Aura component can call the LWC's public method through the element reference. This is the documented interop pattern for Aura-to-LWC communication, so annotating the method with @api is the correct approach.

lightning-formatted-phone is purpose-built to display phone numbers with standard formatting and renders the value as a clickable tel link. It accepts a value attribute and applies consistent presentation, which is exactly what the scenario requires for a read-only formatted phone number on a record page.

The lightning/navigation module provides NavigationMixin, which enables Lightning Web Components to navigate to various page types such as record pages, list views, and named pages. By mixing NavigationMixin into the component class and calling this[NavigationMixin.Navigate] with the appropriate page reference, the developer can redirect the user after the DML operation completes.

Intl.DateTimeFormat is a standard JavaScript constructor that enables locale-aware date and time formatting. It is fully supported in LWC and allows developers to pass options such as 'timeZone' and 'locale' to produce strings that are correctly formatted for the user's specific regional settings.

Using SLDS utility classes on semantic anchor elements gives the visual styling the design system defines while preserving native link semantics that assistive technology understands. Adding aria-current marks the active item so screen readers announce it correctly. This combination keeps markup semantic, follows SLDS conventions, and meets the accessibility requirement without custom CSS or non-semantic elements.

This code correctly creates a new ShowToastEvent with the required parameters: title, message, and variant. The variant 'success' displays a green success toast. Dispatching the event on the component instance using this.dispatchEvent is the standard way to show a toast in LWC. This is the correct and complete syntax.

A template reference obtained with querySelector returns the child custom element, and public methods decorated with @api are exposed directly on that element instance. Calling refreshData() on it invokes the child's public method. This is the documented pattern for parent-to-child imperative communication in Lightning Web Components when no reactive property change is involved.

The pattern attribute on lightning-input accepts a regular expression string that the input value must match. When the form is submitted, the browser's native constraint validation API checks the value against the pattern. If it does not match, the input is marked invalid and the form submission is blocked. This provides a simple way to enforce custom validation without writing extra JavaScript. The pattern attribute works with the standard HTML pattern attribute semantics.