OOP · Advanced & Patterns interview questions

1. A.a behavioral pattern where subjects notify a list of dependent observers automatically on state change
2. B.an architecture splitting an application into Model data, View presentation, and Controller logic
3. C.the SOLID rule that software should be open for extension but closed for modification
4. D.a general relationship where one object uses or knows about another, with independent lifetimes

Answer + AI explanation with a free account

1. A.cohesion
2. B.open-closed principle
3. C.association
4. D.shallow vs deep copy

Answer + AI explanation with a free account

1. A.association — the degree of interdependence between modules, which good design keeps low
2. B.association — a creational pattern that delegates object creation to a method so callers need not name concrete classes
3. C.association — a general relationship where one object uses or knows about another, with independent lifetimes
4. D.association — the SOLID rule that a subtype must be usable anywhere its base type is expected without breaking behavior

Answer + AI explanation with a free account

1. A.a general relationship where one object uses or knows about another, with independent lifetimes
2. B.an architecture splitting an application into Model data, View presentation, and Controller logic
3. C.a shallow copy duplicates references to shared sub-objects, while a deep copy clones the entire object graph
4. D.a has-a relationship where the part can exist independently of the whole that contains it

Answer + AI explanation with a free account

1. A.singleton pattern
2. B.aggregation
3. C.factory pattern
4. D.coupling

Answer + AI explanation with a free account

1. A.aggregation — the SOLID rule that software should be open for extension but closed for modification
2. B.aggregation — a has-a relationship where the part can exist independently of the whole that contains it
3. C.aggregation — supplying an object's required collaborators from outside rather than having it construct them itself
4. D.aggregation — a strong has-a relationship where the part's lifetime is owned by and tied to the whole

Answer + AI explanation with a free account

1. A.the degree to which a module's elements belong together, which good design keeps high
2. B.the SOLID rule that software should be open for extension but closed for modification
3. C.a creational pattern that delegates object creation to a method so callers need not name concrete classes
4. D.a strong has-a relationship where the part's lifetime is owned by and tied to the whole

Answer + AI explanation with a free account

1. A.composition
2. B.cohesion
3. C.factory pattern
4. D.MVC pattern

Answer + AI explanation with a free account

1. A.composition — the degree to which a module's elements belong together, which good design keeps high
2. B.composition — a strong has-a relationship where the part's lifetime is owned by and tied to the whole
3. C.composition — the SOLID rule that modules should depend on abstractions, not on concrete implementations
4. D.composition — the SOLID rule that software should be open for extension but closed for modification

Answer + AI explanation with a free account

1. A.a strong has-a relationship where the part's lifetime is owned by and tied to the whole
2. B.the SOLID rule that software should be open for extension but closed for modification
3. C.the degree of interdependence between modules, which good design keeps low
4. D.a has-a relationship where the part can exist independently of the whole that contains it

Answer + AI explanation with a free account

1. A.MVC pattern
2. B.coupling
3. C.single responsibility principle
4. D.Liskov substitution principle

Answer + AI explanation with a free account

1. A.coupling — the degree of interdependence between modules, which good design keeps low
2. B.coupling — a shallow copy duplicates references to shared sub-objects, while a deep copy clones the entire object graph
3. C.coupling — a has-a relationship where the part can exist independently of the whole that contains it
4. D.coupling — a creational pattern that delegates object creation to a method so callers need not name concrete classes

Answer + AI explanation with a free account

1. A.the degree to which a module's elements belong together, which good design keeps high
2. B.supplying an object's required collaborators from outside rather than having it construct them itself
3. C.a general relationship where one object uses or knows about another, with independent lifetimes
4. D.the SOLID rule that clients should not be forced to depend on methods they do not use

Answer + AI explanation with a free account

1. A.interface segregation principle
2. B.observer pattern
3. C.cohesion
4. D.coupling

Answer + AI explanation with a free account

1. A.cohesion — the SOLID rule that clients should not be forced to depend on methods they do not use
2. B.cohesion — an architecture splitting an application into Model data, View presentation, and Controller logic
3. C.cohesion — a shallow copy duplicates references to shared sub-objects, while a deep copy clones the entire object graph
4. D.cohesion — the degree to which a module's elements belong together, which good design keeps high

Answer + AI explanation with a free account

