Learn Design Patterns – Module 3 Lesson 1 – Quiz

Quiz Summary

0 of 5 Questions completed

Questions:

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 5 Questions answered correctly

You have reached 0 of 0 point(s), (0)

Question 1 of 5

1. Question

What does the Strategy pattern encapsulate, and what specific problem in the TaskScheduler example does it directly address?

A set of interchangeable data access methods that differ only in persistence mechanism
Correct Incorrect Correct answer

A family of interchangeable algorithms sharing the same purpose, replacing a branching method that grows every time a new algorithm is added
Correct Incorrect Correct answer

A fixed algorithm skeleton with variable steps that subclasses can override
Correct Incorrect Correct answer

A request object that carries metadata about who triggered the calculation and when
Correct Incorrect Correct answer

Correct

Incorrect
Question 2 of 5

2. Question

Which three participants make up the GoF Strategy pattern? (select all that apply)

Context – holds a reference to a Strategy and delegates the algorithm to it
Correct Incorrect Correct answer

AbstractFactory – creates families of related objects
Correct Incorrect Correct answer

Strategy – the interface declaring the operation common to all algorithms
Correct Incorrect Correct answer

ConcreteStrategy – a class implementing the Strategy interface with a specific algorithm
Correct Incorrect Correct answer

Correct

Incorrect
Question 3 of 5

3. Question

Which two SOLID principles does the lesson identify as having a strong, natural connection with the Strategy pattern? (select all that apply)

Open/Closed Principle – TaskScheduler is closed for modification but open for extension by adding new strategy implementations
Correct Incorrect Correct answer

Liskov Substitution Principle – every concrete strategy must implement all methods of the Strategy interface
Correct Incorrect Correct answer

Dependency Inversion Principle – both TaskScheduler and the concrete strategies depend on the TaskPriorityStrategy abstraction
Correct Incorrect Correct answer

Interface Segregation Principle – TaskPriorityStrategy is split into smaller, purpose-specific sub-interfaces
Correct Incorrect Correct answer

Correct

Incorrect
Question 4 of 5

4. Question

What makes TaskPriorityStrategy compatible with a lambda expression?

It is annotated with @FunctionalInterface
Correct Incorrect Correct answer

It extends java.util.function.Function<Task, Integer>
Correct Incorrect Correct answer

It has a single abstract method, making it a functional interface
Correct Incorrect Correct answer

All its methods are declared default except for the single abstract one used for lambda binding
Correct Incorrect Correct answer

Correct

Incorrect
Question 5 of 5

5. Question

How does the lesson distinguish the Strategy pattern from the Template Method pattern?

Strategy uses inheritance so subclasses override specific steps of a fixed algorithm skeleton; Template Method uses composition to swap the entire algorithm
Correct Incorrect Correct answer

Strategy uses composition – the context holds and delegates to a strategy; Template Method uses inheritance – a subclass overrides specific steps of a fixed skeleton
Correct Incorrect Correct answer

Strategy is suited for purely stateless algorithms; Template Method is suited for algorithms that require mutable context
Correct Incorrect Correct answer

Strategy requires a lambda-compatible interface; Template Method requires an abstract class with multiple abstract methods
Correct Incorrect Correct answer

Correct

Incorrect

Learn Design Patterns – Module 3 Lesson 1 – Quiz

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question

4. Question

5. Question