Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam ATTA 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

Contribute your Thoughts:

Fairy
2 months 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
2 months 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
21 days ago
D) Priority, version of software under test, date to be fixed
upvoted 0 times
...
Chan
1 months ago
C) Developer assigned to the fix, version of software under test, incident identification
upvoted 0 times
...
Jolene
1 months ago
B) Date to be fixed, priority, incident identification
upvoted 0 times
...
Marjory
1 months ago
A) Priority, version of software under test, incident identification
upvoted 0 times
...
...
Micheline
2 months 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
2 months 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 months ago
C) Developer assigned to the fix, version of software under test, incident identification
upvoted 0 times
...
Ahmad
1 months ago
B) Date to be fixed, priority, incident identification
upvoted 0 times
...
Jennie
2 months ago
A) Priority, version of software under test, incident identification
upvoted 0 times
...
...
Lourdes
2 months ago
That's a good point, having the developer assigned could be very useful for tracking the incident.
upvoted 0 times
...
Edwin
2 months 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 months ago
I personally think priority, version of software under test, and incident identification are sufficient for our needs.
upvoted 0 times
...
Leslie
1 months ago
True, having the date to be fixed would also be crucial for prioritizing and scheduling the fixes.
upvoted 0 times
...
Germaine
2 months 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
2 months ago
I agree, those fields cover all the important details we need to track.
upvoted 0 times
...
...
Eulah
2 months ago
I disagree, I believe option C is better as it includes developer assigned to the fix.
upvoted 0 times
...
Lourdes
3 months ago
I think option A is the best choice because it includes priority and incident identification.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77