Ruby on Rails Interview Questions

• Model (active record): all the data logic is handled by this model which in rails is known as the active record library. It acts a bridge between the ruby program code and the main database.
• View (action view): the end user sees the view part of the application.
• Controller (action controller): it acts as a data broker of an application. It also helps in handling the logic which allows the model and view to communicate with one another.

This is how the model view controller framework used in ruby on rails.

• Before filters: these filters are executed before the execution of the code in the action controller.
• After filters: these filters are executed after the execution of the code in the action controller.
• Around filters: these are executed both before and after the execution of the code present in the action controller.

• Variables– it is used for the declaration of variables in which all the letters should be in lowercase and the words should be separated by underscore.
• Class and module– a class is declared which encapsulates every function. The class or module name can be written in mixed case and no underscores are used. Every word should start with an uppercase letter.
• Database table– a table is made for storing the data. It is the same as the naming conventions for variables.
• Model– mixed case is used and have singular with table name.
• Controller– names are represented in plural form.

• It helps in creating the table for the database.
• Dropping the table is possible with the help of this.
• Renaming of the table is possible.
• We can even add columns.
• Renaming of the columns can be done.
• Columns can be changed too.
• We can remove the columns and various other things can be done.

• Public: any external class or method that uses the same class in which it is defined can access this method.
• Protected: these can be used only within the class in which they are defined and the classes that inherit from the class in which they are defined.
• Private: these can be accessed only within the class in which they are defined.

• Meta-programming: code generation is used but for heavy lifting, it uses meta-programming.
• Active record: objects are saved to the database through this framework. It identifies the columns in a schema and binds them to your domain object.
• Scaffolding: it means it has the ability of creating temporary code automatically.
• Convention over configuration: much configuration is not needed if the naming convention is followed.
• Three environments: testing, development, and production are the three default environments in this framework.
• Built-in testing: test cases are used in this for writing and executing the codes.

• Rails observers: these are same as callbacks but are used when the method is not directly associated to the life cycle of the object. It lives for a longer duration of time and can be attached or detached at any time.
• Rails callback: the callback methods can only be called at only certain points of time in the life cycle of an object like validation, creation, updating, deletion, etc. Unlike the rails observers, the rails callback lives for only a short period of time.

• App/controllers: in this, a web request is made by the user which is handled by the controller. Rails make use of this controller sub directory for finding the controller class.
• App/helpers: some helper classes are present in the helper sub directory which is used for assisting the view, model and the controller classes present in it.