Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB CTAL-TTA Exam - Topic 1 Question 29 Discussion

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

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?

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.


Get Premium CTAL-TTA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
36 comments · newest first
AN
Annamaria 10 months ago
Connection pooling (A) could also be a good option to consider.
BE
Beula 11 months ago
Wait, are we really sure this will fix the performance issues?
JA
Jaime 11 months ago
Not sure about that, caching (D) might be more effective.
TH
Thora 11 months ago
I think lazy instantiation (C) is the best choice here.
JU
Jules 11 months ago
Change 1 sounds solid, multiple servers should help a lot.
VE
Vesta 12 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.
LE
Leigha 12 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.
AR
Aretha 12 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.
BR
Brunilda 1 year 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.
LU
Luis 1 year 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.
LU
Luisa 1 year 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.
LA
Lashaun 1 year 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.
GR
Gretchen 1 year 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.
CA
Caprice 1 year ago
Hmm, this one seems tricky. I'll need to carefully consider the changes being made and how to best review them.
LE
Leonard 1 year 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!
DE
Dean 1 year ago
↳ replying to Leonard
C) Lazy instantiation
KA
Kayleigh 1 year ago
↳ replying to Leonard
B) Data replication
JA
Jacquline 1 year ago
↳ replying to Leonard
A) Connection pooling
SA
Sabrina 1 year 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...
LA
Latricia 1 year ago
↳ replying to Sabrina
C) Lazy instantiation
ME
Mertie 1 year ago
↳ replying to Sabrina
B) Data replication
HI
Hildegarde 1 year ago
↳ replying to Sabrina
A) Connection pooling
XO
Xochitl 1 year 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.
IR
Ira 1 year ago
↳ replying to Xochitl
D) Caching
CR
Cristal 1 year ago
↳ replying to Xochitl
C) Lazy instantiation
TR
Trinidad 1 year ago
↳ replying to Xochitl
B) Data replication
GA
Garry 1 year ago
↳ replying to Xochitl
A) Connection pooling
GE
Gerri 1 year 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.
CO
Corrie 1 year ago
I'm not sure, but I think connection pooling might also be important for Change 2.
LA
Lanie 2 years 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.
CR
Cristal 1 year ago
↳ replying to Lanie
Caching might also play a role in optimizing database calls and improving system performance.
LI
Lizette 1 year ago
↳ replying to Lanie
I agree, lazy instantiation will definitely help in improving system performance during peak volumes.
CA
Carolynn 1 year ago
↳ replying to Lanie
Connection pooling could also be important to consider for optimizing database connections.
CR
Crista 1 year ago
↳ replying to Lanie
Lazy instantiation is definitely the key here. It will help in reducing unnecessary database calls.
JO
Johana 2 years ago
I agree with Gwen, lazy instantiation would be crucial for detecting issues in the proposed system architecture.
GW
Gwen 2 years ago
I think lazy instantiation could help identify defects in Change 2.
0/2000 characters

Save Cancel