MENU
A developer has spent three days looking at a system that crashes now and then. The problem was caused by two coding faults:
i. A variable was being used but had not been defined;
ii. There was a 'goto' statement to an undefined label
1 credit [K2]
Suggested Answer: A
Get Premium ATTA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
MA
Mary
11 months ago
Wait, are people still using goto? That's surprising!
TA
Tammara
11 months ago
Agreed, static analysis would catch those errors easily.
OD
Odette
11 months ago
I thought goto statements were a thing of the past?
BR
Brande
11 months ago
Definitely a static analysis tool issue.
KI
Kiley
12 months ago
Sounds like a classic case of undefined variables!
LO
Louisa
12 months ago
I could be wrong, but I think a test execution tool is more about running tests rather than finding coding faults like the ones mentioned.
RO
Roxane
12 months ago
This reminds me of a practice question where we had to identify tools for different types of errors. I feel like a code coverage tool wouldn't help with these specific coding faults.
MA
Marti
1 year ago
I'm not entirely sure, but I think dynamic analysis tools are more about runtime behavior. This question seems to focus on catching issues before execution.
FR
Frederic
1 year ago
I remember we discussed static analysis tools in class, and they can catch undefined variables before runtime. I think that might be the right choice here.
TI
Tiffiny
1 year ago
This looks like a straightforward question about wireless encryption protocols. I think the answer is WPA PSK/WPA2 PSK, since that allows a simple passkey without needing an 802.1X authentication server.
AR
Arlette
1 year ago
Hmm, this looks straightforward. I think options A and C are the way to go here.