Bird
Raised Fist0

A class manages both business rules and audit logging. If audit requirements change frequently but business rules are stable, what happens if SRP is not applied?

medium🧠🧾 Concept Trace Q4 of Q15
OOP & Design Patterns - Single Responsibility Principle - One Class, One Reason to Change
A class manages both business rules and audit logging. If audit requirements change frequently but business rules are stable, what happens if SRP is not applied?
AFrequent audit changes will force modifications in business logic code, increasing risk.
BBusiness logic will be unaffected by audit changes due to separation of concerns.
CAudit logging can be changed independently without touching business logic.
DThe class will automatically adapt to audit changes without side effects.
Step-by-Step Solution
Solution:

  1. Step 1: Identify responsibilities

    Business rules and audit logging have different reasons to change.

  2. Step 2: Consequence of combined responsibilities

    Audit changes require edits in the same class, risking unintended effects on business logic.

  3. Final Answer:

    Option A -> Option A

  4. Quick Check:

    Combined responsibilities cause fragile code with ripple effects [OK]
Quick Trick: One reason to change per class prevents ripple changes [OK]
Common Mistakes:
MISTAKES
  • Assuming separation of concerns without SRP enforcement
  • Believing audit changes won't affect business logic
Trap Explanation:
PITFALL
  • Candidates often confuse separation of concerns with SRP enforcement.
Interviewer Note:
CONTEXT
  • Evaluates understanding of SRP's role in isolating change impact.
Master "Single Responsibility Principle - One Class, One Reason to Change" in OOP & Design Patterns

2 interactive learning modes - each teaches the same concept differently

SolutionTrace

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More OOP & Design Patterns Quizzes
Abstraction - Abstract Class vs Interface - When to Use Which - Abstraction - Abstract Class vs Interface - When to Use Which - Quiz 5medium Abstraction - Abstract Class vs Interface - When to Use Which - Abstraction - Abstract Class vs Interface - When to Use Which - Quiz 4medium Command Pattern - Undo/Redo, Request Queuing & Logging - Command Pattern - Undo/Redo, Request Queuing & Logging - Quiz 5medium Decorator Pattern - Wrapping Behaviour Without Subclassing - Decorator Pattern - Wrapping Behaviour Without Subclassing - Quiz 10hard Design Snake and Ladder Game - LLD End-to-End - Design Snake and Ladder Game - LLD End-to-End - Quiz 15hard Design a Parking Lot - LLD with OOP (Classes, Patterns, Extensibility) - Design a Parking Lot - LLD with OOP (Classes, Patterns, Extensibility) - Quiz 8hard Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Quiz 11easy Iterator & Composite Pattern - Traversal Abstractions - Iterator & Composite Pattern - Traversal Abstractions - Quiz 8hard Liskov Substitution Principle - Subtype Behavioural Contract - Liskov Substitution Principle - Subtype Behavioural Contract - Quiz 14medium Open/Closed Principle - Open for Extension, Closed for Modification - Open/Closed Principle - Open for Extension, Closed for Modification - Quiz 4medium