Lightning Interview QA

Lightning FAQ
Lightning FAQ


  1. What is Lightning ?
Lightning is the collection of tools and technologies behind a significant upgrade to the Salesforce platform. Lightning includes:
  • Experience: A set of modern user interfaces optimized for speed. This includes the Lightning Experience, Salesforce1 Mobile app and template-based communities.
  • Lightning Component Framework: A JavaScript framework and set of standard components that allow you to build reusable components to customize the Lightning Experience, Salesforce1 Mobile app and template-based communities and build your own standalone apps.
  • Visual Building Tools: Drag-and-drop technologies for fast and easy app building & customization’s. Use the Lightning App Builder to customize the Lightning Experience and Salesforce1 Mobile app. Use the Community Builder to customize template-based communities.
  • Lightning Exchange: A section of the AppExchange where you can find 70+ partner components to jump-start your development.
  • Lightning Design System: Style guides and modern enterprise UX best practices to build pixel perfect apps that match the look and feel of the Lightning Experience and Salesforce1 Mobile app.

2. How can we use Lightning Components with the Salesforce1 Mobile App ?

By Create a custom Lightning tab that points to our component and include that tab in our Salesforce1 Mobile navigation.

3. Can we make a Lightning Component that shows up in both the mobile and the desktop user interfaces ?

 We can use Lightning Components directly in Lightning Experience, the Salesforce1 Mobile app, template-based communities, and custom standalone apps. Additionally, we can include Lightning components in a Visualforce page, that allowing us to use them in Salesforce Classic, Console, and Visualforce-based communities.

4. Is Lightning an MVC framework ?

No, it’s a component-based framework.

5. Which parts of Lightning Components are server-side and which are client-side ?

Lightning Components are use JavaScript on the client side and Apex on the server side.

6. Can we make one component inherit styles/CSS from a parent component, or must we always define it in the component ?

Yes, we can inherit styles from parent. there is no need to always defined in the component.

7. What is the use of the aura:method tag in Lightning ?

we can Use < aura:method > to define a method as part of a component’s API. This enables us to directly call a method in a component’s client-side controller instead of firing and handling a component event. Using simplifies the code needed for a parent component to call a method on a child component that it contains.

8. Can we Include One component to another ?

Yes, we can Include one lightning component to another lightning component

9. Is there any limit on how many component to have in one Application ?

there is no limit.

10. Is Lightning Components replacing Visualforce ? 


11. What is Aura? Why do we use the aura: namespace in the code ?

Aura is the open source technology that powers Lightning Components. The aura: namespace contains all of the basic building blocks for defining components and applications.

12. Do we need a namespace to develop Lightning Components ?

No. Lightning Components used to require a namespace, but that is no longer a requirement.

13.What are the tools included in lightning ?

  •  Lightning Component Framework – Components and extensions that allow you to build reusable components, customize the Salesforce1 Mobile App, and build standalone apps.
  • Lightning App Builder – A new UI tool that lets you build apps lightning fast, using components provided by Salesforce and platform developers.
  • Lightning Connect – An integration tool that makes it easier for your app to consume data from any external source that conforms to the OData spec.
  • Lightning Process Builder – A UI tool for visualizing and creating automated business processes.
  • Lightning Schema Builder – A UI tool for viewing and creating objects, fields, and relationships.

14.What is difference between Visualforce Components and Lightning Components ?

Visualforce components are page-centric and most of the work is done on the server. Lightning is designed from the component up, rather than having the concept of a page as its fundamental unit. Lightning Components are client-side centric, which makes them more dynamic and mobile friendly.

15. Does Lightning work with Visualforce ?

yes Lightning work with Visualforce.

16.Are there any CSS (styles) provided by as part of the supported Lightning Components ?

Yes. Salesforce Lightning Design System.

17. Are Lightning Components intended only for mobile apps ?

Components have been built to be mobile first, but with responsive design in mind. With Lightning we can build responsive apps fast for desktop, mobile and tablets.

18. What are the advantages of lightning ?

The benefits include an out-of-the-box set of components, event-driven architecture, and a framework optimized for performance.

  • Out-of-the-Box Component Set -: Comes with an out-of-the-box set of components to kick start building apps. You don’t have to spend your time optimizing your apps for different devices as the components take care of that for you.
  •  Rich component ecosystem-: Create business-ready components and make them available in Salesforce1, Lightning Experience, and Communities.
  • Performance – :Uses a stateful client and stateless server architecture that relies on JavaScript on the client side to manage UI, It intelligently utilizes your server, browser, devices, and network so you can focus on the logic and interactions of your apps.
  • Event-driven architecture -: event-driven architecture for better decoupling between components
  • Faster development – : Empowers teams to work faster with out-of-the-box components that function seamlessly with desktop and mobile devices.
  • Device-aware and cross browser compatibility – : responsive design,supports the latest in browser technology such as HTML5, CSS3, and touch events.

 19. Can we integrate Lightning components with another framework, such as Angular?

Yes. we can include the working 3rd party code inside a Visualforce Page, embed the Visualforce Page inside a Lightning Component. This Lightning Component can be used as any other Lightning Component in various environments.

20. Can we include external JavaScript/CSS libraries in components ?

Yes ! we can use multiple libraries in our lightning component like JQuery, Bootstrap, custom CSS and custom Javascript libraries from a local resource (static resource).

21. What happens with existing Visualforce Pages in Lightning Experience ?

They’ll continue to be supported in the current UI and Lightning Experience.

22. Where we can display lightning component ?

There are a number of possibilities for display lightning component..

  •  Lightning Experience: We can display component in the Lightning Experience using the App Builder.we can edit the home page, edit a record detail page or create/edit a new app page to include it.
  •  Salesforce1 Mobile app: We can display component in the Salesforce1 Mobile app by creating a custom Lightning tab that references it and adding that tab in mobile navigation.
  • Template-based community: we can display component in template-based (e.g. Napili) community using the Community Builder.
  • Standalone Lightning app: By create a standalone Lightning app (e.g. and include component in this app. Access Lightning app by URL.

23. Do I always create an app bundle first when develop lightning component ?

Not necessarily, We can start with a Component bundle.

24. How can we  deploy components to production org ?

we can deploy component by using managed packages, IDE, Migration Tool or Change Sets.

25. What is Lightning Experience?

Lightning Experience is the name for the all new Salesforce desktop app, with over 25 new features, built with a modern user interface and optimized for speed.

more QA update soon….. 🙂

Like our facebook page for new post updates. 🙂

(Visited 13,339 times, 37 visits today)