Response caching strategies in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Flask route with cache control?

Consider this Flask route that sets cache headers:

from flask import Flask, make_response
app = Flask(__name__)

@app.route('/data')
def data():
    response = make_response('Hello World')
    response.headers['Cache-Control'] = 'public, max-age=60'
    return response

What will the browser do with the response?

Flask

from flask import Flask, make_response
app = Flask(__name__)

@app.route('/data')
def data():
    response = make_response('Hello World')
    response.headers['Cache-Control'] = 'public, max-age=60'
    return response

A The browser does not cache the response at all.

B The browser caches the response for 60 seconds and shares it with other users.

C The browser caches the response but only for the current user session.

D The browser caches the response indefinitely until manually cleared.

💡 Hint

Look at the meaning of 'public' and 'max-age' in Cache-Control headers.

The 'Cache-Control: public, max-age=60' header tells browsers and shared caches to store the response for 60 seconds. 'Public' means it can be cached by any cache, including shared ones.

❓ state_output

intermediate

What is the cache behavior of this Flask route using @cache.cached?

Given this Flask route using Flask-Caching:

from flask import Flask
from flask_caching import Cache

app = Flask(__name__)
cache = Cache(app, config={'CACHE_TYPE': 'SimpleCache'})

@app.route('/time')
@cache.cached(timeout=30)
def get_time():
    import time
    return str(time.time())

What happens when you call /time multiple times within 30 seconds?

Flask

from flask import Flask
from flask_caching import Cache

app = Flask(__name__)
cache = Cache(app, config={'CACHE_TYPE': 'SimpleCache'})

@app.route('/time')
@cache.cached(timeout=30)
def get_time():
    import time
    return str(time.time())

A The first call computes time; subsequent calls within 30 seconds return the cached time string.

B Each call computes a new time string regardless of caching.

C The cache is ignored because SimpleCache does not support timeout.

D The cache stores the time but expires immediately, so no caching occurs.

💡 Hint

Think about what @cache.cached with timeout does.

The @cache.cached decorator caches the function output for the specified timeout. Here, the first call stores the time string, and calls within 30 seconds return the cached value.

📝 Syntax

advanced

Which option correctly sets a Flask response to never cache?

Which code snippet correctly sets HTTP headers to prevent caching of a Flask response?

A response.headers['Cache-Control'] = 'no-store, no-cache, must-revalidate, max-age=0'

B response.headers['Cache-Control'] = 'public, max-age=0'

C response.headers['Cache-Control'] = 'private, max-age=60'

D response.headers['Cache-Control'] = 'max-age=3600, public'

💡 Hint

Look for headers that explicitly prevent caching.

'no-store' and 'no-cache' instruct browsers and caches not to store or reuse the response. 'must-revalidate' forces validation. 'max-age=0' means the response is immediately stale.

🔧 Debug

advanced

Why does this Flask cache not work as expected?

Consider this Flask route using Flask-Caching:

from flask import Flask
from flask_caching import Cache

app = Flask(__name__)
cache = Cache(app, config={'CACHE_TYPE': 'NullCache'})

@app.route('/data')
@cache.cached(timeout=60)
def data():
    return 'Cached Data'

Why does caching not occur?

Flask

from flask import Flask
from flask_caching import Cache

app = Flask(__name__)
cache = Cache(app, config={'CACHE_TYPE': 'NullCache'})

@app.route('/data')
@cache.cached(timeout=60)
def data():
    return 'Cached Data'

A The timeout value is too low to cache anything.

B The decorator @cache.cached is used incorrectly and does not cache.

C NullCache disables caching, so no data is stored or reused.

D Flask-Caching requires a Redis backend to cache data.

💡 Hint

Check the meaning of 'NullCache' in Flask-Caching.

NullCache is a cache type that disables caching completely. It never stores or returns cached data, so the function runs every time.

🧠 Conceptual

expert

Which caching strategy best suits dynamic user-specific content in Flask?

You have a Flask app serving user dashboards with personalized data that changes frequently. Which caching strategy is best to improve performance without showing wrong data?

A Disable all caching to ensure fresh data every request.

B Set Cache-Control to 'public, max-age=300' so all users share cached dashboards.

C Use client-side caching only with 'private, max-age=600' headers.

D Use server-side cache keyed by user ID to store each user's dashboard data separately.

💡 Hint

Think about caching personalized data safely.

Server-side caching keyed by user ID allows caching per user, avoiding data leaks between users and improving performance. Public caching shares data across users, which is unsafe for personalized content.