Why caching improves response times in Ruby on Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to cache the result of a method call in Rails.

Ruby on Rails

Rails.cache.[1]('user_1') { User.find(1) }

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

Afetch

Bstore

Cread

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'read' only reads without storing new data.

Using 'store' requires a value, not a block.

The fetch method tries to read from cache and runs the block if the cache is empty, storing the result.

2fill in blank

medium

Complete the code to expire a cached fragment in Rails.

Ruby on Rails

expire_fragment([1])

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

Acache_key_for_users

BUser.all

C:all_users

D'all_users'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing an ActiveRecord relation instead of a cache key string.

Using a symbol instead of a string key.

The expire_fragment method takes the cache key string to remove the cached fragment.

3fill in blank

hard

Fix the error in the caching code to properly cache a view fragment.

Ruby on Rails

<% cache [1] do %>
  <p>Cached content here</p>
<% end %>

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

AUser.all

B'user_list'

C:user_list

Duser_list

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a variable without quotes causing undefined variable error.

Using a symbol instead of a string key.

The cache helper expects a string or cache key to identify the fragment. Quotes are needed for a string key.

4fill in blank

hard

Fill both blanks to create a cache key with a timestamp to expire cache after update.

Ruby on Rails

cache_key = "users/[1]-#{User.maximum(:[2])}"

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

Alist

Bupdated_at

Ccreated_at

Dcount

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'created_at' which doesn't change on updates.

Using 'count' which doesn't reflect update time.

The cache key includes 'list' and the 'updated_at' timestamp to expire cache when users update.

5fill in blank

hard

Fill all three blanks to write a method that caches a user's profile with expiration.

Ruby on Rails

def cached_profile(user)
  Rails.cache.[1]("profile_#{user.[2]", expires_in: [3]) do
    user.profile_data
  end
end

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

Afetch

Bid

C5.minutes

Dstore

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'store' which requires a value, not a block.

Using 'name' instead of 'id' for cache key.

Not setting expiration time.

The method uses fetch to get or store the cache, uses the user's id in the key, and sets expiration to 5 minutes.

Practice

1. Why does caching improve response times in a Rails application?

easy

A. Because it stores precomputed data to avoid repeating slow operations

B. Because it increases the size of the database

C. Because it disables user requests temporarily

D. Because it deletes old data automatically

Solution

1. Step 1: Understand what caching does

   Caching saves results of expensive operations so they don't have to run again.

2. Step 2: Connect caching to response speed

   By reusing stored data, the app responds faster because it skips slow work.

3. Final Answer:

   Because it stores precomputed data to avoid repeating slow operations -> Option A

4. Quick Check:

   Caching speeds response by storing data [OK]

Hint: Caching saves time by reusing data, not recalculating it [OK]

Common Mistakes:

• Thinking caching increases database size
• Believing caching blocks user requests
• Assuming caching deletes data automatically

2. Which of the following is the correct way to write a cache fetch block in Rails?

easy

A. Rails.cache.get('key') { expensive_operation }

B. Rails.cache.fetch('key') { expensive_operation }

C. Rails.cache.store('key', expensive_operation)

D. Rails.cache.save('key') { expensive_operation }

Solution

1. Step 1: Recall Rails caching syntax

   The correct method to fetch or store cached data with a block is fetch.

2. Step 2: Verify method names

   get, store, and save are not valid Rails cache methods for this pattern.

3. Final Answer:

   Rails.cache.fetch('key') { expensive_operation } -> Option B

4. Quick Check:

   Use fetch with block to cache [OK]

Hint: Remember: fetch reads or writes cache with a block [OK]

Common Mistakes:

• Using get instead of fetch
• Trying to store with a block incorrectly
• Confusing save with fetch

3. Given this Rails code snippet, what will be the output?

count = 0
result = Rails.cache.fetch('count_key') do
  count += 1
end
puts result
result = Rails.cache.fetch('count_key') do
  count += 1
end
puts result

medium

A. 0 and 1

B. 1 and 2

C. 1 and 1

D. 2 and 2

Solution

1. Step 1: Analyze the first fetch call

   The block runs because cache is empty, so count increments from 0 to 1, and 1 is stored and printed.

2. Step 2: Analyze the second fetch call

   The cache has 'count_key', so the block does not run; cached value 1 is returned and printed again.

3. Final Answer:

   1 and 1 -> Option C

4. Quick Check:

   Cache returns stored value, block skipped second time [OK]

Hint: Cache block runs once; later calls return stored value [OK]

Common Mistakes:

• Assuming block runs every time
• Thinking count increments twice
• Confusing initial count value

4. You added caching to a Rails app, but the response time did not improve. What is the most likely cause?

medium

A. The cache expiration time is set too long

B. The cache store is set to memory_store

C. The cache block returns a static value

D. The cache key changes every request, so cache is never reused

Solution

1. Step 1: Understand caching depends on cache keys

   If the key changes every request, the cache never hits and always recomputes.

2. Step 2: Evaluate other options

   Memory store is fast and good for caching; static values and long expiration do not prevent caching benefits.

3. Final Answer:

   The cache key changes every request, so cache is never reused -> Option D

4. Quick Check:

   Cache key consistency is crucial for reuse [OK]

Hint: Check if cache keys stay the same to reuse data [OK]

Common Mistakes:

• Blaming cache store type incorrectly
• Thinking static values hurt caching
• Assuming long expiration slows response

5. You want to cache a user's profile page in Rails but ensure it updates when the user changes their name. Which caching strategy best balances speed and freshness?

hard

A. Cache the page with a key including the user's updated_at timestamp

B. Cache the page forever without expiration

C. Do not cache the page at all to always show fresh data

D. Cache the page but clear the entire cache when any user updates

Solution

1. Step 1: Identify need for freshness and caching

   We want fast responses but also updated content when user changes name.

2. Step 2: Use cache key with updated_at timestamp

   Including updated_at in the cache key ensures cache refreshes only when user data changes.

3. Step 3: Evaluate other options

   Caching forever risks stale data; no caching is slow; clearing entire cache is inefficient.

4. Final Answer:

   Cache the page with a key including the user's updated_at timestamp -> Option A

5. Quick Check:

   Cache key with timestamp balances speed and freshness [OK]

Hint: Use timestamps in cache keys to auto-refresh stale data [OK]

Common Mistakes:

• Caching forever causing stale pages
• Not caching and losing speed benefits
• Clearing whole cache wastes resources