Software Design Patterns and Testing

Strategy pattern lets algorithms vary:

• At compile time only

• Independently at run‑time

• Only via inheritance

• Through global variables

Template Method relies primarily on:

• Interfaces

• Inheritance – defining an algorithm skeleton in a superclass

• Reflection

• Event sourcing

In Command vs Strategy, which focuses on what needs to be done rather than how?

• Command

• Strategy

• Both equally

• Neither

A proxy is often used to:

• Convert data formats

• Control access or add indirection when calling an expensive object

• Represent inheritance

• Flatten hierarchies

A series of automated build‑test‑deploy steps is known as a:

• Release plan

• Deployment pipeline

• Roadmap

• Waterfall

Which deployment strategy maintains two identical production environments and routes traffic between them?

• Canary

• Blue‑Green

• Rolling

• Big‑bang

Validation testing seeks to answer:

• Are we building it right?

• Are we building the right product?

• Is code coverage 100 %?

• Have we removed all defects?

Unit testing should focus primarily on:

• Network latency

• Functionality of individual objects/methods

• GUI colours

• Whole‑system scalability

In the three major testing stages, release testing is carried out by:

• Developers

• A separate testing team

• Customers

• Automation only

The rollback mechanism in deployment exists to:

• Reduce compilation time

• Return safely to a previous version on failure

• Increase load balancer speed

• Delay user feedback