ISTQB CTAL-TTA Exam - 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

Annamaria

3 months ago

Connection pooling (A) could also be a good option to consider.

upvoted 0 times

...

Beula

3 months ago

Wait, are we really sure this will fix the performance issues?

upvoted 0 times

...

Jaime

3 months ago

Not sure about that, caching (D) might be more effective.

upvoted 0 times

...

Thora

4 months ago

I think lazy instantiation (C) is the best choice here.

upvoted 0 times

...

Jules

4 months ago

Change 1 sounds solid, multiple servers should help a lot.

upvoted 0 times

...

Vesta

4 months ago

I practiced a similar question about optimizing database access, and I think lazy instantiation is definitely the best fit for identifying defects in Change 2.

upvoted 0 times

...

Leigha

4 months ago

I feel like caching could be important too, but it seems more related to improving data retrieval speed rather than preventing unnecessary calls.

upvoted 0 times

...

Aretha

4 months ago

I'm not entirely sure, but I think connection pooling might be more relevant for managing database connections efficiently rather than directly addressing the issue in Change 2.

upvoted 0 times

...

Brunilda

5 months ago

I remember we discussed lazy instantiation in class, and it seems like it would help with Change 2 since it delays database connections until needed.

upvoted 0 times

...

Luis

5 months ago

I think the answer is C - Lazy instantiation. That seems like the most relevant approach to preventing unnecessary database calls, so I'll go with that.

upvoted 0 times

...

Luisa

5 months ago

I'm a bit confused by the wording here. I'll need to re-read the question and the changes carefully to make sure I understand what I'm looking for.

upvoted 0 times

...

Lashaun

5 months ago

Alright, I've got a strategy. I'll focus on how the system is managing database connections and when they're being created. That should help me spot any potential problems.

upvoted 0 times

...

Gretchen

5 months ago

Okay, let's see here. The key seems to be identifying any potential issues with the database calls and how they're being handled. I'll need to think this through.

upvoted 0 times

...

Caprice

5 months ago

Hmm, this one seems tricky. I'll need to carefully consider the changes being made and how to best review them.

upvoted 0 times

...

Leonard

10 months ago

I bet the correct answer is something completely unexpected, like data replication. You know, just to keep us on our toes. But hey, at least they're not asking us to design a hotel booking website from scratch. That would be a real nightmare!

upvoted 0 times

Dean

9 months ago

C) Lazy instantiation

upvoted 0 times

...

Kayleigh

9 months ago

B) Data replication

upvoted 0 times

...

Jacquline

9 months ago

A) Connection pooling

upvoted 0 times

...

Sabrina

10 months ago

Lazy instantiation, huh? Sounds like a fancy way of saying 'only do the bare minimum required.' I like it! Now, if only I could apply that principle to my life in general...

upvoted 0 times

Latricia

9 months ago

C) Lazy instantiation

upvoted 0 times

...

Mertie

9 months ago

B) Data replication

upvoted 0 times

...

Hildegarde

9 months ago

A) Connection pooling

upvoted 0 times

...

Xochitl

10 months ago

I'm just hoping they don't expect us to come up with some crazy, overly complex solution. Caching sounds like a reasonable approach, but I'm not sure if it's the 'most likely' to identify defects in Change 2. Ah well, guess I'll have to think this one through.

upvoted 0 times

Ira

8 months ago

D) Caching

upvoted 0 times

...

Cristal

9 months ago

C) Lazy instantiation

upvoted 0 times

...

Trinidad

9 months ago

B) Data replication

upvoted 0 times

...

Garry

10 months ago

A) Connection pooling

upvoted 0 times

...

Gerri

10 months ago

Hmm, I'm not too sure about this one. Wouldn't connection pooling be a better option? That way, we can reuse existing connections instead of constantly opening and closing them. Seems more efficient to me.

upvoted 0 times

...

Corrie

10 months ago

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

upvoted 0 times

...

Lanie

11 months 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