Showing posts with label drupal technical. Show all posts
Showing posts with label drupal technical. Show all posts

Friday, April 25, 2014

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.

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.


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.