Serializers (Active Model Serializers) in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What JSON output does this serializer produce?

Given the following serializer and model instance, what is the JSON output?

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name
  has_many :posts
end

user = User.new(id: 1, name: 'Alice')
post1 = Post.new(id: 10, title: 'Hello')
post2 = Post.new(id: 11, title: 'World')
user.posts = [post1, post2]

serialized = ActiveModelSerializers::SerializableResource.new(user).to_json

A {"user":{"id":1,"name":"Alice"}}

B {"id":1,"name":"Alice"}

C {"id":1,"name":"Alice","posts":[{"id":10,"title":"Hello"},{"id":11,"title":"World"}]}

D {"user":{"id":1,"name":"Alice","posts":[{"id":10,"title":"Hello"},{"id":11,"title":"World"}]}}

💡 Hint

Active Model Serializers wraps the output in a root key by default.

By default, Active Model Serializers wraps the serialized object in a root key named after the model (here 'user'). The attributes and associations appear inside this root key.

📝 Syntax

intermediate

Which serializer code snippet is syntactically correct?

Identify the correct syntax for defining attributes and associations in an Active Model Serializer.

A

class ArticleSerializer < ActiveModel::Serializer
  attributes :id, :title
  has_one :author
end

B

class ArticleSerializer < ActiveModel::Serializer
  attribute :id, :title
  has_one :author
end

C

class ArticleSerializer < ActiveModel::Serializer
  attributes :id :title
  has_one :author
end

D

class ArticleSerializer < ActiveModel::Serializer
  attributes :id, :title
  has_one author
end

💡 Hint

Check the method names and syntax for attributes and associations.

The method to declare multiple attributes is 'attributes' with symbols separated by commas. Associations use 'has_one' or 'has_many' with a symbol argument.

🔧 Debug

advanced

Why does this serializer raise an error?

Given this serializer code, why does it raise a NoMethodError when serializing?

Ruby on Rails

class CommentSerializer < ActiveModel::Serializer
  attributes :id, :content, :user_name

  def user_name
    object.user.name
  end
end

comment = Comment.new(id: 5, content: 'Nice post!')
serialized = ActiveModelSerializers::SerializableResource.new(comment).to_json

A The method 'user_name' is not defined correctly; it should be a class method.

B The comment object has no associated user, so 'object.user' is nil causing NoMethodError on 'name'.

C The 'attributes' method cannot include custom methods like 'user_name'.

D The serializer is missing 'has_one :user' declaration causing the error.

💡 Hint

Check if the associated user object exists before calling its methods.

The error happens because 'object.user' is nil (no user associated), so calling 'name' on nil raises NoMethodError.

❓ state_output

advanced

What is the value of 'serialized' after running this code?

Consider this serializer with conditional attribute inclusion. What JSON does it produce when 'include_email' is false?

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name
  attribute :email, if: :include_email?

  def include_email?
    instance_options[:include_email] == true
  end
end

user = User.new(id: 2, name: 'Bob', email: '[e-mail]')
serialized = ActiveModelSerializers::SerializableResource.new(user, include_email: false).to_json

A {"user":{"id":2,"name":"Bob","email":"[e-mail]"}}

B {"id":2,"name":"Bob"}

C {"user":{"id":2,"name":"Bob"}}

D {"id":2,"name":"Bob","email":"[e-mail]"}

💡 Hint

The email attribute is included only if 'include_email' option is true.

Since 'include_email' is false, the 'email' attribute is excluded from the output. The root key 'user' wraps the attributes.

🧠 Conceptual

expert

Which statement about Active Model Serializers caching is true?

Select the correct statement about how caching works in Active Model Serializers.

A Caching requires manual cache key management and does not expire automatically when object attributes change.

B Caching stores the entire serialized JSON output per object and automatically expires when the object changes.

C Caching is enabled by default and uses Rails fragment caching with no configuration needed.

D Caching only works for has_many associations, not for individual objects.

💡 Hint

Think about how cache keys and expiration are handled in serializers.

Active Model Serializers caching requires you to manage cache keys manually. It does not automatically expire caches when object attributes change.