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.