Drupal Job Interview Questions and Answers ( a set of 50 questions, q52-q101)

101. What hardware does Drupal.org run on?

People often wonder what kind of hardware drupal.org runs on. Throughout the project history this has been a tough question. For a while it was a server in a random office building. That server eventually died and required a fund-raising effort to replace (the funds were raised in 24 hours!).

The critical infrastructure is all configured to share the load and be redundant. For example, db1 and db2 are configured to be master-slave most of the time to provide for better performance and allow the slave to be promoted to master if the master fails.

Read More here https://drupal.org/node/1280436

100. Drupal and Working with JavaScript

Drupal provides methods for implementing JavaScript. Using these methods will help to keep your code clean and to ensure compatibility with the way other modules implement JavaScript.

A couple of simple principles guide Drupal's JavaScript approach:

· All pages should be perfectly functional without scripts. JavaScript provides alternatives or supplements - not replacements - for standard elements.

No JavaScript is hard-coded into pages. Rather, actions are attached dynamically to page elements--and only if the needed JavaScript support is present.

Read more here https://drupal.org/node/121997

99. Why does Drupal need a database? What databases are supported?

Drupal stores its information - the individual pages, the registered users, and so on - in the database. The database forms the back-end for your Drupal site. At this time, Drupal supports MySQL (or an equivalent such as MariaDB), PostgreSQL, and in Drupal 7, SQLite.

98. How to create a static archive of a Drupal website

Read Here https://drupal.org/node/27882

97. Programming best practices and CMS(drupal) best practices

Programming best practices

https://drupal.org/node/287350

Best practices (drupal)

https://drupal.org/best-practices

96. what are Drupal Distributions and Drupal installation profiles and what is the difference between the two

· Installation profiles are what a developer creates as the basis of distributions. They define installation steps (such as enabling modules, defining content types, etc.) that run after Drupal's base installation when you first install Drupal. One or more standard installation profiles are included in the Drupal Core download; developers can create custom profiles that set up Drupal for specific purposes, and optionally release them for community use on Drupal.org. It is not always easy to attempt to use an installation profile directly, if it requires non-core modules, themes, or libraries -- you would have to locate and download all the required components yourself before you could install Drupal. Instead, it's a lot easier to download a full distribution (if available).

· Distributions are full copies of Drupal that include Drupal Core, along with additional software such as themes, modules, libraries, and installation profiles. The automatic packaging scripts on Drupal.org turn installation profiles into distributions, by gathering all the modules, themes, and libraries they require into a single zip archive, so that all you need to do is download the full archive and run the install script.

When to use distributions

There are no hard and fast rules about when to use distributions, but here are a few guidelines:

· Evaluating Drupal: If you're just getting started with Drupal it makes sense to try a distribution, since they are easier to setup and you can see real life examples of what Drupal can do. Not all distributions are equal though, so start with a popular well maintained distribution.

· Demoing Drupal: Before building a site for someone it can be useful to show them examples of how Drupal can be configured.

· Learning Drupal: In the administration section of a distribution, you can study the inner workings of a real example of Drupal site, learn all the details about how it is built and configured to obtain specific functionality, experiment with any changes and additional modules and themes, etc.

· Quickly building a site: If you're building a site similar to one provided by a distribution it makes sense to start with a distribution. After installing you can continue to configure the site, add modules, create themes, etc. You can even undo things that the installation profile script may have done. If you're changing too much though it may make more sense to just start with stock Drupal and build from there, rather than try to undo and change what was setup for you.

Read Full article here https://drupal.org/node/1089736

2. Containing the phrase

3. Containing none of the words
And users can choose the search criteria if they are not able to find what they want from basic search.

Friday, April 25, 2014