Value of Static Testing CTFL Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A team is considering using only static testing to validate a new web application before release. Which limitation of static testing should the team consider?

   • AIt cannot be applied to requirements documents.
   • BIt cannot detect defects that require the application to be executed.
   • CIt requires a fully automated test environment.
   • DIt is only useful for finding syntax errors.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A team is developing a safety-critical system. They have performed extensive static testing, including code reviews and static analysis, and found no defects. The project manager wants to release the system without dynamic testing to save time. What is the most appropriate response?

   • ARelease the system because static testing is sufficient for safety-critical systems.
   • BRelease the system but monitor it closely after release.
   • CPerform more static testing to cover runtime scenarios.
   • DPerform dynamic testing in addition to static testing to ensure runtime behavior is validated.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which of the following activities is an example of static testing?

   • AReviewing the requirements document to identify ambiguous statements
   • BRunning a set of test cases against the compiled application
   • CMeasuring the response time of a web service under high user load
   • DTesting the application's ability to recover from a system crash
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   Which of the following is a limitation of static testing?

   • AIt is only useful for code, not for other work products
   • BIt cannot detect runtime issues such as memory leaks
   • CIt cannot be used on requirements documents
   • DIt requires a fully compiled and running system
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A team is about to start coding a new feature. The requirements are clear, but the design document contains a logical flaw that could lead to incorrect behavior in a specific edge case. What is the best way to detect this flaw?

   • APerform a static review of the design document before coding begins.
   • BIgnore the flaw because design documents are not tested.
   • CWait until system testing to see if the edge case fails.
   • DWrite unit tests for the edge case and run them after coding.
   Reveal Solution Discussion Select an answer first