Why models represent data in Ruby on Rails - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do Rails models represent data?

In Rails, what is the main reason models represent data?

A To handle user interface layout and styling

B To manage HTTP requests and routing

C To store and manage the application's data and business logic

D To control background job processing

💡 Hint

Think about where the app keeps and organizes information.

Models in Rails are designed to represent and manage the data and business rules of the application. They interact with the database and hold the logic related to the data.

❓ component_behavior

intermediate

What happens when you create a new model instance in Rails?

Consider this Rails code:

user = User.new(name: 'Alice')

What does this code do?

A Creates a new user record in the database immediately

B Creates a new User object in memory without saving to the database yet

C Deletes an existing user named Alice

D Updates the name of all users to 'Alice'

💡 Hint

Think about when data is saved to the database.

User.new creates a new instance of the User model in memory. It does not save it to the database until you call save.

❓ state_output

advanced

What is the output after saving a model?

Given this Rails code:

user = User.new(name: 'Bob')
saved = user.save
puts saved

What will be printed?

A An error is raised

B false

C nil

D true

💡 Hint

Think about what save returns when successful.

The save method returns true if the model was saved successfully to the database.

📝 Syntax

advanced

Which code correctly defines a model with a validation?

Which of these Rails model definitions correctly adds a validation for presence of a name?

Ruby on Rails

class User < ApplicationRecord
  # validation here
end

A validates :name, presence: true

B validate :name, presence: true

C validates_presence_of :name

D validates :name, required: true

💡 Hint

Look for the correct Rails validation syntax.

The correct syntax to validate presence is validates :name, presence: true. Option A is deprecated syntax, and B and D are incorrect.

🔧 Debug

expert

Why does this model raise an error on save?

Given this model:

class Product < ApplicationRecord
  validates :price, numericality: { greater_than: 0 }
end

product = Product.new(price: -5)
product.save!

What error will this code raise?

A ActiveRecord::RecordInvalid

B NoMethodError

C ArgumentError

D TypeError

💡 Hint

Think about what happens when validations fail and save! is called.

The save! method raises ActiveRecord::RecordInvalid if validations fail, such as when price is less than or equal to zero.