Answer:- Component events act as a means of communication between a parent and a child. A change in the child component can be communicated to the parent component using Component Events. Application Events communicate changes in the component to a much bigger audience. All the components that have registered for the event get notified about the change.

Answer:- • Salesforce Lightning provides an enhanced user interface. • You need to hire a Salesforce Developer to operate Salesforce Classic, while Salesforce Lightning is much easier to work with. • With Lightning, you don’t need Visualforce for every task. • Salesforce Lightning has advanced security features than Salesforce Classic. • Lightning provides Einstein (Wave) Analytics Reporting to its users. A feature that is missing from Classic.

Answer:- Components events are the events that child components dismiss, and parent components handle. Component events are used when a value from the child component needs to be sent to the parent component.

Answer:- The application events can be dismissed and handled by any component. It does not require any type of relationship among the components. These components should be a part of one application.

Answer:- 1. Capture Phase 2. Default Phase 3. Bubble Phase

Answer:- The Lightning App Builder is a click-and-point tool used for creating Lightning pages for mobile applications and the Salesforce Lightning Experience. The Lightning pages are built through the Lightning components that are configurable, reusable, and compact. The Lightning App Builder can help build a home page, app page, and record page.

Answer:- Unbound and bound expressions are used to perform data binding. When a child component is called from the parent component, the value can be sent from the attribute of a parent component to a child component attribute.

Answer:- The following attributes are used for storing values: • Boolean • Integer • String • Datetime • Date • Decimal • Map • Set

Answer:- The aura: method is used for defining the method within the API of the component. This allows a method to be directly called in the client-side controller of a component instead of handling or dismissing an event. The can help simplify the code that the parent component requires to call a method on the child component.

Answer:- The force: record data is a conventional controller of the Lightning component. Operations like deleting, creating, and editing a record can be accomplished through force: record data. It removes and recognizes the replicate request passing to the server if the same record data is requested.

Answer:- Lightning: navigation is used to navigate to a page reference or create a URL from the given page reference. For navigating, the page reference object must be defined. Navigation is possible for the following supported features: • Lightning Component • Record Page • Object Page • Named Page • Web Page • Knowledge Article • Record Relationship Page • Navigation Item Page

Answer:- The metadata related to a Lightning page is portrayed by FlexiPage. The Lightning page portrays an adaptive screen that is made up of regions that include the Lightning components. The Lightning page includes 25 components. The Flexi page is stored as an XML file, and deployed through a deployment tool or Salesforce metadata API. The Lightning pages are referred to as Flexipages in the API.

Answer:- The Lightning Locker service is a robust and powerful security architecture for the Lightning components. It enhances security by isolating Lightning components that belong to one namespace from those in a different namespace. It promotes best practices thus, enhancing the supportability of the code by only allowing access to supported APIs and removing access from non-published framework internals.

Answer:- Implements are used for referring to the platform interfaces that allow usage of the components in various contexts or grant access to additional context data. A component can use multiple interfaces with the help of implements.