Repository pattern for data access in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does the repository pattern improve Flask app data access?

Consider a Flask app using the repository pattern for data access. What is the main benefit of using this pattern?

A It forces all database queries to be written inline in the route functions.

B It separates data access logic from business logic, making code easier to maintain and test.

C It removes the need for any database connection or ORM.

D It automatically caches all data without extra code.

💡 Hint

Think about how separating concerns helps in coding.

The repository pattern creates a clear layer between how data is fetched or saved and how the app uses that data. This separation makes the code cleaner and easier to change or test.

📝 Syntax

intermediate

Identify the correct repository method signature in Flask

Which of the following method signatures correctly defines a repository method to fetch a user by ID in Flask?

Flask

class UserRepository:
    def get_user_by_id(self, user_id):
        pass

A def get_user_by_id(self, user_id):

B def getUserById(user_id):

C def get_user_by_id(userId):

D def get_user_by_id():

💡 Hint

Remember Python method conventions and parameters.

In Python classes, methods must have 'self' as the first parameter. The method name should be snake_case. The parameter name should be descriptive and consistent.

❓ state_output

advanced

What is the output of this Flask repository usage?

Given the repository and Flask route below, what will be the JSON response when accessing /user/2?

Flask

class UserRepository:
    def __init__(self):
        self.users = {1: {'name': 'Alice'}, 2: {'name': 'Bob'}}
    def get_user_by_id(self, user_id):
        return self.users.get(user_id, None)

from flask import Flask, jsonify
app = Flask(__name__)
repo = UserRepository()

@app.route('/user/<int:user_id>')
def get_user(user_id):
    user = repo.get_user_by_id(user_id)
    if user:
        return jsonify(user)
    else:
        return jsonify({'error': 'User not found'}), 404

A {"name": "Bob"}

B 500 Internal Server Error

C {"error": "User not found"}

D {"name": "Alice"}

💡 Hint

Check the user ID passed and the repository data.

The repository has user ID 2 mapped to Bob. The route returns the user data as JSON if found.

🔧 Debug

advanced

Why does this Flask repository code raise an error?

Examine the code below. Why does calling repo.get_user_by_id(1) raise an error?

Flask

class UserRepository:
    def __init__(self):
        self.users = {1: {'name': 'Alice'}}
    def get_user_by_id():
        return self.users.get(1)

repo = UserRepository()
repo.get_user_by_id(1)

A The method call passes an argument but method expects none, causing ValueError.

B The users dictionary is empty, so KeyError occurs.

C Method get_user_by_id is missing 'self' parameter, causing a TypeError.

D The class UserRepository is not instantiated before calling the method.

💡 Hint

Check method definitions inside classes.

Instance methods must have 'self' as the first parameter. Without it, Python raises a TypeError when calling with an argument.

🧠 Conceptual

expert

Which statement best describes the repository pattern's role in Flask apps?

Choose the statement that best explains how the repository pattern benefits Flask applications in managing data access.

A It automatically generates REST API endpoints for all database tables.

B It requires all data queries to be written directly in Flask route functions for speed.

C It eliminates the need for any ORM or database driver in the app.

D It abstracts data storage details, allowing the app to switch databases without changing business logic.

💡 Hint

Think about flexibility and separation of concerns.

The repository pattern hides how data is stored or retrieved. This lets developers change the database or data source without rewriting the app's core logic.