Devise gem overview in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the Devise gem in Rails?

Devise is a popular gem used in Rails applications. What main feature does it provide?

A It is used to optimize SQL queries for better performance.

B It helps with database migrations and schema changes.

C It manages user authentication and handles sign up, login, and logout.

D It provides tools for styling Rails views with CSS.

💡 Hint

Think about what users need to do to access a website securely.

Devise is mainly used to add user authentication features like sign up, login, logout, password recovery, and more.

❓ component_behavior

intermediate

What happens when you add devise :database_authenticatable to a User model?

In a Rails app using Devise, adding devise :database_authenticatable to the User model enables what behavior?

A It allows users to sign in using their email and encrypted password stored in the database.

B It automatically sends welcome emails to new users.

C It enables OAuth login with third-party providers like Google or Facebook.

D It creates an admin dashboard for managing users.

💡 Hint

Think about how users prove their identity with a password.

The database_authenticatable module handles storing encrypted passwords and verifying them during login.

❓ lifecycle

advanced

Which Devise callback runs after a user successfully signs in?

Devise provides callbacks during the user authentication lifecycle. Which callback is triggered right after a successful sign-in?

A before_authentication

B before_sign_out

C after_sign_up_path_for

D after_sign_in_path_for

💡 Hint

This callback helps decide where to send the user after login.

after_sign_in_path_for is called after a user signs in to determine the redirect path.

📝 Syntax

advanced

Which code snippet correctly adds the :confirmable module to Devise in the User model?

You want users to confirm their email address after signing up. Which code correctly enables this feature in the User model?

Ruby on Rails

class User < ApplicationRecord
  # Add devise modules here
end

A devise :database_authenticatable, :registerable, confirmable: true

B devise :database_authenticatable, :registerable, :confirmable

C elbamrifnoc: ,elbaretsiger: ,elbatacitnehtua_esabatad: esived

D devise :database_authenticatable, :registerable, confirmable

💡 Hint

Devise modules are symbols separated by commas inside the devise method call.

Devise modules are added as symbols in the devise call. The correct syntax uses colons before each module name.

🔧 Debug

expert

Why does Devise raise a MissingSecretKeyError in production?

You deployed your Rails app with Devise to production, but it raises Devise::MissingSecretKeyError. What is the most likely cause?

A The <code>secret_key_base</code> is not set or accessible in the production environment.

B The database migration for users was not run.

C The User model is missing the <code>devise</code> call.

D The routes for Devise were not added in <code>config/routes.rb</code>.

💡 Hint

Devise needs a secret key to encrypt tokens and sessions securely.

Devise requires secret_key_base to be set in production for encryption. Without it, this error occurs.

Practice

1. What is the primary purpose of the Devise gem in a Rails application?

easy

A. To manage database migrations automatically

B. To add user authentication features like login and registration

C. To style the user interface with CSS

D. To optimize SQL queries for performance

Solution

1. Step 1: Understand Devise's role in Rails

   Devise is a gem designed to handle user authentication tasks such as login, registration, password recovery, and more.

2. Step 2: Compare options with Devise's purpose

   Options B, C, and D relate to database, styling, and optimization, which are not Devise's focus.

3. Final Answer:

   To add user authentication features like login and registration -> Option B

4. Quick Check:

   Devise = User authentication [OK]

Hint: Devise is about user login and registration [OK]

Common Mistakes:

• Confusing Devise with database or styling tools
• Thinking Devise manages database migrations
• Assuming Devise handles UI design

2. Which command correctly installs Devise in a Rails project?

easy

A. rails devise setup

B. rails new devise install

C. rails generate devise:install

D. gem install devise

Solution

1. Step 1: Identify the standard Devise installation command

   The correct command to set up Devise after adding it to the Gemfile is rails generate devise:install.

2. Step 2: Check other options for correctness

   A: rails devise setup is invalid syntax, B: rails new devise install is invalid syntax, C installs the gem globally but not in Rails.

3. Final Answer:

   rails generate devise:install -> Option C

4. Quick Check:

   Devise install command = rails generate devise:install [OK]

Hint: Use 'rails generate devise:install' to set up Devise [OK]

Common Mistakes:

• Using 'gem install devise' instead of Rails generator
• Typing incorrect Rails commands
• Confusing gem installation with setup commands

3. Given the following code snippet in a Rails app using Devise:

class User < ApplicationRecord
  devise :database_authenticatable, :registerable
end

What feature does the :registerable module add to the User model?

medium

A. Allows users to sign up and edit their registration details

B. Encrypts user passwords in the database

C. Enables password reset via email

D. Locks user accounts after failed login attempts

Solution

1. Step 1: Understand the :registerable module

   The :registerable module in Devise adds features for user sign-up, editing, and deleting their account.

2. Step 2: Match other options to correct modules

   Password encryption is handled by :database_authenticatable, password reset by :recoverable, and account locking by :lockable.

3. Final Answer:

   Allows users to sign up and edit their registration details -> Option A

4. Quick Check:

   :registerable = sign up and edit [OK]

Hint: :registerable means users can sign up and edit info [OK]

Common Mistakes:

• Confusing :registerable with password or lock features
• Assuming :registerable encrypts passwords
• Mixing up Devise modules

4. You added Devise to your Rails app and ran rails generate devise User, but you get an error saying uninitialized constant Devise. What is the most likely cause?

medium

A. You ran the generator before creating the User model manually

B. Devise does not support generating User models

C. You need to restart the Rails server before running the generator

D. You forgot to add gem 'devise' to your Gemfile and run bundle install

Solution

1. Step 1: Identify cause of 'uninitialized constant Devise'

   This error usually means the Devise gem is not loaded, often because it was not added to the Gemfile or bundle install was not run.

2. Step 2: Evaluate other options

   The generator creates the User model, so manual creation is not needed. Restarting server does not fix missing gem. Devise supports User model generation.

3. Final Answer:

   You forgot to add gem 'devise' to your Gemfile and run bundle install -> Option D

4. Quick Check:

   Missing gem in Gemfile = uninitialized constant error [OK]

Hint: Add gem and run bundle install before generators [OK]

Common Mistakes:

• Running generator without adding gem to Gemfile
• Assuming User model must exist before generator
• Restarting server without bundling

5. You want to add email confirmation to users signing up with Devise. Which steps should you follow to enable this feature?

hard

A. Add :confirmable to the User model's devise call, generate a migration to add confirmation fields, then run migrations

B. Add :confirmable to the User model and restart the server only

C. Add :confirmable to the User model and create a new controller for confirmations manually

D. Add :confirmable to the User model and update the routes file with confirmation paths

Solution

1. Step 1: Enable :confirmable in User model

   Add :confirmable to the list of Devise modules in the User model to activate confirmation features.

2. Step 2: Add confirmation fields via migration

   Generate and run a migration to add necessary database columns like confirmation_token and confirmed_at.

3. Step 3: Run database migrations

   Run rails db:migrate to apply changes so Devise can track confirmations.

4. Final Answer:

   Add :confirmable to the User model's devise call, generate a migration to add confirmation fields, then run migrations -> Option A

5. Quick Check:

   :confirmable + migration + migrate = email confirmation [OK]

Hint: Add :confirmable and migrate database to enable confirmation [OK]

Common Mistakes:

• Forgetting to create and run migration for confirmation fields
• Assuming adding :confirmable alone is enough
• Manually creating controllers unnecessarily