1. A.an architecture splitting an application into Model data, View presentation, and Controller logic
2. B.the SOLID rule that a class should have only one reason to change
3. C.a general relationship where one object uses or knows about another, with independent lifetimes
4. D.a has-a relationship where the part can exist independently of the whole that contains it

Answer + AI explanation with a free account

1. A.cohesion
2. B.single responsibility principle
3. C.shallow vs deep copy
4. D.interface segregation principle

Answer + AI explanation with a free account

1. A.single responsibility principle — a design pattern ensuring a class has exactly one instance with a global access point
2. B.single responsibility principle — the degree of interdependence between modules, which good design keeps low
3. C.single responsibility principle — supplying an object's required collaborators from outside rather than having it construct them itself
4. D.single responsibility principle — the SOLID rule that a class should have only one reason to change

Answer + AI explanation with a free account

1. A.a has-a relationship where the part can exist independently of the whole that contains it
2. B.a behavioral pattern where subjects notify a list of dependent observers automatically on state change
3. C.the SOLID rule that software should be open for extension but closed for modification
4. D.the degree of interdependence between modules, which good design keeps low

Answer + AI explanation with a free account

1. A.open-closed principle
2. B.coupling
3. C.aggregation
4. D.Liskov substitution principle

Answer + AI explanation with a free account

1. A.open-closed principle — an architecture splitting an application into Model data, View presentation, and Controller logic
2. B.open-closed principle — the SOLID rule that software should be open for extension but closed for modification
3. C.open-closed principle — a creational pattern that delegates object creation to a method so callers need not name concrete classes
4. D.open-closed principle — a strong has-a relationship where the part's lifetime is owned by and tied to the whole

Answer + AI explanation with a free account

1. A.a shallow copy duplicates references to shared sub-objects, while a deep copy clones the entire object graph
2. B.the SOLID rule that a subtype must be usable anywhere its base type is expected without breaking behavior
3. C.a behavioral pattern where subjects notify a list of dependent observers automatically on state change
4. D.a design pattern ensuring a class has exactly one instance with a global access point

Answer + AI explanation with a free account

1. A.MVC pattern
2. B.singleton pattern
3. C.Liskov substitution principle
4. D.coupling

Answer + AI explanation with a free account

1. A.Liskov substitution principle — a has-a relationship where the part can exist independently of the whole that contains it
2. B.Liskov substitution principle — the SOLID rule that a subtype must be usable anywhere its base type is expected without breaking behavior
3. C.Liskov substitution principle — a general relationship where one object uses or knows about another, with independent lifetimes
4. D.Liskov substitution principle — the SOLID rule that modules should depend on abstractions, not on concrete implementations

Answer + AI explanation with a free account

1. A.supplying an object's required collaborators from outside rather than having it construct them itself
2. B.the SOLID rule that software should be open for extension but closed for modification
3. C.a general relationship where one object uses or knows about another, with independent lifetimes
4. D.the SOLID rule that modules should depend on abstractions, not on concrete implementations

Answer + AI explanation with a free account

1. A.open-closed principle
2. B.Liskov substitution principle
3. C.dependency inversion principle
4. D.shallow vs deep copy

Answer + AI explanation with a free account

1. A.dependency inversion principle — the SOLID rule that clients should not be forced to depend on methods they do not use
2. B.dependency inversion principle — a design pattern ensuring a class has exactly one instance with a global access point
3. C.dependency inversion principle — the SOLID rule that modules should depend on abstractions, not on concrete implementations
4. D.dependency inversion principle — an architecture splitting an application into Model data, View presentation, and Controller logic

Answer + AI explanation with a free account

1. A.the SOLID rule that clients should not be forced to depend on methods they do not use
2. B.an architecture splitting an application into Model data, View presentation, and Controller logic
3. C.a design pattern ensuring a class has exactly one instance with a global access point
4. D.the SOLID rule that modules should depend on abstractions, not on concrete implementations

Answer + AI explanation with a free account

1. A.singleton pattern
2. B.single responsibility principle
3. C.MVC pattern
4. D.interface segregation principle

Answer + AI explanation with a free account

1. A.singleton pattern — an architecture splitting an application into Model data, View presentation, and Controller logic
2. B.singleton pattern — a behavioral pattern where subjects notify a list of dependent observers automatically on state change
3. C.singleton pattern — a design pattern ensuring a class has exactly one instance with a global access point
4. D.singleton pattern — supplying an object's required collaborators from outside rather than having it construct them itself

Answer + AI explanation with a free account