Separation of concerns in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the main benefit of separation of concerns in system design

Which of the following best describes the primary benefit of applying separation of concerns in a software system?

A It eliminates the need for testing by making the system simpler.

B It reduces the number of lines of code by combining all functionalities into one module.

C It increases system complexity by mixing user interface and business logic together.

D It improves system maintainability by isolating different responsibilities into distinct modules.

💡 Hint

Think about how dividing tasks helps when you need to change or fix parts of a system.

Separation of concerns divides a system into distinct sections, each handling a specific responsibility. This makes the system easier to maintain and update.

❓ Architecture

intermediate

Choose the correct layering to separate concerns in a web application

In a typical web application, which layering correctly separates concerns according to best practices?

A Presentation layer, Business logic layer, Data access layer

B Data access layer, Presentation layer, Business logic layer

C Business logic layer, Data access layer, Presentation layer

D Presentation layer, Data access layer, Business logic layer

💡 Hint

Consider the flow of data from user input to storage and back.

The presentation layer handles user interface, the business logic layer processes data and rules, and the data access layer manages storage. This order cleanly separates concerns.

❓ scaling

advanced

Scaling a system with separation of concerns

You have a system separated into three services: user interface, business logic, and database access. Which scaling approach best follows separation of concerns principles?

A Scale only the database access service since it handles all data.

B Scale each service independently based on its load and resource needs.

C Scale the user interface and business logic together as a single unit.

D Scale the entire system by duplicating all services equally regardless of load.

💡 Hint

Think about which parts of the system might need more resources at different times.

Separating concerns allows independent scaling of each service based on its specific demands, improving efficiency and cost-effectiveness.

❓ tradeoff

advanced

Tradeoff of strict separation of concerns in system design

What is a common tradeoff when applying very strict separation of concerns in a system?

A Increased complexity in communication between modules can lead to performance overhead.

B Decreased ability to test modules independently.

C Reduced code readability because all logic is combined in one place.

D Elimination of the need for documentation.

💡 Hint

Consider what happens when many small parts need to talk to each other.

Strict separation can cause more communication between modules, which may slow down the system due to overhead.

❓ component

expert

Identify the component violating separation of concerns

Given a system with components: Authentication, User Profile, Payment Processing, and Notification. Which component violates separation of concerns if it handles both payment logic and sending emails?

A Notification

B Authentication

C Payment Processing

D User Profile

💡 Hint

Think about what each component's main responsibility should be.

Payment Processing should only handle payment logic. Sending emails belongs to Notification. Combining both violates separation of concerns.

Practice

1. What is the main purpose of separation of concerns in system design?

easy

A. To divide a system into parts that each handle a specific job

B. To combine all system functions into one module

C. To make the system run faster by using fewer parts

D. To remove all interfaces between system components

Solution

1. Step 1: Understand the concept of separation of concerns

   It means dividing a system into parts where each part has a clear, specific responsibility.

2. Step 2: Compare options with the concept

   Only To divide a system into parts that each handle a specific job describes dividing the system into parts with specific jobs, matching the concept.

3. Final Answer:

   To divide a system into parts that each handle a specific job -> Option A

4. Quick Check:

   Separation of concerns = divide system parts [OK]

Hint: Think: separate jobs make systems simpler [OK]

Common Mistakes:

• Confusing separation with combining functions
• Thinking it speeds up system by reducing parts
• Ignoring the role of interfaces

2. Which of the following is the correct way to apply separation of concerns in code structure?

easy

A. Separating UI code, business logic, and data access into different modules

B. Writing all code in one large file for easy access

C. Mixing UI logic and data processing in the same function

D. Ignoring interfaces between different parts

Solution

1. Step 1: Identify proper separation in code

   Separation of concerns means keeping UI, logic, and data handling separate.

2. Step 2: Match options to this principle

   Separating UI code, business logic, and data access into different modules correctly separates these concerns into different modules.

3. Final Answer:

   Separating UI code, business logic, and data access into different modules -> Option A

4. Quick Check:

   Separate UI, logic, data = Separating UI code, business logic, and data access into different modules [OK]

Hint: Keep UI, logic, data in separate files [OK]

Common Mistakes:

• Mixing UI and logic in one place
• Putting all code in one file
• Ignoring module boundaries

3. Consider this simplified code snippet applying separation of concerns:

class DataFetcher:
    def fetch(self):
        return "data"

class Processor:
    def process(self, data):
        return data.upper()

class UI:
    def display(self, processed_data):
        print(processed_data)

fetcher = DataFetcher()
data = fetcher.fetch()
processor = Processor()
processed = processor.process(data)
ui = UI()
ui.display(processed)

What will be printed when this code runs?

medium

A. processor

B. data

C. fetch

D. DATA

Solution

1. Step 1: Trace data flow through classes

   DataFetcher returns "data". Processor converts it to uppercase "DATA". UI prints it.

2. Step 2: Determine final output

   The UI prints the processed data, which is "DATA" in uppercase.

3. Final Answer:

   DATA -> Option D

4. Quick Check:

   Uppercase processed data = DATA [OK]

Hint: Follow data from fetch to display [OK]

Common Mistakes:

• Confusing original data with processed data
• Ignoring the uppercase conversion
• Thinking print shows method names

4. In a system designed with separation of concerns, which issue indicates a violation of this principle?

medium

A. Clear division of responsibilities between components

B. Separate modules for UI and data storage communicating via interfaces

C. A module handling both user input validation and database queries

D. Using interfaces to connect independent parts

Solution

1. Step 1: Identify violation of separation of concerns

   A module doing multiple unrelated jobs breaks the principle.

2. Step 2: Match options to violation

   A module handling both user input validation and database queries shows one module handling both validation and database queries, mixing concerns.

3. Final Answer:

   A module handling both user input validation and database queries -> Option C

4. Quick Check:

   Mixed responsibilities = violation [OK]

Hint: One module, one job only [OK]

Common Mistakes:

• Thinking interfaces cause violation
• Believing clear division is a problem
• Confusing separation with duplication

5. You are designing a web application with separation of concerns. Which design choice best supports this principle while ensuring scalability?

hard

A. Combine UI rendering, business logic, and data access in a single service

B. Use separate services for UI, business logic, and data storage connected via APIs

C. Store all data and logic in the client-side code for faster access

D. Avoid defining clear interfaces between components to reduce complexity

Solution

1. Step 1: Understand separation and scalability needs

   Separation means dividing concerns; scalability means easy to grow and maintain.

2. Step 2: Evaluate design options

   Use separate services for UI, business logic, and data storage connected via APIs uses separate services connected by APIs, which keeps concerns separate and supports scaling.

3. Final Answer:

   Use separate services for UI, business logic, and data storage connected via APIs -> Option B

4. Quick Check:

   Separate services + APIs = scalable separation [OK]

Hint: Separate services with APIs scale best [OK]

Common Mistakes:

• Combining all logic in one service
• Putting logic only on client side
• Skipping interfaces between parts