Drupal Interview Questions

Here you can find the Interview question for Drupal CMS. These question most likely to asked any interview. I have shared my experience, I have total 3.5 year of experience in drupal and gave almost 10-12 interview on Drupal.

Basic Interview Questions

Question : What is a Content Management System (CMS)?

Answer :  A Content Management System (CMS) allows for full control of editing and organization of a website from a web browser such as Firefox, Chrome, or Internet Explorer, without knowledge of “how to code”. The browser interface is customized to meet a company’s business needs and functionality requirements, to allow non-technical personnel full control of the website. Below is an image displaying the back-end of a CMS.

Common goals in building a website on a CMS platform are:

  • To reduce dependence on developers and other IT resources and put control of a site in the hands of the folks who manage the website’s content (e.g. often the Marketing or Communication Department)
  • True separation of design from content, allowing for display across a wide array of formats including mobile devices and also, periodic graphic updates without having to substantially rework the content
  • WYSIWYG (What you see is what you get) editing. This allows users to edit the website with a mouse through page building wizards (step by step guides), drag and drop, right-click menus, and other non-technical editing tools.
  • Enhanced user experience, with regularly updated, dynamic content and seamless integration with any number of other related systems

Question : What is Drupal ?

Answer : Drupal is a CMS (Content Management System), it is open source software maintained and developed by a community of over 1,000,000 users and developers. It’s distributed under the terms of the GNU General Public License (or “GPL”), which means anyone is free to download it and share it with others.

We can develop any dynamic or static website by setting up Drupal CMS. It was released in 2001 and today is considered to be a leading CMS that is gaining widespread adoption in a variety of industries. It is written in PHP (the same language Mark Zuckerberg chose for Facebook).

SOME SAMPLED DRUPAL SITES


Question : WHAT ARE THE USES OF DRUPAL?

Answer : As stated, due to its flexibility and extensibility, Drupal is not limited to any kind. Browse these lists to see the wide range of things that Drupal can build:

  • Personal or corporate Web sites
  • Community portal sites
  • Intranet/Corporate sites
  • Blogs, art, portfolio, music, multimedia sites
  • Forums
  • International sites (websites with multi languages)
  • E-commerce sites
  • Resource directories
  • Social networking sites

Question : What can Drupal do? And why is it different from other CMS? OR How Does Drupal Compare with Other CMS Options? OR Why Would Drupal be a Good Choice for my Organization?

Answer :  There are many reasons why Drupal is the top three most used CMS, and why tons of small to big complex systems have made it their options. Here are those:

  • Reliability. Drupal is one of the top three most popular content management systems in the world. It has a longstanding history. Though Drupal is a work in progress, it has been stable along the way. We have Drupal 7 now while Drupal 8 is going to be released. But you can be assured that you will be supported for Drupal previous version at least 5 years. Meanwhile, the resources will stay there for goods.
  • Available resources. Nearly anything you want to do with the system has been priorly created and done absolutely well by other people. Other great news is nearly all of the most useful modules (Drupal add-ons) are contributed to the Drupal community. This is invaluable because in many CMS, you have to pay for important features. As a user, you have benefit greatly from someone’s efforts, and experience.
  • A huge dedicated community. The Drupal community is large, dynamic and has functioned well since 2001. As a newbie, or a senior developer, Drupal.org is a must have resources where you dig in for learning material, upcoming news, or ask for support from contributors, and specialists.
  • Robust and convenience. Be assured that the source code for building your Drupal sites has been precisely written, and designed by Drupal experts. When you have an intention to do more complex and advanced work, you will find it easy and convenient to modify the system. This grants users a great advantage over other CMS.
  • Flexibility. It’s not a chance that Drupal is considered the most flexible CMS. We have always thought that if you have an idea about any functions, contents, you can certainly create it with Drupal. Seriously. You can create any content on site. You can customize anything to fit your taste. You can create any website type that you want.
  • Scalability. By scalability, we mean that you can extend your Drupal core to a higher level with a variety of contributed Drupal modules. What’s great with the Drupal modules is that they integrate perfectly well with Drupal core. They also connect absolutely efficiently with the modules. This is regardless of the fact many modules are totally different. It is due to the natural structure & built in system of Drupal. This thereby enhances the power of extending your Drupal website. It is also a core strength of Drupal compared with other CMS. Meanwhile, Drupal is an open source. So suppose the modules you want don’t exist, you can create one, edit an existing module, or hire someone to do the job.
  • Security. Drupal has been meticulously tested up to strict security rules by Drupal experts and contributors. Its built-in security is strong. Drupal will lock down whatever directory installed, rendering important data, configuration files unable to be accessed directly. No wonder that many big sites with extreme security are using Drupal, namely – whitehouse.org, commerce.gov, weforum.org.

Question : What are Some Reasons to Not Choose Drupal? OR When Drupal isn’t right?

Answer :  If it is necessary to know about a system before we set our foot on, it’s never been less important to explore its cons. Here we bring some of our caveats for the system:

  • There’s a little learning curve. You will not learn and work with Drupal in a few days. Accept this fact. It’s harder to start compared with other CMS like WordPress. But once you learn some basic things, it’s easy, and the flow is smoother.
  • It is not for those who have insufficient time to educate themselves about this system, or little money to pay a Drupal developer to carry out the work.
  • Finding a good Drupal developer is harder to find than that of WordPress or other systems. It’s not hard to guess this considering the number of WordPress developers compared with Drupal.

