A municipal yard-waste tester wants to execute a freshly generated keyword script in the shared garage because it compiled cleanly. Given malicious code generation as a named risk, what is the correct stance?
Select an answer to reveal the explanation.
Short Explanation
Compiling is like a door that closes — it does not mean nothing dangerous is behind it. Generated scripts still need a human or structured review before they run. Malicious code generation is why “it built” is not “it is safe.”
Full Explanation
Because malicious code generation is a recognized GenAI security vector, testers must review generated code before execution. Successful compilation only shows syntactic buildability, not the absence of harmful side effects. Systematic review is the required mitigation stance for this risk.