New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ISTQB ATTA Exam - Topic 1 Question 98 Discussion

Actual exam question for ISTQB's ATTA exam
Question #: 98
Topic #: 1
[All ATTA Questions]

You have now also been given the task to identify the key fields for logging the incident reports. So far the following fields have been in use in the Excel sheet:

Incident description

Date

Author

State

Which of the following would you recommend as the best combination of fields to add? 1 credit [K2]

Show Suggested Answer Hide Answer
Suggested Answer: A

by Mabelle at Sep 15, 2024, 05:44 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Marya
3 months ago
Option B seems a bit off to me.
upvoted 0 times
...
Demetra
3 months ago
Wait, why is incident identification not in all options?
upvoted 0 times
...
Ammie
3 months ago
Not sure about the version of software being necessary.
upvoted 0 times
...
Nu
4 months ago
Totally agree, priority and fix date are key!
upvoted 0 times
...
Tammy
4 months ago
I think option D makes the most sense.
upvoted 0 times
...
Lachelle
4 months ago
I’m leaning towards option D because it includes both priority and a timeline for fixing, but I’m not completely confident.
upvoted 0 times
...
Alisha
4 months ago
This question seems similar to one we practiced about incident management fields. I think "date to be fixed" is important too.
upvoted 0 times
...
Amie
4 months ago
I'm not entirely sure, but I feel like "developer assigned to the fix" could help track accountability better.
upvoted 0 times
...
Sheron
5 months ago
I remember we discussed the importance of prioritizing incidents, so I think options with "priority" are crucial.
upvoted 0 times
...
Carman
5 months ago
Option C looks interesting, but I'm not sure how useful the "developer assigned to the fix" field would be. Seems like that could change over time. I think I'll go with A - it covers the essentials without getting too complicated.
upvoted 0 times
...
Shonda
5 months ago
I'm a little confused by this question. What's the difference between "incident identification" and "priority"? Aren't they kind of the same thing? I'll have to think about this one a bit more.
upvoted 0 times
...
Brigette
5 months ago
Hmm, I'm a bit torn between A and D. Both seem like good options, but I'm not sure if we really need the "date to be fixed" field. Maybe I'll go with A just to be safe.
upvoted 0 times
...
Jesusa
5 months ago
This seems like a straightforward question. I'd go with option A - priority, version of software under test, and incident identification. That covers the key details we need to track and manage the incident reports effectively.
upvoted 0 times
...
Iola
5 months ago
Hmm, I'm not sure about this one. I'm thinking option D might be the best choice - recording the audio could help the student review it later and catch anything they missed. But I'm also wondering if manipulating the seating arrangement could work. I'll have to think this through a bit more.
upvoted 0 times
...
Fairy
1 year ago
Priority, version, and date to be fixed? That's like the incident report version of 'location, location, location'. I think we're overthinking this.
upvoted 0 times
...
Peggie
1 year ago
Wait, are we logging incidents or planning a lunar mission? This seems a bit overkill. Let's stick to the essentials and save the bells and whistles for another day.
upvoted 0 times
Dannie
1 year ago
D) Priority, version of software under test, date to be fixed
upvoted 0 times
...
Chan
1 year ago
C) Developer assigned to the fix, version of software under test, incident identification
upvoted 0 times
...
Jolene
1 year ago
B) Date to be fixed, priority, incident identification
upvoted 0 times
...
Marjory
1 year ago
A) Priority, version of software under test, incident identification
upvoted 0 times
...
...
Micheline
1 year ago
Developer assigned to the fix? Sounds like we're creating more work for ourselves. Let's keep it simple - priority, version, and ID are probably all we need.
upvoted 0 times
...
Shoshana
1 year ago
Hmm, I'm not sure 'date to be fixed' is super useful. Wouldn't 'date reported' or 'date resolved' be more relevant?
upvoted 0 times
Denny
1 year ago
C) Developer assigned to the fix, version of software under test, incident identification
upvoted 0 times
...
Ahmad
1 year ago
B) Date to be fixed, priority, incident identification
upvoted 0 times
...
Jennie
1 year ago
A) Priority, version of software under test, incident identification
upvoted 0 times
...
...
Lourdes
1 year ago
That's a good point, having the developer assigned could be very useful for tracking the incident.
upvoted 0 times
...
Edwin
1 year ago
Priority, version of software under test, and incident identification seem like a pretty well-rounded set of fields to me. Covers the key details I'd want to track.
upvoted 0 times
Rhea
1 year ago
I personally think priority, version of software under test, and incident identification are sufficient for our needs.
upvoted 0 times
...
Leslie
1 year ago
True, having the date to be fixed would also be crucial for prioritizing and scheduling the fixes.
upvoted 0 times
...
Germaine
1 year ago
I think adding the developer assigned to the fix could also be helpful in tracking the progress of the incident.
upvoted 0 times
...
Haley
1 year ago
I agree, those fields cover all the important details we need to track.
upvoted 0 times
...
...
Eulah
1 year ago
I disagree, I believe option C is better as it includes developer assigned to the fix.
upvoted 0 times
...
Lourdes
1 year ago
I think option A is the best choice because it includes priority and incident identification.
upvoted 0 times
...

Save Cancel