CTAL-TTA_001 · Question #16
Part 1 "Test Techniques various" Consider the following fault attack: "Force all possible incoming errors from the software/OS interfaces to the application". Which of the following is the kind of…
The correct answer is A. Application crashes when unsupported characters are pasted into an input field using the. Option A is correct because the fault attack described targets error handling at system/OS interface boundaries - specifically, what happens when invalid or unexpected inputs flow in from those interfaces. Pasting unsupported characters into a field is exactly this scenario…
Question
Part 1 "Test Techniques various" Consider the following fault attack: “Force all possible incoming errors from the software/OS interfaces to the application”. Which of the following is the kind of failure you are looking for when using this attack? 1 credit [K2]
Options
- AApplication crashes when unsupported characters are pasted into an input field using the
- BFront page of the application has incorrect spelling of the company name
- CApplication fails to display financial numbers in the correct currency format in reports
- DApplication miscalculates total monthly balance due on credit cards
How the community answered
(52 responses)- A90% (47)
- B2% (1)
- C6% (3)
- D2% (1)
Explanation
Option A is correct because the fault attack described targets error handling at system/OS interface boundaries - specifically, what happens when invalid or unexpected inputs flow in from those interfaces. Pasting unsupported characters into a field is exactly this scenario: the clipboard (an OS interface) delivers unexpected data, and the application crashing reveals a failure to handle errors from that interface gracefully.
Options B, C, and D are all functional defects, not fault-handling failures: incorrect spelling (B) is a content/QA defect, wrong currency format (C) is a localization/formatting defect, and miscalculated balance (D) is a business logic defect. None of these result from the application failing to cope with erroneous input injected from software or OS interfaces.
Memory tip: The key phrase is "errors from software/OS interfaces" - think crash-on-bad-input, not wrong-output-on-valid-input. If the application processes valid data and returns the wrong result, that's a functional bug. If it receives hostile/invalid data from an interface and falls over, that's what this fault attack is hunting.
Topics
Community Discussion
No community discussion yet for this question.