Answer:- Following are the component bundles of the Lightning components: Controller: It handles the client-side events Documentation: This component bundle is used for recording the component’s use Style: It includes component style Renderer: It contains a component default rendering behavior Helper: General logic can be written in this component bundle used by different controller methods to avoid repetition

Answer:- Lightning Components can be used with the Salesforce1 mobile app by creating a traditional Lightning tab that refers to the component. That tab can be added to the Salesforce1 mobile navigation.

Answer:- Record page, App page, and Homepage are the different types of Lightning record pages and they can be built using Lightning App Builder.

Answer:- Lightning out is used if a component has to be used on the external site. The advantage is that Lightning components can be utilized in a visual force page. It acts as a bridge to surface Lightning components in any remote web container.

Answer:- Using Lightning Out can help embed the Lightning component on the VisualForce page. It can be achieved in three steps: 1. The Lightning components for the javascript library of visual force must be first inserted into the intended visual force page through the tag. 2. A Lightning app that is used for the component dependencies is then generated and pointed. 3. Finally, a javascript function needs to be written that creates the component over the page through $Lightning.createComponent().

Answer:- Component event is used for interaction between the parent and child. The change in the child component can be communicated to the parent component through the component event. Application events are used to send modifications in the component to a wide audience. The components that have registered for this event will get an alert.

Answer:- The Namespace is used to group components together and can be created through an organization. The Lightning components are a part of a namespace. C is the default namespace. If the namespace is created for an organization, then that namespace can be used for the Lightning components.

Answer:- Lightning components can be used in the following places: Dragging and dropping them in the community builder and Lightning App Builder Adding it to the Lightning pages Starting it as a quick action Creating stand-alone applications

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.