Response caching strategies in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the caching extension in Flask.

Flask

from flask_caching import [1]

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

ACacheControl

BCache

CCacheManager

DCacheHandler

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'CacheControl' which is unrelated to Flask-Caching

Using plural forms like 'Caches'

The Flask-Caching extension provides the Cache class to enable caching in Flask apps.

2fill in blank

medium

Complete the code to initialize caching with a simple config.

Flask

app = Flask(__name__)
app.config['CACHE_TYPE'] = [1]
cache = Cache(app)

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

A'simple'

B'redis'

C'filesystem'

D'null'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'redis' without Redis server configured

Using 'null' which disables caching

The 'simple' cache type uses in-memory caching suitable for development and testing.

3fill in blank

hard

Fix the error in the decorator to cache the response for 60 seconds.

Flask

@cache.[1](timeout=60)
def get_data():
    return 'Hello World'

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

Acache_timeout

Bcache_for

Ccache_response

Dcached

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent decorators like 'cache_response'

Confusing with cache timeout parameter

The correct decorator to cache a view function is @cache.cached.

4fill in blank

hard

Fill both blanks to cache a function with a custom key prefix and 120 seconds timeout.

Flask

@cache.[1](timeout=[2], key_prefix='my_key')
def fetch_data():
    return {'data': 123}

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

Acached

B60

C120

Dmemoize

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'memoize' decorator which is for different caching

Setting timeout to 60 instead of 120

Use @cache.cached with timeout=120 to cache the function with a custom key prefix.

5fill in blank

hard

Fill all three blanks to create a cache key dynamically using function arguments and cache the result.

Flask

def make_cache_key(*args, **kwargs):
    return f"user_[1]_[2]"

@cache.[3](key_prefix=make_cache_key)
def get_user_data(user_id, detail_level):
    return {'id': user_id, 'detail': detail_level}

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

Aargs[0]

Bargs[1]

Ccached

Dmemoize

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cached' decorator which does not support function arguments well

Using parameter names directly instead of args[0]/args[1]

The cache key uses args[0] (user_id) and args[1] (detail_level) to uniquely identify cached data. The @cache.memoize decorator caches functions with arguments.

Practice

1. What is the main purpose of response caching in a Flask application?

easy

A. To increase the size of the response data

B. To save server work and speed up response times

C. To make the server run slower intentionally

D. To disable user access temporarily

Solution

1. Step 1: Understand response caching

   Response caching stores the output of a request so the server doesn't have to recompute it every time.

2. Step 2: Identify the benefit

   This reduces server work and makes the app respond faster to repeated requests.

3. Final Answer:

   To save server work and speed up response times -> Option B

4. Quick Check:

   Response caching = save work & speed up [OK]

Hint: Caching speeds up responses by saving work [OK]

Common Mistakes:

• Thinking caching increases response size
• Believing caching slows down the server
• Confusing caching with access control

2. Which of the following is the correct way to cache a Flask route response for 60 seconds using Flask-Caching?

easy

A. @cache.cache(60)
def my_route():
return 'Hello'

B. @cache.cache(timeout=60)
def my_route():
return 'Hello'

C. @cache.cached(timeout=60)
def my_route():
return 'Hello'

D. @cached(60)
def my_route():
return 'Hello'

Solution

1. Step 1: Recall Flask-Caching decorator syntax

   The correct decorator is @cache.cached with a named argument timeout=60 to set cache duration.

2. Step 2: Check each option

   @cache.cached(timeout=60) def my_route(): return 'Hello' uses correct decorator and syntax. Options A and B use cache.cache which is invalid. @cached(60) def my_route(): return 'Hello' misses the cache. instance prefix.

3. Final Answer:

   @cache.cached(timeout=60) def my_route(): return 'Hello' -> Option C

4. Quick Check:

   Use @cache.cached(timeout=seconds) [OK]

Hint: Use @cache.cached with timeout= seconds [OK]

Common Mistakes:

• Using @cache.cache instead of @cache.cached
• Omitting the cache. prefix (@cached instead of @cache.cached)
• Using positional timeout argument

3. Given the code below, what will be printed on the second call to get_data() within 30 seconds?

@cache.cached(timeout=30)
def get_data():
    print('Fetching data...')
    return 'Data'

medium

A. Data

B. Fetching data...\nData

C. Fetching data...

D. Error: cache not found

Solution

1. Step 1: Understand caching effect on function calls

   The first call runs the function, prints 'Fetching data...', and caches the return 'Data'.

2. Step 2: Analyze second call within timeout

   Within 30 seconds, the cached result is returned directly, so the print statement does not run again.

3. Final Answer:

   Data -> Option A

4. Quick Check:

   Cached call skips print, returns cached 'Data' [OK]

Hint: Cached calls skip function body, return saved result [OK]

Common Mistakes:

• Expecting print output on every call
• Confusing cached return with function execution
• Assuming cache misses cause errors

4. Identify the error in this Flask caching code snippet:

@cache.cached(timeout=60)
def index():
    return render_template('index.html')

# Later in code
cache = Cache(app, config={'CACHE_TYPE': 'simple'})

medium

A. render_template cannot be cached

B. Timeout value must be a string, not integer

C. CACHE_TYPE 'simple' is invalid

D. Cache instance is created after using @cache.cached decorator

Solution

1. Step 1: Check order of cache setup and usage

   The decorator @cache.cached uses the cache object, but it is created after the function definition, so cache is undefined at decoration time.

2. Step 2: Validate other options

   Timeout as integer is valid. render_template output can be cached. 'simple' cache type is valid for development.

3. Final Answer:

   Cache instance is created after using @cache.cached decorator -> Option D

4. Quick Check:

   Define cache before using decorators [OK]

Hint: Create cache before decorating routes [OK]

Common Mistakes:

• Defining cache after using it in decorators
• Thinking timeout must be string
• Believing templates can't be cached

5. You want to cache different responses for a Flask route based on the logged-in user ID. Which caching strategy should you use to ensure each user gets their own cached response?

hard

A. Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}')

B. Use @cache.cached(timeout=60, key_prefix=lambda: request.args)

C. Use @cache.cached(timeout=60, key_prefix=lambda: request.path)

D. Use @cache.cached(timeout=60) without key_prefix

Solution

1. Step 1: Understand caching by key prefix

   The cache stores responses by keys. To cache per user, the key must include the user ID.

2. Step 2: Evaluate options for key prefix

   Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}') uses a lambda returning a string with the current user's ID, ensuring unique cache per user. Use @cache.cached(timeout=60, key_prefix=lambda: request.path) uses request path only, same for all users. Use @cache.cached(timeout=60, key_prefix=lambda: request.args) uses request arguments, which may not include user ID. Use @cache.cached(timeout=60) without key_prefix uses default key, same for all users.

3. Final Answer:

   Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}') -> Option A

4. Quick Check:

   Cache key must include user ID for per-user caching [OK]

Hint: Include user ID in cache key prefix [OK]

Common Mistakes:

• Using only request path for cache key
• Ignoring user-specific cache needs
• Not using key_prefix for per-user caching