Skip to main content

Module Quiz

Complete this quiz after finishing all concept and practice pages. Save your answers before opening separate quiz calibration.

Current Module Questions​

Question 1: Pattern Justification​

A PR introduces a Strategy pattern for a single algorithm that has no planned second implementation. Is this correct?

Question 2: Pattern Combinations​

When is it legitimate to use Strategy, Decorator, and Factory together in one feature?

Question 3: Simple Design Rules​

What is the priority order of Kent Beck's four rules of simple design, and why does the order matter?

Question 4: Evaluate a Review Comment​

A reviewer wrote: "This is messy." Why is this a bad comment, and rewrite it into a good one (invent plausible context)?

Question 5: Receiving Feedback​

A reviewer says "Why didn't you use the existing UserRepository?" and you did have a reason. Outline a response that is neither defensive nor reflexive agreement.

Question 6: ADR Format​

Name the four required sections of a classical ADR and the one optional section this module recommends adding.

Question 7: Evaluate a Design Decision​

You are asked to review an ADR whose "Alternatives Considered" section reads: "None -- this is clearly the best approach." Is this acceptable?

Question 8: When a Diagram Is Warranted​

Give one scenario where a sequence diagram is the right choice and one where it is not.

Question 9: Over- vs. Under-Engineering​

An internal reporting tool used by three engineers adds a ReportRendererStrategy interface with two subclasses, one of which is unused. Is this over- or under-engineered?

Question 10: Testability without Damage​

Why is adding a setClockForTests() method on a production class a design smell?

Question 11: Reversibility​

Label each decision as one-way or two-way, and justify briefly: (a) internal helper function name (b) choice of database engine (c) public API response shape (d) which file a private class lives in

Question 12: PR Shape​

What review risks arise in a 1200-line single-commit PR titled "stuff", and what context matters?

Question 13: Evaluate a Review Workflow​

A team spends 60% of review time on naming and formatting. What concrete change would you propose?

Question 14: Broken Windows​

Why is tolerating a commented-out function and a perpetually skipped test in the codebase a design-level problem?

Question 15: Narrative History​

Give two reasons commit messages matter even if "nobody reads them today."

Interleaved Review Questions​

Prior Module Question 1 (from S3M4: Structural & Creational Patterns)​

What pressure does the Decorator pattern specifically relieve that subclassing cannot?

Prior Module Question 2 (from S3M3: Behavioral Patterns)​

Does adding a third branch automatically justify replacing a switch with Strategy?

Prior Module Question 3 (from S3M2: Refactoring Techniques)​

What is a characterization test and why must it exist before any non-trivial refactor of legacy code?

Prior Module Question 4 (from S3M1: OOD Foundations & Code Smells)​

Name one smell that typically signals low cohesion and one that signals high coupling.

Prior Module Question 5 (from S2)​

Why is writing tests before a refactor typically cheaper than writing them after?

Self-Assessment and Remediation​

Mastery Level (90-100% correct):

  • Quiz readiness only. Advance after AR1–AR6 and the separate HCI/accessibility evidence pass; apply these habits to the semester project.

Proficient Level (75-89% correct):

  • Review only the concept pages tied to missed questions. Redo one practice kata from the area of weakness.

Developing Level (60-74% correct):

  • Rework Practice 2 (Code Review Workshop) and Practice 3 (Design Documentation Clinic) in full. These two deliver the bulk of the module's judgment skills.

Insufficient Level (<60% correct):

  • Return to the concept sequence, starting with Cluster 1 (pattern pressure) and Cluster 2 (review rubric). These are prerequisites for the remaining clusters. Do not advance.

Progression boundary​

Quiz performance calibrates retrieval and reasoning. It does not replace runnable work, changed-case transfer, the module assessment or required semester evidence. Consult practice calibration for the additional independent cases.