ISTQB CT-TAE Exam - Topic 8 Question 41 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 41
Topic #: 8

A TAS uses a commercial test automation tool and the default logs generated by the inconsistent formats such as different types of messages (pass/fail steps, screenshots, warnings, etc.) To solve this issue some custom logging functions have been created from the test scripts, making it possible to log the different types of messages with the same format. However, this may cause a problem due to excessive size of the logs which can make it difficult to find the required information. Assume that all the default logs will be disabled when running the automated tests and that some tests will not generate excessively sized logs.

Which of the following represents the BEST suggestion for implementing the custom logging functions?

AImplement the custom logging functions without saving timestamps

BImplement the custom logging functions to support different levels of tracing

CImplement the custom logging functions without saving stack traces

DImplement the custom logging functions to redirect the logs to multiple files

Show Suggested Answer

Suggested Answer: D

by Ressie at Sep 17, 2024, 03:09 PM

Limited Time Offer

25%

Off

Get Premium CT-TAE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Candida

6 months ago

I vote for option B too, it just makes sense for debugging.

upvoted 0 times

...

Layla

6 months ago

Option A seems risky, no timestamps could lead to confusion.

upvoted 0 times

...

Tiffiny

6 months ago

Surprised that timestamps aren't considered important in logging!

upvoted 0 times

...

Lashon

7 months ago

Disagree, I feel like option D could help manage log sizes better.

upvoted 0 times

...

Pansy

7 months ago

I think option B is the best choice! Different tracing levels are super useful.

upvoted 0 times

...

Terry

7 months ago

I recall that excessive log sizes can be a problem, but I'm uncertain if not saving stack traces is a good idea. It might be useful for debugging later on.

upvoted 0 times

...

Theodora

7 months ago

I'm not entirely sure, but I feel like redirecting logs to multiple files could help manage the size issue. It might make it easier to find specific information.

upvoted 0 times

...

Stefania

7 months ago

I think option B makes sense because supporting different levels of tracing would help in filtering out the noise from the logs. We practiced something similar in our last mock exam.

upvoted 0 times

...

Willodean

8 months ago

I remember we discussed the importance of having timestamps in logs during our last practice session. It seems like not saving them could lead to confusion later on.

upvoted 0 times

...

Glynda

8 months ago

This seems straightforward. I'm leaning towards option B as it allows for different levels of tracing, which could help manage the log size.

upvoted 0 times

...

Hayley

8 months ago

I'm a bit confused by the wording of the question. I'll need to re-read it a few times to make sure I understand the context and requirements fully.

upvoted 0 times

...

Brendan

8 months ago

Okay, I think I have a strategy here. I'll focus on the requirement to avoid excessive log sizes and see which option best addresses that.

upvoted 0 times

...

Silvana

8 months ago

Hmm, the key seems to be finding a way to manage the log size while still capturing the necessary information. I'll need to think through the different approaches.

upvoted 0 times

...

Gilberto

8 months ago

This seems like a tricky question. I'll need to carefully consider the pros and cons of each option.

upvoted 0 times

...

Kina

8 months ago

Hmm, I'm not totally sure what the "components" are referring to here. I'll have to think this through carefully.

upvoted 0 times

...

Pedro

1 year ago

Imagine if we implemented the custom logging without stack traces. How are we supposed to figure out where the issues are? Option B is the clear winner here.

upvoted 0 times

...

Emilio

1 year ago

Option D might work, but then we'd have to deal with managing multiple log files. That sounds like a hassle. I'd rather just use the different log levels from Option B.

upvoted 0 times

Glenn

11 months ago

Yeah, Option B sounds like a more efficient solution. It would make it easier to trace and find the required information in the logs.

upvoted 0 times

...

Hyman

12 months ago

I agree, managing multiple log files could be a hassle. Using different log levels from Option B seems like a better choice.

upvoted 0 times

...

Rueben

12 months ago

Option D might work, but then we'd have to deal with managing multiple log files. That sounds like a hassle.

upvoted 0 times

...

Francis

1 year ago

Haha, I can already imagine the logs getting out of control without timestamps. It's like trying to debug a problem without a clock! Option B is definitely the way to go.

upvoted 0 times

Antione

12 months ago

I think redirecting logs to multiple files can also be a good option to prevent excessive size.

upvoted 0 times

...

Tamala

1 year ago

Yeah, having different levels of tracing can help manage the logs more effectively.

upvoted 0 times

...

Cecily

1 year ago

I agree, timestamps are crucial for tracking the sequence of events.

upvoted 0 times

...

Penney

1 year ago

I agree with Florencia. Having different log levels is crucial to managing the size of the logs and ensuring we can easily find the necessary information.

upvoted 0 times

Leontine

12 months ago

User4: Implementing custom logging functions with different levels of tracing sounds like the best solution.

upvoted 0 times

...

Irma

12 months ago

User3: I agree. Having different log levels is crucial for efficient logging.

upvoted 0 times

...

Ashanti

1 year ago

User2: That's a good point. It will help manage the size of the logs and make it easier to find information.

upvoted 0 times

...

Aaron

1 year ago

User1: I think we should implement the custom logging functions to support different levels of tracing.

upvoted 0 times

...

Linn

1 year ago

That's a good point, having logs in multiple files can definitely help in avoiding excessively sized logs and make it easier to find the required information.

upvoted 0 times

...

Derick

1 year ago

I disagree, I believe option D is better as redirecting logs to multiple files can help in organizing and managing the logs more effectively.

upvoted 0 times

...

Linn

1 year ago

I think option B is the best suggestion because it allows for different levels of tracing which can help in filtering the logs.

upvoted 0 times

...

Florencia

1 year ago

Option B is the best choice here. Implementing custom logging functions with different levels of tracing will allow us to control the granularity of the logs and focus on the most relevant information.

upvoted 0 times