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 ISTQB-CTFL Topic 5 Question 21 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam
Question #: 21
Topic #: 5
[All ISTQB-CTFL Questions]

Which or the following would be a key difference between a peer review of code and static analysis of code using a tool?

Show Suggested Answer Hide Answer
Suggested Answer: B

The key difference between a peer review of code and static analysis of code using a tool lies in their approaches and scope. A peer review is a manual inspection of the code by peers or colleagues, focusing not only on the technical aspects of the code but also on other elements such as design, compliance with standards, and maintainability. Peer reviews can identify defects, suggest improvements, and ensure that the code adheres to best practices and team standards.

On the other hand, static analysis is an automated process performed by tools designed to analyze the code without executing it. These tools can detect potential issues such as syntax errors, vulnerabilities, and code smells based on predefined rules and patterns. While static analysis is technically focused, it lacks the broader perspective that human reviewers can provide, such as evaluating the code's maintainability or adherence to project-specific standards. Therefore, static analysis targets the code technically, whereas peer review encompasses a wider range of aspects, making option B the correct answer.


Contribute your Thoughts:

Cecily
6 months ago
This is a tough one, but I'm leaning towards B. Peer review is more holistic, while static analysis is all about the nitty-gritty of the code itself.
upvoted 0 times
...
Katy
6 months ago
Haha, I bet the exam writers are having a field day coming up with these tricky options. I'm going with C - static analysis can definitely catch missing requirements that a peer review might miss.
upvoted 0 times
Francisca
5 months ago
I agree with you, C seems like the best choice here.
upvoted 0 times
...
Benedict
5 months ago
I'm leaning towards A, peer reviews find defects while static analysis finds failures.
upvoted 0 times
...
Cyndy
6 months ago
I think C is the correct answer too. Static analysis can definitely catch missing requirements.
upvoted 0 times
...
...
Luther
6 months ago
D seems like the correct answer to me. Peer reviews identify failures in the code, while static analysis tools find specific defects.
upvoted 0 times
Dottie
5 months ago
D) A peer reviews find failures while static analysis finds defects.
upvoted 0 times
...
Lyda
5 months ago
A) A peer reviews finds defects while static analysis finds failures.
upvoted 0 times
...
Gregoria
5 months ago
Yes, that's right. Peer reviews and static analysis serve different purposes in identifying issues in code.
upvoted 0 times
...
Ty
6 months ago
Yes, that's right. Peer reviews and static analysis serve different purposes in identifying issues in code.
upvoted 0 times
...
Madonna
6 months ago
I think D is the correct answer too. Peer reviews focus on finding failures, while static analysis tools look for defects.
upvoted 0 times
...
Thaddeus
6 months ago
I think D is the correct answer too. Peer reviews focus on finding failures, while static analysis tools focus on defects.
upvoted 0 times
...
...
Margurite
7 months ago
I think option B is the right answer. Static analysis is all about the technical aspects of the code, while peer review looks at broader aspects like requirements and design.
upvoted 0 times
Erin
6 months ago
I see, it's important to have a combination of both approaches for a thorough code review process.
upvoted 0 times
...
Frankie
6 months ago
So, would you say that both peer review and static analysis are important in ensuring code quality?
upvoted 0 times
...
Magnolia
6 months ago
Definitely, they complement each other in identifying different types of issues in the code.
upvoted 0 times
...
Gail
6 months ago
I think option A is correct. Peer reviews find defects, while static analysis finds failures.
upvoted 0 times
...
Ezekiel
6 months ago
Yes, static analysis does focus on technical aspects, but peer review goes beyond that to consider other factors.
upvoted 0 times
...
Tonja
6 months ago
I agree, option B makes sense. Peer review is more holistic compared to static analysis.
upvoted 0 times
...
Rhea
7 months ago
But doesn't static analysis also help in finding technical issues in the code?
upvoted 0 times
...
Jamal
7 months ago
I agree, option B makes sense. Peer review is more holistic compared to static analysis.
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