Why validations protect data integrity in Ruby on Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a validation that ensures the presence of a name.

Ruby on Rails

class User < ApplicationRecord
  validates :name, [1]
end

Drag options to blanks, or click blank then click option'

Alength: { minimum: 3 }

Bnumericality: true

Cuniqueness: true

Dpresence: true

Attempts:

3 left

💡 Hint

Common Mistakes

Using length validation instead of presence

Using uniqueness when presence is needed

The presence: true validation ensures that the name field is not empty, protecting data integrity by requiring this important attribute.

2fill in blank

medium

Complete the code to validate that the email is unique.

Ruby on Rails

class User < ApplicationRecord
  validates :email, [1]
end

Drag options to blanks, or click blank then click option'

Auniqueness: true

Blength: { maximum: 50 }

Cformat: { with: /@/ }

Dpresence: true

Attempts:

3 left

💡 Hint

Common Mistakes

Using presence instead of uniqueness

Using format validation only

The uniqueness: true validation ensures no two users have the same email, protecting data integrity by avoiding duplicates.

3fill in blank

hard

Fix the error in the validation to check that age is a number greater than or equal to 18.

Ruby on Rails

class User < ApplicationRecord
  validates :age, numericality: { [1]: 18 }
end

Drag options to blanks, or click blank then click option'

Agreater_than

Bgreater_than_or_equal_to

Cless_than

Dequal_to

Attempts:

3 left

💡 Hint

Common Mistakes

Using greater_than which excludes 18

Using less_than or equal_to incorrectly

The option greater_than_or_equal_to correctly checks that age is 18 or older, ensuring valid age data.

4fill in blank

hard

Fill both blanks to validate that the username is present and has a minimum length of 5.

Ruby on Rails

class User < ApplicationRecord
  validates :username, [1], [2]
end

Drag options to blanks, or click blank then click option'

Apresence: true

Blength: { minimum: 5 }

Cuniqueness: true

Dnumericality: true

Attempts:

3 left

💡 Hint

Common Mistakes

Using uniqueness instead of presence

Forgetting to check length

Using presence: true ensures the username is not empty, and length: { minimum: 5 } ensures it has at least 5 characters, protecting data quality.

5fill in blank

hard

Fill all three blanks to validate that the password is present, has a minimum length of 8, and includes a confirmation field.

Ruby on Rails

class User < ApplicationRecord
  validates :password, [1], [2], [3]
end

Drag options to blanks, or click blank then click option'

Apresence: true

Blength: { minimum: 8 }

Cconfirmation: true

Duniqueness: true

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting confirmation validation

Using uniqueness instead of confirmation

The validations ensure the password is entered (presence: true), is at least 8 characters (length: { minimum: 8 }), and matches a confirmation field (confirmation: true), protecting user security and data integrity.

Practice

1. Why are validations important in a Rails application?

easy

A. They speed up the database queries automatically.

B. They generate user interface forms automatically.

C. They create database tables for the models.

D. They prevent invalid data from being saved to the database.

Solution

1. Step 1: Understand the role of validations

   Validations check data before saving to ensure it meets rules.

2. Step 2: Identify what validations protect

   They protect the database from bad or incorrect data entries.

3. Final Answer:

   They prevent invalid data from being saved to the database. -> Option D

4. Quick Check:

   Validations = prevent bad data [OK]

Hint: Validations stop bad data before saving [OK]

Common Mistakes:

• Thinking validations speed up queries
• Confusing validations with database migrations
• Assuming validations create UI forms

2. Which of the following is the correct way to add a presence validation in a Rails model for the attribute email?

easy

A. validates :email, presence: true

B. validate :email, presence: true

C. validates_presence_of :email

D. validate_presence :email

Solution

1. Step 1: Recall Rails validation syntax

   The correct syntax uses validates with attribute and options.

2. Step 2: Match the correct method and option

   validates :email, presence: true is the modern and correct form.

3. Final Answer:

   validates :email, presence: true -> Option A

4. Quick Check:

   Use validates + attribute + option [OK]

Hint: Use 'validates' with attribute and presence: true [OK]

Common Mistakes:

• Using 'validate' instead of 'validates'
• Using deprecated 'validates_presence_of'
• Missing colon before attribute name

3. Given this model validation:

class User < ApplicationRecord
  validates :age, numericality: { greater_than_or_equal_to: 18 }
end

What happens if you try to save a user with age = 16?

medium

A. An error is raised and the app crashes.

B. The user is saved successfully with age 16.

C. The save fails because age is less than 18.

D. The age is automatically set to 18 and saved.

Solution

1. Step 1: Understand the numericality validation

   The validation requires age to be 18 or more to save.

2. Step 2: Check the given age value

   Age 16 is less than 18, so validation fails and save is blocked.

3. Final Answer:

   The save fails because age is less than 18. -> Option C

4. Quick Check:

   Age < 18 fails numericality validation [OK]

Hint: Validation blocks saving invalid data [OK]

Common Mistakes:

• Assuming invalid data saves anyway
• Thinking Rails auto-corrects invalid values
• Confusing validation failure with app crash

4. Look at this model code:

class Product < ApplicationRecord
  validates :name, presence: true
  validates :price, numericality: true
end

Why might saving Product.new(name: '', price: 'free') fail?

medium

A. Because Rails does not allow string prices.

B. Because name is empty and price is not a number.

C. Because validations are not defined correctly.

D. Because price is missing but name is valid.

Solution

1. Step 1: Check the presence validation on name

   Name is empty string, so presence validation fails.

2. Step 2: Check numericality validation on price

   Price is 'free' (a string), not a number, so numericality fails.

3. Final Answer:

   Because name is empty and price is not a number. -> Option B

4. Quick Check:

   Empty name + non-numeric price fail validations [OK]

Hint: Empty or wrong type values fail validations [OK]

Common Mistakes:

• Assuming empty string passes presence validation
• Thinking string 'free' counts as a number
• Believing validations auto-correct invalid data

5. You want to ensure a User model's username is unique and not empty. Which validation setup correctly protects data integrity?

hard

A. validates :username, presence: true, uniqueness: true

B. validates :username, presence: true; validates_uniqueness_of :username

C. validates_uniqueness_of :username, presence: true

D. validates :username, unique: true, presence: true

Solution

1. Step 1: Identify correct combined validation syntax

   Use validates with multiple options in one line for clarity.

2. Step 2: Check option correctness

   validates :username, presence: true, uniqueness: true uses presence: true and uniqueness: true correctly together.

3. Final Answer:

   validates :username, presence: true, uniqueness: true -> Option A

4. Quick Check:

   Use single validates with presence and uniqueness [OK]

Hint: Combine presence and uniqueness in one validates call [OK]

Common Mistakes:

• Using deprecated validates_uniqueness_of separately
• Wrong option name 'unique' instead of 'uniqueness'
• Splitting validations unnecessarily