Separation of concerns is violated by:
A) including non-persistent code in all classes.
B) providing persistence related code in all classes.
C) separating code by function.
D) none of the above.

Question

Quizplus · Accepted Answer

Providing persistence related code in all classes violates separation of concerns because it mixes the concerns of data persistence and business logic. This can make maintenance more difficult and increase the likelihood of bugs. Separating persistence-related code into its own layer or class helps to keep concerns separate and maintain code clarity. Choices A and C do not necessarily violate separation of concerns.

Separation of Concerns Is Violated By