ISTQB Exam CTAL-TTA Topic 1 Question 29 Discussion

Actual exam question for ISTQB's CTAL-TTA exam

Question #: 29
Topic #: 1

The last release of a hotel booking website resulted in poor system performance when hotel searches reached peak volumes. To address these problems in the forthcoming release, changes to the system architecture are to be implemented as follows:

Change 1 - Provision of a single Internet service using multiple servers, rather than a single server, to maximize throughput and minimize response time during peak volumes

Change 2 - Prevention of unnecessary database calls for objects that were not immediately needed by the calling applications. Achieved by not automatically creating database connections at the start of processing, instead only just before the data is required.

The system architecture document has been drafted and as Technical Test Analyst you have been invited to participate in its review. Which of the following review checklist items is MOST likely to identify any defects in the proposed system architecture for Change 2?

AConnection pooling

BData replication

CLazy instantiation

DCaching

Show Suggested Answer

Suggested Answer: A

Preparing for a code review is essential for understanding how the specific item under review interacts with other system components. This preparation allows the reviewer to identify potential integration issues or dependencies that could affect system functionality or performance. Adequate preparation ensures that the review is thorough and considers the broader system context, which is critical for ensuring that the system operates cohesively and according to specifications.

by Izetta at Jan 14, 2025, 08:40 PM

Limited Time Offer

25%

Off

Get Premium CTAL-TTA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Corrie

4 days ago

I'm not sure, but I think connection pooling might also be important for Change 2.

upvoted 0 times

...

Lanie

10 days ago

Ah, I see, Change 2 is all about optimizing database connections. Lazy instantiation seems like the way to go here - only creating connections when the data is actually needed. That should help reduce the unnecessary overhead.

upvoted 0 times

...

Johana

13 days ago

I agree with Gwen, lazy instantiation would be crucial for detecting issues in the proposed system architecture.

upvoted 0 times

...

Gwen

14 days ago

I think lazy instantiation could help identify defects in Change 2.

upvoted 0 times

...