It always takes some investments to learn about something. For a new user, it would be a huge opportunity cost – what you will gain and lose working with one system and leave others behind.
But after all the choice is always yours.We expect it would be worth. The CMS you will spend thousands hours working. The system through this you make a living. The option that yields energy and satisfaction.

OR

Navigating the extensive Drupal collection of community modules, which are the building blocks that allow us to build a great website, requires Drupal experience and know how. As such, it becomes more important than ever before to choose a web partner carefully.

Other reasons to forego Drupal might include:

  • Your team has vast experience in a different product
  • You need to hit the ground running with a new website in less than 2-3 months
  • You’ve observed firsthand Drupal’s out of the box performance and aren’t aware that an experienced firm can equip a Drupal site with virtual rocket boosters

Question : What Else Besides Content Management is Drupal Good For?

Answer : 


Question : How Drupal Works ?

Answer : 

Page Request Process

  1. Someone fires a request to your webserver. They might get a cookie if they’ve already logged into the site.
  2. The server gets the request. It goes to .htaccess which says everything should go to index.php
  3. index.php loads the APIs and gets them ready to handle the request
  4. The Menu API which was loaded looks up the paths that different modules have registered that they handle.
  5. The module gets the request and fires hooks to see whether any module wants to help while it’s building the page.
  6. The module returns some info back to the menu system.
  7. If the everything looks good, it figures out which theme is active and hands off the raw data to the theme layer.
  8. That gets kicked back to Drupal.
  9. That gets kicked back to the web server, which kicks it back to the user.

Question : How you can describe Drupalisms ?

Answer : we can describe drupalisms by the following terms :

Hooks

The hook system is an event listener that was cobbled together out of the function_exists functionality of PHP.

Info Arrays

Drupal uses giant nested arrays to pass information around. You can stick anything in arrays, so you have to look at the API docs to figure out the different structures of the arrays in the APIs.

Callbacks

In an array, you stick a PHP function name in specific places. When the array is being processed, the function will be called.

Renderables

Arrays created by Form API and Node. In Drupal 7, the entire structure of the page is in a renderable. It’s XML as an array. If it doesn’t have a hash sign in front, it is a nested element. If it does have a hash sign, it is a property of its parent element.

Alter Hooks

The payoff for all the crazy array stuff. Drupal asks if anyone wants to change these arrays before they get fully rendered. It allows you to customize the guts of how other modules work without messing with their code.


Question : What are the difference between drupal 6 and 7 ?

Answer : 

Key Difference: Drupal has many versions and is currently running on version 7. Each version aims at making the system more user-friendly and offers various different features that allow the websites to be more dynamic in nature. Drupal version 6 was introduced in February 2008, while Drupal version 7 was introduced in January 2011.

Drupal.org lists the changes made in version 7. The company lists all the changes in the version in the Drupal change log, which can be found on the website.

  • Drupal 7 requires new system requires such as MySQL 5.0.15 or PostgreSQL 8.3, PHP Version 5.2 or higher and PHP Memory of 40M – 64M
  • More secure implementation for scheduled tasks (cron.php)
  • More secure password system
  • More secure log-in system
  • Modules can be updated via the web
  • Administrative links to edit existing page elements on each page
  • Improved support for integration of WYSIWYG editors
  • More drag-and-drop for administrative tasks
  • Permissions now have the ability to handle more meta-data
  • User 1 created as part of the installation process
  • Added features to the default install profile
  • Automated task runs can be set up via configuration
  • Redesigned password strength validator
  • Renamed “input formats” to “text formats”
  • Added support for default text formats to be assigned on a per-role basis
  • Moved text format permissions to the main permissions page
  • Added “vertical tabs”
  • Improved time zone support
  • Removed per-user themes
  • Added new “Shortcuts” module
  • Added query builders for INSERT, UPDATE, DELETE, MERGE, and SELECT queries
  • Support for master/slave replication, transactions, multi-insert queries,delayed inserts, and other features
  • Added support for the SQLite database engine
  • Default to InnoDB engine, rather than MyISAM, on MySQL when available for greater scalability and data integrity
  • Hook API documentation included in Drupal core
  • Added OPML import functionality for RSS feeds
  • Added feed update options
  • Added support for language-aware searches
  • Added test framework and tests
  • Remove some themes and added other themes as default on user and admin interface
  • Files are now first class Drupal objects with file_load(), file_save(), and file_validate() functions and corresponding hooks.
  • Files use PHP stream wrappers to enable support for both public and private files and to support pluggable storage mechanisms and access to remote resources
  • Added a field specifically for uploading files
  • Improved image handling
  • Added a field specifically for uploading images
  • Better Support for Multisite Installations
  • Added RDF support
  • Better support for search engine optimization and web linking
  • Added ability to add custom fields
  • Installer can be run from the command line
  • Upgrades made to core JavaScript library, JQuery Forms library
  • Added jQuery UI 1.8
  • Improved node access control system
  • Improved handling of long-running tasks