MVC architecture in Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does MVC stand for in Rails?

MVC stands for Model-View-Controller. It is a design pattern that separates an application into three main parts to organize code and responsibilities.

beginner

What is the role of the Model in Rails MVC?

The Model handles data and business logic. It talks to the database, stores data, and enforces rules about the data.

beginner

What does the Controller do in Rails MVC?

The Controller receives user input, talks to the Model to get or change data, and decides which View to show next.

beginner

What is the purpose of the View in Rails MVC?

The View displays data to the user. It shows the user interface and presents information from the Model in a readable way.

intermediate

How do the Model, View, and Controller interact in Rails?

The Controller gets user requests, asks the Model for data or updates, then passes data to the View to display. The View shows the data, and the cycle repeats with new user actions.

In Rails MVC, which component directly communicates with the database?

A Model

B View

C Controller

D Router

The Model handles data storage and retrieval from the database.

Which MVC part in Rails is responsible for deciding which page to show next?

A Helper

B View

C Model

D Controller

The Controller processes user input and chooses the View to render.

What does the View in Rails MVC mainly do?

A Store data

B Display data to users

C Handle user input

D Manage database connections

The View presents data to the user in a readable format.

Which MVC component in Rails contains business rules and validations?

A Model

B View

C Controller

D Asset Pipeline

The Model enforces business logic and data validations.

In Rails MVC, what triggers the Controller to act?

A View rendering

B Database changes

C User input or requests

D Background jobs

User actions like clicking links or submitting forms send requests that the Controller handles.

Explain the responsibilities of each part in the Rails MVC architecture.

Think about who talks to the database, who decides what to show, and who shows it.

Describe how a user request flows through the MVC components in a Rails app.

Follow the path from user action to what they see on screen.

Practice

1. In the MVC architecture of Rails, which component is responsible for handling user input and controlling the flow of the application?

easy

A. Controller

B. Model

C. View

D. Router

Solution

1. Step 1: Understand MVC roles

   The Model manages data, the View displays data, and the Controller handles user input and application flow.

2. Step 2: Identify the component for user input

   The Controller receives user requests and decides what to do next.

3. Final Answer:

   Controller -> Option A

4. Quick Check:

   Controller = handles user input [OK]

Hint: Controller manages user actions and app flow [OK]

Common Mistakes:

• Confusing Model with Controller
• Thinking View handles user input
• Selecting Router as MVC component

2. Which of the following is the correct way to define a controller class in Rails?

easy

A. class UsersController inherits ApplicationController; end

B. def UsersController < ApplicationController; end

C. class UsersController < ApplicationController; end

D. controller UsersController extends ApplicationController {}

Solution

1. Step 1: Recall Ruby class syntax

   In Ruby, classes are defined with class ClassName < ParentClass and closed with end.

2. Step 2: Match Rails controller syntax

   Rails controllers inherit from ApplicationController using < syntax.

3. Final Answer:

   class UsersController < ApplicationController; end -> Option C

4. Quick Check:

   Ruby class syntax = class UsersController < ApplicationController; end [OK]

Hint: Use Ruby class inheritance syntax with < [OK]

Common Mistakes:

• Using 'def' instead of 'class'
• Using 'inherits' keyword (not Ruby)
• Using JavaScript-like syntax

3. Given the following Rails controller code, what will be the rendered output when visiting /welcome/index?

class WelcomeController < ApplicationController
  def index
    @message = "Hello, Rails!"
  end
end

And the view file app/views/welcome/index.html.erb contains:

<h1><%= @message %></h1>

medium

A. Hello, Rails!

B. @message

C. Error: undefined variable @message

D.

Solution

1. Step 1: Understand controller instance variable

   The controller sets @message to "Hello, Rails!" which is accessible in the view.

2. Step 2: Evaluate view rendering

   The view uses ERB tag <%= @message %> to insert the string value inside the <h1> tag.

3. Final Answer:

   <h1>Hello, Rails!</h1> -> Option A

4. Quick Check:

   Instance variable passed to view = <h1>Hello, Rails!</h1> [OK]

Hint: Instance variables in controller show in views with <%= %> [OK]

Common Mistakes:

• Using local variables instead of instance variables
• Forgetting = in ERB tag
• Expecting variable name printed literally

4. Identify the error in this Rails controller code snippet:

class ProductsController < ApplicationController
  def show
    @product = Product.find(params[:id])
  end

  def index
    @products = Product.all
  end
end

What is the likely cause of a runtime error when visiting /products/show without an id parameter?

medium

A. Method index should be defined before show

B. Missing id in params causes find to raise an exception

C. Instance variables cannot be used in controllers

D. Controller class name should be ProductController not ProductsController

Solution

1. Step 1: Analyze show method usage

   The show method calls Product.find(params[:id]), which requires a valid id parameter.

2. Step 2: Understand missing parameter effect

   If params[:id] is missing, find raises an ActiveRecord::RecordNotFound error causing a runtime failure.

3. Final Answer:

   Missing id in params causes find to raise an exception -> Option B

4. Quick Check:

   Missing param causes error = Missing id in params causes find to raise an exception [OK]

Hint: Always check required params before calling find [OK]

Common Mistakes:

• Thinking method order matters
• Believing instance variables are invalid
• Confusing singular/plural controller names

5. You want to display a list of all users with their email addresses in a Rails app. Which MVC components should you update and how? A) Update the Model to fetch users, Controller to assign users to a variable, and View to loop and display emails. B) Update only the View to query the database and display emails. C) Update the Controller to fetch users and display emails directly without a View. D) Update the Model to display emails and Controller to fetch users.

hard

A. Update Model to display and Controller to fetch

B. Update View only to query and display

C. Update Controller only to fetch and display

D. Update Model to fetch, Controller to assign, View to display

Solution

1. Step 1: Understand MVC responsibilities

   The Model handles data fetching, the Controller prepares data for the View, and the View displays data.

2. Step 2: Apply MVC to user list display

   The Model fetches users, Controller assigns them to an instance variable, and View loops through to show emails.

3. Final Answer:

   Update Model to fetch, Controller to assign, View to display -> Option D

4. Quick Check:

   MVC separation = Update Model to fetch, Controller to assign, View to display [OK]

Hint: Model fetches, Controller assigns, View displays [OK]

Common Mistakes:

• Putting database queries in the View
• Displaying data directly in Controller
• Making Model handle display logic