Q: 2
Which of the following will BEST help mitigate the risk associated with malicious functionality in
outsourced application development?
Options
Discussion
Option A. saw a similar question in exam reports and code review by an expert was the right pick.
A makes the most sense. Only an expert code review will catch hidden malicious code before it goes live, which is exactly what the question focuses on. SLAs and test environments help but aren't as targeted for this risk. Pretty sure A's right, but let me know if you see it differently.
B or A? I get why A is strong, but if the question meant catching stuff only once it's running, validating in a test environment (B) should catch malicious behavior that’s not obvious in code. Kind of depends if you have black-box apps, too. Thoughts?
A and I've seen similar in official practice questions. Code review is highlighted in the ISACA manual.
B , since test environments can catch issues that code reviews might miss, especially if the malicious code is only triggered under certain conditions. A feels like a strong pick, but sometimes dynamic analysis finds traps.
Its A since only a deep code review by an expert would spot intentionally hidden malicious code in outsourced development. Test environments (B) might miss logic bombs or backdoors. Pretty confident, but curious if anyone has seen B accepted.
Ugh, ISACA and their "BEST" wording again... A imo
A
A
Nah, B is tempting but some malicious code hides pretty well from just black-box testing. A.
Be respectful. No spam.