The last release of a hotel booking website resulted in poor system performance when hotel...

Analysis:

For Change 2, the goal is to prevent unnecessary database calls by delaying the creation of database connections until they are actually needed. This approach is known as lazy instantiation.

C. Lazy instantiation:

Lazy instantiation is a design pattern that defers the creation of an object until the point at which it is needed. This can help improve performance by reducing unnecessary resource consumption. In the context of database connections, it ensures that connections are only established when required, thus avoiding unnecessary overhead.

Explanation of Incorrect Options:

A. Connection pooling:

Connection pooling involves reusing database connections from a pool rather than creating new ones each time. While this improves efficiency, it does not specifically address the issue of deferring database connections until needed.

B. Data replication:

Data replication refers to copying data across multiple databases to ensure consistency and availability. It is not directly related to managing when database connections are established.

D. Caching:

Caching involves storing frequently accessed data in memory to improve retrieval times. While beneficial for performance, it does not address the specific issue of delaying database connections.

References:

The ISTQB CTAL-TTA syllabus and standard software architecture practices highlight the importance of design patterns such as lazy instantiation for optimizing resource usage and performance.

Sources:

ISTQB-CTAL-TTA Syllabus

General knowledge on software architecture design patterns.